Compendium / Platform surfaces

Generative AI Performance Report (Search Console)

TypePlatform surface
Term maturityestablished
Operator maturityplausible
Lifecyclein flux
Relevanceoperational
Verified2026-10-28
Google's Generative AI performance report in Search Console counts how often links to a site were shown inside AI Overviews and AI Mode, by page, country, device and date. It reports no queries, no clicks and, according to Google's documentation, no split between the two surfaces (as of October 2026). Read it as a record of exposure next to page-level clicks, never as a traffic or effect metric.

Consensus definition

The Generative AI performance report (Search) is a Search Console view that Google introduced on 3 June 2026 for a subset of websites and had rolled out to all websites worldwide by 31 August 202612. A separate report covers generative AI features in Discover; this entry covers the Search report2. It covers generative AI features on Google Search, currently AI Overviews and AI Mode; Google expects to update that list over time, and Search Labs experiments are not included2. The report lists a single metric, impressions, defined as how many times links to the site were shown to a user in a generative AI feature on Google Search2. Data can be grouped by page (the final linked URL after redirects, mostly assigned to the canonical URL), country, date (Pacific Time) and device, and filtered by search type: text-based web search, or multimodal search such as Google Lens, Circle to Search and uploaded images23. The chart aggregates by property, so two links to the same site in one AI feature count as one impression, and switches to the URL when a URL filter is set; a table grouped by page counts per page. The two totals can differ, and the 1,000-row limit of the performance reports also applies here2. The impressions are part of the Web search data in the Performance report, not added to it21. A companion Search Console control lets a site exclude itself from AI Overviews, AI Mode and AI features in Discover; an excluded site receives no impressions or traffic from those features, and Google states the control is not a ranking signal elsewhere in Search45.

rhinegold operator refinement

Rhinegold's position: the report documents exposure, not effect. An impression says that a link to the page was shown inside an AI answer. It does not say which question triggered the answer, whether the link was read, or whether a visit followed. Google's launch post names impressions, pages, countries, devices and dates, and no clicks or queries1; trade coverage at launch noted that click data was not mentioned6. In our measurement work we therefore use the report as the numerator of an exposure share. Per page and period, set the AI impressions next to the same page's Web impressions and Web clicks from the Performance report, with the same dates, country, device and search type. The share of Web impressions with an AI link is AI impressions divided by Web impressions; it can be formed because the AI impressions are part of the Web data2. It measures how often an AI feature carried the page's link, not how visibility splits between AI and classic results. Next to it we read the page's Web click-through rate; neither ratio is an AI click-through rate, because the clicks include all web search. Read numerator and denominator separately: the share also rises when Web impressions fall while AI impressions stay put. A page whose share rises while its clicks stay flat or fall is a candidate for zero-click loss; whether the AI surface caused it needs a separate test with untreated comparison pages, as described under AI Overview Traffic.

Operational use

Export the page table on a fixed weekly date range; the export covers chart and table, and values shown as ~ or - in the report become zeros in the download2, so a zero in the export can mean missing rather than none. Join the page tables of both reports on URL for the same dates, country, device and search type, keep both on Pacific Time days, and use the same aggregation level in numerator and denominator2. Before comparing periods, check Google's list of data anomalies: a logging error lowered this report's impressions for 13 to 17 August 2026, restored on 21 August7. Use the joined view for three jobs: find the pages that appear in AI answers at all, which narrows the page set for prompt-level checks of citation rate in AI Mode and AI Overviews; track the share of Web impressions with an AI link per page over time; and, after a change to the generative AI control, check whether impressions stop or return — a use Google names for this report; exclusion takes effect within one to two days, for some content later5. Read the effect on clicks in the Performance report against comparison pages. Record the report's state on each export date, since Google has said it will add metrics over time, without naming them or giving dates14.

Measurement boundary

The report cannot show the queries or prompts behind an impression, clicks or click-through rate, position or prominence inside an answer, or, according to the documentation, a split between AI Overviews and AI Mode21. Clicks from both surfaces are counted in the Performance report under the Web search type, together with all other web clicks89: AI clicks are not reported separately at any level, and the report's impressions carry no query. The Performance report's position and query data follow their own rules — all links in one AI Overview share a single position, and in AI Mode a follow-up question counts as a new query with its own impressions, positions and clicks9; this report has neither positions nor queries. Google says a site that has not received enough impressions in these features usually does not see the report, and gives no threshold2. An AI answer that does not link the page produces no impression, so a share of zero does not mean that no AI feature drew on the page. Google has said it will add metrics over time14, so this boundary describes the report as of October 2026. Bing Webmaster Tools takes a different approach: it counts citations and shows a sample of grounding queries for Copilot and Bing's AI answers, and Bing states that these counts say nothing about placement or role within an answer10; see Bing AI Performance Report.

Distinct from

From AI Overviews vs AI Mode: those are the two surfaces; the report counts exposure across both and, per the documentation, does not separate them2. From citation rate: a citation rate is a share of AI answers on a defined prompt set; the report has no prompt set and no count of answers, only a count of times links were shown. From LLM referral traffic: referral traffic counts visits that arrived; the report counts showings, and clicks from Google's AI surfaces arrive mixed into Web search data8. From grounding: grounding is the retrieval step behind an answer; the report counts only links that were shown after it2. From Microsoft Copilot and Bing's AI Performance report: Bing counts citations and shows grounding queries, Google counts impressions without queries102.

Common mistakes

  • Reading AI impressions as AI traffic: the report has no clicks, and a page can gain AI impressions while losing clicks in the same period.
  • Adding AI impressions to Web impressions: they are already included in the Performance report under the Web search type21.
  • Comparing the chart total with the sum of page rows: the chart counts one impression per property for links shown in the same feature, a table grouped by page one per page, so the totals can differ2.
  • Attributing a change to AI Overviews or to AI Mode alone: the documentation describes no split between the two surfaces2.
  • Reading a missing report as zero exposure without checking the generative AI control: a site with too few AI impressions and an excluded site both see no report25.

Sources & deeper reading

Last verified 2026-10-28 · Next review 2026-12-03
Question this measurementA metric can be right and the conclusion still wrong.Ask Dietrich →
Related terms
Cite this entry
rhinegold. “Generative AI Performance Report (Search Console).” The Rhinegold Compendium. https://insights.rhinegold.de/compendium/generative-ai-performance-report/. Updated 2026-10-28.