Google’s generative AI performance report in Search Console is widely reported as reaching properties broadly, according to trade press coverage on August 11 from Search Engine Roundtable, Search Engine Journal, RW Digital, Search Engine Watch, and ppc.land. Google has issued no separate announcement of a completed rollout; the June 3 Search Central Blog post remains its only official statement on the report. Google publishes two separate reports, one covering AI features in Search and one covering AI features in Discover, and each returns exactly one metric: impressions.
What Changed Since June
Google introduced the reports on June 3 in a Search Central Blog post, describing rollout to “a subset of website owners.” We covered that launch, the impressions-only limit, and the opt-out in our report on the generative AI reports launch, and noted that rollout reached UK-based site owners first, with no date announced for wider access. Trade coverage now says access has widened well beyond that subset, though Google has published no completion notice to confirm it. The data itself is a single number, split by page, country, device, and date.
What the Report Shows, and What It Withholds
| Reported | Not reported |
|---|---|
| Impressions, by page (final/canonical URL) | Clicks |
| Impressions, by country | Queries or prompts |
| Impressions, by device (desktop, tablet, mobile) | CTR and average position |
| Impressions, by date (daily, weekly, monthly, Pacific Time) | Citation placement, passage used, conversion data |
Search Labs experiments sit outside both reports. Per Google’s help documentation, an impression here means a link to the site was shown to a user inside a generative AI feature on Search. That definition sounds identical to the standard Search Console impression. It is not counted the same way.
Why an AI Impression Is Not a Search Impression
Google’s help documentation states it directly: “The generative AI performance report includes data from the Web search type in the Performance report (Search results).” These impressions are not a separate count layered on top of a site’s existing Search totals. They are a slice drawn from the same Web search data the Performance report already tracks, which is one documented reason the two numbers should not simply be added together.
Three counting rules widen the gap further. At the property level, if two URLs from the same site appear inside one generative response, Google’s chart counts that as a single impression, not two, which is why chart totals and page-level table totals can diverge. In AI Overviews, a link only counts once a user scrolls or expands it into view; a link that loaded but stayed off-screen counts for nothing. In AI Mode, a follow-up question is treated as a brand-new query, so a single conversation can generate several impression events rather than one. For ordinary web results, by contrast, Google documents that an impression counts whenever an item appears in the current page of results, whether or not it is scrolled into view.
Can You Compare the Search Console Generative AI Report to Standard Search Data?
No. The figure in the Search Console generative AI report is drawn from the same Web search data already inside the Performance report, not an addition to it, and it requires a link to be scrolled or expanded into view in an AI Overview, or counts as a fresh event on every AI Mode follow-up. For ordinary web results, an impression counts when the item appears in the current page of results. Summing or ratio-comparing the two produces a figure without a defined meaning.
The Missing Prompt Is the Point
The report has no query or prompt dimension, so a page can show impressions inside an AI feature with no record of which question produced them. That gap sits at the query stage. geoSurge research, covered in our report on brand recall inside Gemini’s fan-out queries, found brands present in a model’s recall set turned up in fan-out queries 55.7% of the time, against 17.4% for brands outside it, a 3.2x gap across 66 questions and roughly 3,960 answers. Search Console’s impression count only arrives after that stage has run its course.
The Usual Search Console Limits Still Apply
The report inherits Search Console’s standard 1,000-row limit and its normal time-period constraints. Preliminary data can shift within hours of appearing and is marked with dotted lines on the charts until it settles. Search Engine Journal’s guide to reading the report sets out the same dimensions, the excluded metrics, and the aggregation behaviour behind the chart-versus-table difference.
Wider Access, Same Single Metric
Trade coverage puts access well beyond the “subset” Google described in June. What it opens is still a single, differently-triggered slice of data the Performance report already holds, not an addition to it. That definition comes from Google’s own documentation for the report Google introduced on June 3.
