Google introduced dedicated generative AI performance reporting in Search Console. The useful move for a WordPress site is not staring at the chart. It is mapping AI impressions to pages, queries, snippets, internal links, and content assets that make the page worth clicking.
Use this for business sites, blogs, service pages, documentation, and resource hubs that are starting to see AI visibility but cannot yet explain which content should be refreshed.
Quick answer
Search Console Generative AI Performance Report Actions should be handled with a narrow evidence-first workflow: export report, map canonical pages, improve answers, then verify the result before making broader changes.
What to check first
- Export AI performance data by page, query, date, country, and device when the report is available.
- Separate visibility questions from click-through questions so expectations stay realistic.
- Map each AI-visible query to one preferred canonical page and one next-step page.
- Add a direct answer block, comparison table, checklist, diagram, or example when the page is too generic.
- Add internal links from high-impression pages into the cluster page that should convert.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Export report | Export AI performance data by page, query, date, country, and device when the report is available. | Each valuable AI-visible query has one preferred page. |
| Map canonical pages | Separate visibility questions from click-through questions so expectations stay realistic. | The preferred page answers the query in a clear extractable block. |
| Improve answers | Map each AI-visible query to one preferred canonical page and one next-step page. | The page contains a useful visual, table, checklist, or example. |
| Add assets | Add a direct answer block, comparison table, checklist, diagram, or example when the page is too generic. | Internal links point to the service, hub, or diagnostic page that helps the reader continue. |
Why this usually happens
- AI features can increase impressions while clicks stay flat.
- A page can be cited or shown for a query that it only answers halfway.
- Generic content gives the search result enough answer to skip the click but not enough trust to convert.
- Without internal links, AI-visible posts do not pass visitors into the service path.
Field notes
- Do not chase every AI impression. Prioritize queries with business fit and pages already ranking in normal Search.
- Keep one page as the canonical answer for each important question.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
ai_report_action:
query: avada changelog
preferred_page: /blog/avada-builder-vulnerability-changelog-monitoring
support_page: /blog/avada-changelog-security-update-priority-board
missing_asset: patch priority matrix
next_internal_link: /services
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Export report
- Map canonical pages
- Improve answers
- Add assets
- Link to next step
What to tell the client or owner
Summarize which AI-visible pages need a title refresh, answer block, internal links, or new supporting content.
Production verification checklist
- Each valuable AI-visible query has one preferred page.
- The preferred page answers the query in a clear extractable block.
- The page contains a useful visual, table, checklist, or example.
- Internal links point to the service, hub, or diagnostic page that helps the reader continue.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, turn AI Search Console data into content improvements.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Annotate the AI reporting boundary
When generative AI visibility first appears, use the Search Console AI Mode totals baseline report to compare matched windows and avoid double counting the separate AI view with overall performance totals.
Add social and video platform properties carefully
Google now offers Search Console platform properties for Instagram, TikTok, X, and YouTube. Use the platform-property verification and access test to document business ownership, authorization, report access, exports, revocation, and agency handoff before comparing social and website search performance.
Move FAQ effort after Google rich result deprecation
Google stopped showing FAQ rich results in May 2026. Use the FAQ rich result deprecation and WordPress schema cleanup to keep useful answers, remove duplicate markup and obsolete promises, and measure ordinary search clicks and conversions instead.
Add a preferred-source control with a verifiable fallback
For Google's August 20 publisher control, use the Google Preferred Sources button for WordPress to choose the standard, custom, or deeplink path and test domain eligibility, localization, caches, keyboard use, and return navigation.
Helpful references