Since August 11, 2026, every Search Console property carries a report that did not exist in this form before: the Generative AI report. It shows how often your pages appear in Google's generative AI features — in AI Overviews, in AI Mode, and in generative Discover features. For the first time, Google delivers official numbers for a layer of visibility that was previously only measurable indirectly.
Before this report, AI Overview visibility could not be separated from classical impressions in Search Console: an appearance in an AI overview and a blue link counted into the same bucket. Anyone who wanted to know whether their domain shows up in generative answers had to rely on their own prompt tests. That is changing now — partially.
Partially, because the report can do considerably less than the initial excitement suggests. And because it is running with a known logging bug that currently sabotages any naive reading of the time series. This article puts both into perspective: what is in it, what is missing, and how the report fits into a measurement routine that can carry decisions.
The timeline: announced quietly, rolled out even more quietly
Google announced the report on June 3, 2026 on the Search Central blog and initially enabled it for a subset of properties only; the launch ran through the United Kingdom, among other markets. The full rollout came without a second announcement: since August 11, 2026, the report has been visible in all Search Console properties. Anyone who has not actively checked may not have opened it to this day.
Announcement on the Search Central blog, rollout to a subset of properties
Visible in all properties — not separately announced by Google
Start of the logging bug: impressions falsely trending down
The three dates belong together: two days after the full rollout, a data error began that distorts the time series to this day. Anyone opening the report for the first time now is looking at a curve whose most recent segment is wrong — more on that below.
What the report shows: one metric, four dimensions
The report reports impressions from generative AI features: AI Overviews and AI Mode in Search, plus generative features in Discover. These impressions can be broken down across four dimensions:
- Pages: which URLs appeared in generative answers
- Countries: which markets the impressions occur in
- Devices: distribution across mobile and desktop
- Time ranges: from hourly to monthly resolution
This yields three first looks worth taking before any dashboard gets built:
1. Which pages carry the AI impressions?
The pages dimension answers whether AI visibility is spread broadly across the domain or hangs on a few URLs. Both have consequences: a broad distribution suggests that generative systems use the domain as a whole. A strong concentration shows which content types actually land in answers — and which investments went nowhere.
2. How do countries and devices break down?
If you operate internationally, you see here in which markets generative features already touch your visibility and where they do not. The device breakdown answers how AI impressions distribute across device categories — relevant to the question of which usage situations are affected.
3. How does the time series develop?
The time series is the genuinely valuable view — with hourly resolution for short-term effects and monthly resolution for the strategic line. It is also the view that currently has to be read most carefully, because of the logging bug since August 13.
What the report does not show — and what that means for interpretation
The gaps are bigger than the scope. An honest inventory:
| Metric / feature | In the report | Consequence |
|---|---|---|
| Impressions | Yes | The only metric — shows appearance, not impact |
| Clicks | No | No traffic statement possible |
| CTR | No | No efficiency comparison with classical search |
| Queries / prompts | No | No intent mapping, no topic analysis |
| API access | No | Export is manual only, no automated pipelines |
Google has announced additional metrics — without a timeline. Until they arrive, two hard limits of interpretation apply:
Without clicks, no traffic statement. An AI impression proves that a page appeared in a generative answer. Whether that appearance was noticed, read, or clicked cannot be derived from the report. Any conversion of AI impressions into visitors, leads, or revenue is, on this data basis, made up.
Without queries, no intent mapping. The report does not say for which questions the pages appeared. Whether a URL surfaces for purchase-ready prompts or for casual definition questions remains invisible — and with it the commercially decisive information.
From this follows the most important equation of this article: impressions ≠ citations ≠ visitors. Anyone presenting slides with “AI visibility +X%” on this basis is selling a number whose business meaning they do not know. Such reports are already circulating — they are the AI equivalent of the ranking report without search volume.
“The report does not answer the question of what AI search delivers for you. It answers the question of whether you are in the game at all — and on which pages.”
The logging bug since August 13: do not overinterpret the dips
For data from August 13, 2026 onward, the report shows falsely declining impressions. According to Google, this is purely a logging problem: the data collection is faulty, while actual visibility in AI Overviews and AI Mode has not changed because of it. As of this article, the bug has not been fixed.
The operational risk is not the bug itself but its interpretation. Three wrong reactions that will now start appearing in reportings: First, the panic analysis — a team sees the drop and launches a root-cause investigation for a problem that does not exist. Second, false causality — anyone who shipped a relaunch, a content migration, or a technical update around August 14 sees a kink that has nothing to do with it. Third, the inversion: as long as the data collection is faulty, a real visibility loss in this period cannot be distinguished from the bug either. Until a confirmed fix, the time series from August 13 onward is simply not assessable — in either direction.
The annotation that will save you in six months
Every dashboard and every reporting document carrying these numbers needs an event annotation on August 13, 2026 as of now (“start of the GSC logging bug, impressions under-reported from here”) — and a second one as soon as Google confirms the fix. Time series without annotations generate discussions months later that nobody can resolve anymore, because by then nobody remembers the bug.
The practical routine: how the report belongs in your reporting
The report is not a dashboard replacement but a data source with narrow limits. Within those limits it is useful — if the routine is right. Four building blocks:
Step 1: Secure a baseline — manually, because there is no API
The report is not available through the Search Console API; export runs manually only. So: define a fixed interval (weekly is enough for most organizations), file the export, document the export date and the bug status. This sounds trivial and is the step most often skipped. Whoever starts exporting six months from now has no comparison base for the only question the report can answer: whether something is changing.
Step 2: Read trends, ignore absolute values
What exactly counts as one impression inside a generative interface cannot be audited from the outside — and without clicks and queries, the absolute value has no business translation. What is usable is the direction: is your own time series rising or falling, and is the structure shifting across pages, countries, and devices? Read your own history against itself, never against third-party benchmarks — for which no reliable data basis exists anyway.
Step 3: Hold the page level against your own citable assets
The analytically most productive exercise: lay the URLs with AI impressions against the list of pages deliberately built as citable assets — definitions, data, structured answers. Three patterns are possible. An asset collects impressions: it works. An asset collects none: a diagnostic case for structure, accessibility, or relevance. And a page collects impressions that was never meant as an asset: a hint at what generative systems actually use from the domain — often not what the content team expects. The systematic version of this comparison, including prompt tests against multiple models, is the core of the GEO audit.
Step 4: Combine with cross-model tracking
The report covers Google's ecosystem exclusively. ChatGPT, Perplexity, Claude, and Copilot still deliver no analytics at all — for those systems, prompt-based tracking remains the only data source: repeated, versioned prompt sets against multiple models, evaluated for mention, portrayal, and competitors, as in LLM citation monitoring. For the qualitative diagnosis — why a model picks or passes over a source — the method from prompt reverse engineering complements this. The GSC report then validates a subset of these observations with official numbers; it replaces none of them.
The opt-out switch: a business decision, not an SEO trick
Alongside the report, Google introduced an opt-out switch that lets sites take their content out of AI features without losing organic rankings. For the first time, a separation exists that was missing until now: out of generative answers, in the classical index.
This decision is a business decision, not an SEO tactic. The switch is a candidate for business models whose value lies in the content itself — paid content, exclusive data, original research — and that do not want generative answers to preempt that value. Whoever lives on visibility, recommendation, and authority, by contrast, gives up with the opt-out exactly the surface this discipline is about. And the switch is not a ranking lever in either direction: it promises that organic rankings are preserved — a mechanism by which an opt-out improves classical rankings does not exist.
Generative AI report FAQ
Why do I see no clicks in the Generative AI report?
Because the report does not include them. It reports impressions from generative AI features exclusively — no clicks, no CTR, no queries. Google has announced additional metrics without a timeline. Until they arrive, statements about traffic or efficiency based on this report are not possible, not even approximately.
Are declining AI impressions since mid-August a warning sign?
Most likely not: for data from August 13, 2026 onward, the report shows falsely declining impressions due to a known logging bug. According to Google, this is purely a data-collection problem, not a real change in visibility; as of this article, it has not been fixed. Evaluate the time series from that date only after a confirmed fix, and annotate the period in your own reporting.
Does the report replace external AI monitoring?
No. It covers Google's ecosystem exclusively: AI Overviews, AI Mode, and generative Discover features. For ChatGPT, Perplexity, Claude, and Copilot there is still no official analytics — for those systems, prompt-based cross-model tracking remains the only measurement method. The report adds official Google numbers to that tracking; it cannot replace it.
Bottom line
The Generative AI report is real progress: for the first time, Google separates AI visibility from classical impressions and makes it visible per page, country, device, and time range. It is at the same time limited progress: a single metric, no API access, no queries — and currently a logging bug that renders the most recent time series unusable.
Used correctly, it is the Google module of a larger measurement architecture: a manually secured baseline, reading trends instead of absolute values, comparison against your own citable assets, combined with cross-model tracking for the systems without analytics. Used incorrectly, it is a percentage generator for slides nobody can stand behind.
Set up the routine now, and in twelve months you will have an annotated, interpretable time series. Everyone else will have screenshots.