Google states that impressions from generative AI features are included in the overall Search Console performance report and that a separate generative AI view is rolling out to a subset of sites. When visibility begins appearing, totals, CTR, device mix, and page trends can change even if rankings or site content did not change that day.
Use this for SEO, content, agency, executive, and client reports when AI Overviews, AI Mode, or generative Discover visibility appears in Search Console or when impressions rise sharply without matching clicks.
Quick answer
Search Console AI Mode Totals Baseline Anomaly Report should be handled with a narrow evidence-first workflow: record reporting boundary, export matched scopes, build before-after baseline, then verify the result before making broader changes.
What to check first
- Record the first visible date for the generative AI report, available dimensions, property type, data freshness, filters, and export method.
- Export overall and generative AI data for the same date range, search type, country, device, and page scope without assuming the two views are additive.
- Build 28-day before and after baselines for clicks, impressions, CTR, average position, pages, countries, devices, and conversions.
- Annotate release dates, content launches, migrations, tracking changes, seasonality, and known Google updates beside the reporting boundary.
- Separate discovery, click-through, landing-page engagement, leads, and revenue so more AI impressions are not reported as business growth by themselves.
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 |
|---|
| Record reporting boundary | Record the first visible date for the generative AI report, available dimensions, property type, data freshness, filters, and export method. | Overall and AI reports use the same property, dates, filters, and dimension definitions. |
| Export matched scopes | Export overall and generative AI data for the same date range, search type, country, device, and page scope without assuming the two views are additive. | The dashboard explains whether AI metrics are included in overall totals and avoids double counting. |
| Build before-after baseline | Build 28-day before and after baselines for clicks, impressions, CTR, average position, pages, countries, devices, and conversions. | Every reported change separates impressions, clicks, CTR, landing engagement, and conversions. |
| Annotate other changes | Annotate release dates, content launches, migrations, tracking changes, seasonality, and known Google updates beside the reporting boundary. | Stakeholders can see which pages, countries, and devices changed after the boundary. |
Why this usually happens
- A new reporting view can expose visibility that was already blended into totals or becomes countable under updated reporting.
- AI result layouts can produce many impressions with different click behavior from traditional blue links.
- Property, date, country, device, page, and search-type filters can make two exports look comparable when they are not.
- A large impression increase can lower CTR while clicks and conversions remain stable.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
report_boundary:
property: sc-domain:example.com
first_ai_report_date: 2026-06-03
compare_window_days: 28
dimensions: [date, page, country, device]
metrics: [clicks, impressions, ctr, position, leads]
note: do_not_add_ai_view_to_overall_totals
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.
- Record reporting boundary
- Export matched scopes
- Build before-after baseline
- Annotate other changes
- Connect to outcomes
What to tell the client or owner
Share the property, report availability date, exact filters, export timestamps, before and after windows, overall and AI totals, annotations, and conversion source.
Production verification checklist
- Overall and AI reports use the same property, dates, filters, and dimension definitions.
- The dashboard explains whether AI metrics are included in overall totals and avoids double counting.
- Every reported change separates impressions, clicks, CTR, landing engagement, and conversions.
- Stakeholders can see which pages, countries, and devices changed after the boundary.
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, measure WordPress AI search visibility.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references