If your Search Console Generative AI report shows rising impressions, that does not automatically mean your GEO program is working—or that you should rewrite your site. Those impressions measure how often links to your pages appeared in Google Search generative AI features such as AI Overviews and AI Mode. They do not measure ChatGPT, Perplexity, or Gemini answers, and they are not a revenue forecast. This article shows how to read the report, what to ignore, and how to decide whether a strategy change is justified.
Bottom line: Use the Generative AI performance report as a Google-surface visibility layer. Pair it with overall Search performance and a separate assistant-probe audit for ChatGPT-style surfaces. Change content or budget only after you map impressions to eligible pages, business-relevant queries, and downstream engagement—not after a single weekly spike.
What the Generative AI report actually measures
Google launched dedicated Search Generative AI performance reports in Search Console in June 2026, with a Search view and a Discover view. Per Google’s help documentation, the Search report covers impressions for AI Overviews and AI Mode, and Google notes the insights were rolled out to websites worldwide as of August 31, 2026.
In the Search report, an impression is counted when links to your site were shown to a user inside a generative AI feature on Google Search. Google’s broader impression guidance for AI Overviews states that standard impression rules apply and that, to be counted, the link must be scrolled or expanded into view. Clicking an external link inside an AI Overview or AI Mode counts as a click in Search Console’s usual methodology.
Two aggregation details matter when you interpret totals:
-
Chart totals are property-level. If two of your URLs appear in the same generative AI result, the chart can count that as one property impression.
-
Page tables are URL-level. Grouping by pages can show more impressions than the chart because each linked URL is counted separately.
Also note Search Console’s explicit limit: Labs experiments are excluded. Treat early experimental surfaces as out of scope for this report.
The Three-Layer Visibility Stack
Businesses get into trouble when they treat one dashboard as the full AI-search story. Use three layers with different jobs:
|
Layer |
Primary signal |
Decision it supports |
|
1. Generative AI report |
Impressions (and related page/country/device cuts) in AI Overviews and AI Mode |
Whether Google generative features are surfacing your URLs at all |
|
2. Overall Search Performance |
Clicks, CTR, queries, and landing-page engagement for the same URLs |
Whether visibility is translating into visits worth investigating in Analytics |
|
3. Assistant-probe audit |
Manual or tooling checks of how assistants describe and cite your brand |
Whether non-Google answer surfaces are a separate gap |
Layer 1 answers a narrow question: “Are we appearing as supporting links in Google’s generative features?” Layer 3 answers a different question that Search Console cannot answer for ChatGPT or Perplexity. If you need a structured process for Layer 3, use Oasbit’s guide on how to audit brand visibility in AI answers.
Eligibility checks before you blame content quality
Google’s guide to optimizing for generative AI features is explicit: to be eligible for generative AI features on Google Search, a page must be indexed and eligible to appear in Google Search with a snippet. The same guide states that a site must also be included in Search generative AI features in Search Console.
That second condition is easy to miss. Under Settings → Search generative AI, properties can include or exclude links and content from AI Overviews, AI Mode, and generative AI features in Discover. Google documents that exclusion is the reason some owners see no Generative AI report data. If the control is set to exclude, zero impressions are a configuration outcome—not proof that your content failed.
Run this short eligibility pass before rewriting pages:
-
Confirm the property is set to include Search generative AI features (or intentionally excluded).
-
Confirm priority pages are indexed and snippet-eligible (no blanket noindex or aggressive nosnippet where you want AI-feature links).
-
Confirm important copy is available as text, not trapped in non-crawlable interfaces.
-
Only then evaluate whether the content itself is commodity versus distinctive.
Google also myth-busts common GEO shortcuts for Google Search: you do not need special AI text files such as llms.txt, forced content “chunking,” or inauthentic mention campaigns to appear in Google’s generative features. Keep those items out of your Google-only action plan unless you have a separate, non-Google reason to publish them.
The Generative AI Impression Action Matrix
Once eligibility is clear, classify what you see. This matrix is designed for operators who need a next step, not a vanity score.
|
Pattern |
What it usually means |
Primary next move |
|
No report / near-zero impressions |
Too little generative-feature exposure, exclusion control, or eligibility gaps |
Fix inclusion and technical eligibility before commissioning net-new GEO content |
|
Impressions concentrated on low-intent pages |
Google can surface you, but not on pages that create demand |
Strengthen commercial and decision-support pages with unique, people-first depth |
|
Impressions rising, clicks flat |
Visibility without a compelling reason to leave the AI answer |
Improve title/snippet clarity, unique proof, and on-page next steps—not more near-duplicate FAQs |
|
Clicks rising, conversions flat |
AI-assisted discovery is working; the offer or landing path is not |
Treat this as conversion work, not a generative-AI ranking emergency |
|
Google layer healthy, assistants weak |
Your gap is multi-surface GEO, not Google eligibility alone |
Keep Google fundamentals; expand third-party evidence and assistant-specific monitoring |
A 30-minute reading workflow
Use this sequence so the report produces decisions instead of screenshots.
-
Set a comparable window. Compare the last 28 days with the prior 28 days. Ignore one-day spikes while preliminary data is still settling.
-
Export the Pages dimension. Sort by impressions and mark each URL as revenue-adjacent, trust-building, or low business value.
-
Cross-check overall Performance for those URLs. Look for clicks and query themes. Google notes generative AI feature data is also included in the broader Search performance reporting.
-
Check Analytics engagement for the same landing pages. Google has reported that clicks from results pages with AI Overviews can be higher quality in the sense that users may spend more time on site; validate that against your own conversion events.
-
Assign one matrix action per page cluster. Do not create five workstreams from one chart.
Hypothetical example: regional HVAC company
Imagine a regional HVAC company sees Generative AI impressions jump 40% month over month. The Pages table shows most impressions on a generic “what is a heat pump” explainer, while the service-area and financing pages barely appear. Overall Performance shows clicks rising on the explainer but booked-estimate conversions unchanged.
In this hypothetical, the correct response is usually not a sitewide GEO rewrite. Reinforce the explainer with first-hand installation constraints, local climate notes, and clear links into estimate pages. Then improve the decision pages Google is not yet surfacing. That prioritizes non-commodity content—the same direction Google emphasizes—without inventing dozens of near-duplicate tip pages that risk scaled content abuse.
Common failure patterns
-
Treating impressions as assistant citations. Search Console’s Generative AI report is Google Search-centric. A healthy Google layer can coexist with weak ChatGPT findability.
-
Chasing llms.txt as a Google ranking lever. Google states you do not need new machine-readable AI text files to appear in its generative AI capabilities.
-
Publishing query-variation pages to cover fan-out. Google warns that creating separate pages primarily to manipulate generative AI responses can violate scaled content abuse policies and is a weak long-term approach.
-
Confusing chart and table totals. Property-level and page-level aggregation can disagree. Investigate discrepancies before declaring a traffic crisis.
-
Changing opt-out settings without a measurement baseline. If you are evaluating inclusion versus exclusion, capture Generative AI report and overall performance baselines first. Oasbit’s earlier decision guide on keeping or opting out of Google generative AI search features covers that tradeoff in depth.
When this advice does not apply
If your primary acquisition surface is not Google Search—for example, a B2B product discovered mainly inside ChatGPT workflows—Layer 1 will understate the opportunity. In that case, keep Search Console as a hygiene check, but weight assistant-probe audits and third-party evidence more heavily.
If your site is brand-new and barely indexed, generative AI impressions are the wrong north star. Focus on crawlability, indexing, and a small set of distinctive pages first. Generative AI features still depend on Google’s core retrieval and ranking systems.
Recommended next steps
-
Open Search Console → Generative AI performance (Search) and confirm inclusion under Search generative AI settings.
-
Export top impression pages and classify them with the Action Matrix.
-
Pick one page cluster for non-commodity improvement this month—unique process detail, original data, or first-hand constraints—not another generic tip list.
-
Run a separate assistant-probe pass for the five questions your buyers actually ask sales.
If you want help turning Generative AI report patterns into a prioritized visibility plan across Google and assistant surfaces, Oasbit’s generative engine optimization services focus on ethical measurement, content prioritization, and practical implementation—not unverifiable “AI ranking” claims.
To pressure-test how findable your brand is today, start with a growth strategy session or use Oasbit’s free AI visibility checker before you commission a broader rewrite.
Sources
-
Introducing Search Generative AI performance reports in Search Console — Google Search Central Blog
-
Generative AI performance report (Search) — Search Console Help
-
Optimizing your website for generative AI features on Google Search — Google Search Central
-
AI features and your website — Google Search Central
-
Search generative AI control — Search Console Help
-
What are impressions, position, and clicks? — Search Console Help (AI Overviews / AI Mode methodology)




