The Search Console AI Report Gives You Impressions Only

A specific disappointment recurs whenever a site owner opens Search Console’s generative AI performance report for the first time. They expect a second version of the performance chart, with the familiar four metrics, split by AI surface. What they find is one metric and five dimensions, and no obvious way to turn that into a decision. The report is useful, but only if you are clear about what it is measuring.

The five dimensions, and nothing else

Google announced the reports on 3 June 2026 and set out the contents precisely. The Search Central announcement of the generative AI performance reports lists exactly five things the report shows:

• Impressions — how often URLs from your site appeared in generative AI features in Search and Discover.
• Pages — which URLs appeared within those features.
• Countries — your visibility on a country basis.
• Devices — which devices people were using, available for Search results only.
• Dates — hourly, daily, weekly and monthly granularity.

A note now sits at the top of that same post: “As of August 31, 2026, we’ve rolled out these insights to all websites worldwide.” Before that the reports went to a subset of sites while Google tested them, so if yours appeared recently, your history begins when your property was included rather than when the feature launched. That matters the first time you look at a year-to-date chart and see a cliff edge that is an onboarding date, not a traffic event.

No clicks and no position, so no CTR

Impressions are the only metric. There is no click column and no average position, which rules out the two calculations most people reach for. You cannot derive a click-through rate for AI Overviews or AI Mode, and you cannot chart rank movement inside them. Any tool or report that presents an AI click-through rate for your site is inferring it from somewhere else, and it is worth asking exactly where.

This is the practical constraint behind an AI search visibility strategy when you couldn’t measure it. The measurement gap narrowed in June and closed geographically in August, but it did not become a full performance report, and treating it as one produces confident numbers with nothing underneath them.

One view, not one per surface

The report covers generative AI features as a single group. Google’s wording is that it gives dedicated views of impressions within generative AI features on Search, such as AI Overviews and AI Mode, as well as generative AI features in Discover. There is no toggle that separates an AI Overviews impression from an AI Mode impression. If your reporting depends on the difference between AI Mode and AI Overviews, this report will not give it to you, and no filter in Search Console currently will.

These impressions are already counted elsewhere

The announcement is explicit that this data is included in the overall performance report, where it continues to be tracked, and that the new view is a separate lens on the same underlying impressions. Adding the generative AI total to your standard Search total therefore double counts. The correct read is the ratio: what share of your total impressions came from generative AI features, and how that share moves. That is also the number worth watching if you are weighing the Search generative AI control, which lets a property exclude itself from AI Overviews, AI Mode and generative AI features in Discover. Google’s documentation on the Search generative AI control states the default is inclusion and that exclusion means no traffic and no impressions from those features.

What impressions alone can support

Four conclusions survive those constraints, and they are worth stating narrowly because the report invites broader ones. Country skew: if one market produces a disproportionate share of generative AI impressions relative to its share of ordinary impressions, that is a real signal about where these features are dense for your queries. Page-level eligibility: the pages dimension tells you which URLs Google has been willing to surface at all, which is a different question from which pages rank. Device split: available for Search only, so read it as a Search observation and not a whole-site one. Date of onset: hourly granularity makes it possible to place the start of an impression pattern against a deployment or a publication date, which is the one thing a summary layer like the Insights report is not built to do.