Search Console AI Reports Guide 2026

Google's new Search Console generative AI performance reports give SEOs a separate view of where their pages appear inside AI Overviews, AI Mode, and generative AI experiences in Discover. The important caveat: the reports are visibility reports, not traffic reports. They show impressions, pages, countries, devices for Search, and dates, but they do not show clicks, CTR, position, queries, revenue, or a clean split between AI Overviews and AI Mode.

Use the reports to answer one question first: "Which pages are being surfaced by Google's generative AI features?" Then connect that page list to standard Search Console, GA4, CRM, and rank-tracking data before making content or opt-out decisions.

Quick Answer

Google announced Search Console generative AI performance reports on June 3, 2026. The Search report covers AI Overviews and AI Mode; the Discover report covers generative AI features in Discover. Google says the reports provide impression data by page, country, device for Search, and date granularity, while the Help Center confirms the rollout is limited to eligible properties and excludes Search Labs experiments (Google Search Central, June 3, 2026, Search Console Help).

The report is useful for AI-search visibility monitoring, but it is not enough to prove traffic loss or incremental revenue. Treat AI impressions as an early diagnostic layer, then reconcile them with the normal Performance report, GA4 landing-page sessions, conversion data, and content quality reviews.

What Changed on June 3, 2026

Before this launch, site owners had to infer most AI-search impact from blended Search Console data. AI Mode and AI Overviews were counted in broader Search performance surfaces, but SEOs could not isolate where generative AI visibility was happening with a dedicated report.

The June 3 release changed that in three ways:

Change	What it means for SEOs	What it does not solve
Dedicated Search generative AI report	See pages that receive impressions in AI Overviews and AI Mode	Does not show clicks, CTR, position, or queries
Dedicated Discover generative AI report	See visibility in generative Discover surfaces	Does not include device segmentation like Search
New visibility and control language from Google	Gives publishers a clearer place to monitor AI surfaces and manage inclusion	Does not make AI-search ROI measurable from Search Console alone

Google's announcement says the data remains included in overall performance reporting while a separate view is being launched for generative AI visibility (Google Search Central). Google's Help Center adds two practical constraints: not every property has the report during rollout, and a property may not qualify if it has not received enough generative AI impressions (Search Console Help).

Search Engine Land's launch coverage also emphasized the same operational limitation practitioners care about most: the report includes impressions, pages, countries, devices, and dates, but not click data (Search Engine Land).

What The Reports Actually Show

The Search report measures how often URLs from your site appeared in generative AI features on Google Search. Google's Help Center currently lists AI Overviews and AI Mode as included Search features, and says the list may change as Google develops Search (Search Console Help).

The practical dimensions are:

Dimension	Search generative AI report	Discover generative AI report	How to use it
Impressions	Yes	Yes	Measure visibility trend, not traffic
Pages	Yes	Yes	Identify URLs being surfaced by AI features
Countries	Yes	Yes	Separate market rollout and demand differences
Devices	Yes	No, based on Google's launch language	Spot mobile-vs-desktop Search behavior
Dates	Yes	Yes	Track changes after launches, content updates, and opt-out changes

This is enough to build a visibility dashboard, but not enough to answer whether AI Overviews are "stealing clicks" from a page. You need blended analysis because Search Console's AI report intentionally starts with impressions.

What Is Missing

Do not build executive reporting that treats AI impressions as visits or revenue. The missing fields are as important as the included fields:

Missing field	Why it matters	Workaround
Clicks	You cannot calculate actual AI-feature traffic	Compare the same URLs in standard GSC and GA4
CTR	You cannot calculate AI-surface click rate	Use standard Web CTR as a separate, blended signal
Queries	You cannot see which prompts or searches triggered visibility	Infer intent from page topic, Search Console queries, and rank-tracking SERP captures
Position	You cannot compare AI visibility to classic rank	Use standard GSC average position only as traditional Search context
AI Overview vs AI Mode split	You cannot tell which AI surface generated the impression	Use date, country, and device patterns as directional clues only
Conversion value	Search Console has no revenue or lead quality data	Join to GA4, CRM, ecommerce, or BI data by landing page and date

Quattr's analysis of the launch summarized this neatly: the report shows impressions, pages, countries, devices, and dates, but not clicks, CTR, or traffic (Quattr).

How To Access The Report

Inside Search Console, look for the generative AI performance report under the Performance area. If it is missing, do not assume your site has no AI visibility.

Google lists three common reasons the report may not appear:

1. The report is still rolling out and your property does not have access yet.
2. Your site has not received enough generative AI impressions.
3. Your site may be excluded from Search generative AI features, in which case it needs to be included to be eligible (Search Console Help).

Use a domain property where possible. Path-prefix properties can still be useful for traditional reporting, but generative AI visibility is easiest to interpret when the property covers the full site.

The Correct Measurement Model

Think of AI-search measurement as a four-layer model.

Layer	Data source	Question answered	Decision enabled
Visibility	GSC generative AI report	Which pages appeared in AI features?	Which URLs deserve review
Search demand and clicks	Standard GSC Performance report	Did impressions, clicks, CTR, or average position change?	Whether demand or click behavior changed
On-site behavior	GA4, server logs, analytics warehouse	Did organic sessions and engagement change?	Whether click changes affected site visits
Business value	CRM, ecommerce, subscriptions, leads	Did revenue or qualified pipeline change?	Whether to invest, rewrite, or opt out

This model prevents two common mistakes:

• Treating AI impressions as traffic.
• Blaming AI Overviews for a drop that was actually caused by ranking loss, tracking failure, seasonality, or a content quality problem.

For the broader reporting stack, pair this workflow with the SEO1 guides on Google Search Console workflows and measuring SEO ROI.

Weekly Workflow For SEOs

Run this workflow once a week for properties that have the report. It takes 30-45 minutes once dashboards are set up.

1. Export AI-Impressed Pages

Open the generative AI report and sort by impressions. Export the top pages for the last 7, 28, and 90 days.

Create three working groups:

Group	Meaning	First action
High AI impressions, high organic clicks	AI visibility may be additive or at least not obviously harmful	Protect and improve the page
High AI impressions, falling organic clicks	Possible AI answer satisfaction, SERP layout change, or intent shift	Compare queries, rankings, snippets, and GA4
Low AI impressions, strong organic clicks	Traditional search works but AI visibility is weak	Review content structure and entity coverage

Do not judge a page from one day of data unless the traffic pattern is extreme. Use rolling 7-day and 28-day windows for decisions.

2. Join By URL, Not By Query

Because Google's generative AI report does not expose query data, the URL is your stable join key.

For each page, build a row with:

• AI impressions from the generative AI report.
• Web clicks, impressions, CTR, and average position from standard GSC.
• Organic landing-page sessions from GA4.
• Conversions or revenue from your CRM/ecommerce system.
• Last content update date.
• Content type: definition, comparison, tutorial, product page, category page, local landing page, news, or research.

This turns the report from a novelty metric into an editorial queue.

3. Diagnose The Pattern

Use this decision table before making content changes.

Pattern	Likely explanation	Action
AI impressions up, Web clicks stable	AI visibility may be incremental or non-cannibalizing	Keep monitoring; improve internal CTAs
AI impressions up, Web impressions stable, Web CTR down	AI answer may be satisfying more informational intent	Add original data, examples, tools, templates, or first-hand analysis
AI impressions up, Web average position down	Ranking loss may be the main issue, not AI	Run normal SEO diagnosis first
AI impressions down, Web clicks down	Page may be losing relevance or crawl/indexing strength	Refresh content and check indexing, internal links, and competitors
No AI report access, Web CTR down	You cannot prove AI impact from this report	Use SERP tracking and page-level analytics instead

4. Segment By Page Type

Different page types need different responses.

Page type	Best response to high AI impressions	What not to do
Glossary / definition pages	Add concise answer blocks plus deeper examples and internal links	Do not pad with generic definitions
Comparison pages	Add methodology, pricing dates, firsthand testing, and decision tables	Do not let AI summarize a commodity list
Product/category pages	Improve product data, Merchant Center feeds, schema, reviews, and availability	Do not opt out before checking revenue impact
Local pages	Add real service-area proof, photos, reviews, staff, and local examples	Do not create thin location variants
Research/report pages	Promote proprietary data and update dates visibly	Do not hide the core finding below generic intro text

Google's generative AI optimization guidance says foundational SEO still matters because AI features are rooted in Google's Search systems, while unique, non-commodity content is the long-term lever most likely to help visibility (Google Search Central generative AI guide).

5. Separate Content Problems From Reporting Problems

If stakeholders ask, "Did AI Overviews kill our traffic?", answer with a structured test:

1. Did the affected URLs appear in the generative AI report?
2. Did standard Web impressions stay stable or grow?
3. Did Web CTR fall while average position stayed stable?
4. Did GA4 organic sessions fall for the same URLs?
5. Did conversions fall, or only informational visits?
6. Did competitors, SERP features, seasonality, or tracking changes explain the movement?

Only when most of these line up should you call the issue likely AI-search cannibalization.

Opt-Out Controls: When To Use Them

Google announced new controls for website owners alongside the reporting changes, describing them as part of a broader set of tools for navigating AI in Search (Google product blog). The strategic question is not "Can we opt out?" It is "What do we lose if we opt out?"

Use this matrix:

Site/business model	Default recommendation	Reason
Ecommerce	Stay included	Product and category visibility can still drive qualified demand
B2B SaaS	Stay included, monitor demo/pipeline pages closely	AI visibility may influence research-stage buyers
Local services	Stay included	AI answers can surface local entities, reviews, and service proof
Ad-supported publisher	Test carefully by section	Informational answers can reduce pageviews, but visibility may still support brand reach
Subscription publisher	Consider limited opt-out tests	High-value content may lose subscription opportunities if summarized
Regulated YMYL site	Stay included only if content is accurate, reviewed, and current	Wrong or stale content can be amplified in sensitive contexts

Do not use opt-out controls as a substitute for better content. Google's AI features documentation says normal Search controls such as nosnippet, max-snippet, noindex, and robots rules affect how content can appear, but those controls also have broader Search consequences (AI features and your website).

Content Strategy From The Report

The generative AI report is most useful when it changes your content backlog.

Pages With High AI Impressions And Low Clicks

These are often pages where the answer is easy to summarize. Improve them by adding information an AI answer cannot fully replace:

• Original examples from your own data or client work.
• Decision trees.
• Templates.
• Calculators.
• Benchmarks with methodology.
• Screenshots or process evidence.
• Expert commentary with named authorship.
• Comparisons that include trade-offs, not just definitions.

For example, a page explaining "what is crawl budget" may be fully satisfied in an AI answer. A page that diagnoses crawl waste from real log-file patterns, includes a prioritization worksheet, and shows before/after crawl stats has a stronger reason to earn a click.

Pages With Low AI Impressions But Strong Organic Performance

These pages may be ranking well in traditional Search while being hard for AI systems to extract. Review:

• Is the direct answer visible in the first 150-250 words?
• Are entities, dates, products, and steps named clearly?
• Are headings descriptive enough to stand alone?
• Are claims cited close to where they appear?
• Is the page mostly generic, or does it contain original information gain?
• Are images, tables, and examples accessible and crawlable?

This overlaps with Answer Engine Optimization, but avoid treating AEO as a bag of hacks. Google's own guidance says there are no special AI-only tricks required for Search; good technical SEO and useful content remain the base (Google AI optimization guide).

Dashboard Template

Build a dashboard with one row per URL and these columns:

Column	Source	Why it matters
URL	GSC AI report	Join key
AI impressions, 7 days	GSC AI report	Short-term visibility
AI impressions, 28 days	GSC AI report	Trend smoothing
AI impressions delta	GSC AI report	Change detection
Web clicks	Standard GSC	Traffic from traditional Search
Web CTR	Standard GSC	Click behavior
Average position	Standard GSC	Ranking context
Organic sessions	GA4	On-site traffic reality
Conversions/revenue	CRM/ecommerce	Business impact
Last updated	CMS	Freshness
Content type	Manual/CMS	Prioritization
Recommended action	SEO owner	Editorial queue

Use conditional formatting:

• Red: AI impressions up, Web CTR down, conversions down.
• Amber: AI impressions up, Web CTR down, conversions stable.
• Green: AI impressions up, clicks or conversions stable/up.
• Grey: no report access or insufficient data.

Common Mistakes

Mistake 1: Reporting AI Impressions As AI Traffic

Impressions mean visibility. They do not mean a user clicked to your site. Label dashboards "AI visibility" unless clicks are available from another source.

Mistake 2: Assuming Every CTR Drop Is AI Cannibalization

CTR can fall because of ranking changes, SERP features, seasonality, brand demand, tracking changes, or query mix. The AI report is one clue, not a verdict.

Mistake 3: Optimizing Only For Extraction

If a page is too extractable and not useful beyond the summary, it may get impressions without clicks. Add original value that makes the click worthwhile.

Mistake 4: Blocking AI Features Too Early

Opting out can remove visibility before you understand whether that visibility assists branded recall, later conversions, or high-value research paths. Test by section and monitor business outcomes.

Mistake 5: Creating Thin "AI Overview" Pages

Google warns against creating content primarily to manipulate rankings or AI responses. Build pages around user value, original experience, and clear structure, not long-tail query spam (Google generative AI optimization guide).

Quality Checklist

Before changing a page because of AI report data, check:

• The page is indexed and eligible for snippets.
• The main answer is clear near the top.
• The page includes information beyond what a generic AI answer can summarize.
• Factual claims have nearby citations.
• Dates are visible for freshness-sensitive guidance.
• Product, local, or organization data is consistent with structured data and visible content.
• Internal links point to stronger supporting pages.
• The page has a conversion path appropriate to its intent.
• You have compared AI impressions with standard Web clicks and GA4 sessions.
• You have waited long enough to avoid reacting to incomplete data.

FAQ

Does Search Console Now Show AI Overview Clicks?

No. Google's generative AI performance report is currently an impressions-focused visibility report. It shows where URLs appeared in supported generative AI features, not how many users clicked from those features.

Does The Report Include AI Mode?

Yes. Google's Help Center lists AI Overviews and AI Mode as included in the Search generative AI report, while noting that Search Labs experiments are not included (Search Console Help).

Why Can't I See The Report?

The rollout is limited. Google says you may not see the report if your property does not yet have access, if your site lacks enough generative AI impressions, or if the site has been excluded from Search generative AI features (Search Console Help).

Can I Use This Report To Prove AI Overviews Reduced Traffic?

Not by itself. You need page-level comparison with standard GSC clicks/CTR, GA4 sessions, conversion data, ranking data, and SERP observations. The AI report identifies visibility, not traffic loss.

Should I Opt Out Of AI Overviews And AI Mode?

Most SEO, ecommerce, B2B, and local sites should measure first and opt out only when there is clear business harm. Subscription publishers and high-value paywalled content have a stronger case for controlled tests, but the decision should be made by section, not across the whole site by default.

Bottom Line

The Search Console generative AI reports are a major measurement improvement because they turn AI-search visibility from a guess into a page-level signal. They are also deliberately incomplete. The winning workflow is not "optimize for AI impressions." It is:

1. Find pages surfaced in AI Overviews, AI Mode, and Discover AI features.
2. Compare those pages with standard Search clicks, GA4 sessions, and business outcomes.
3. Improve pages where AI visibility exposes commodity content.
4. Protect pages where AI summaries may replace high-value visits.
5. Keep reporting language precise: impressions are visibility, not traffic.

Used this way, the report becomes an editorial and analytics advantage instead of another vanity metric.