What Does the Search Console Generative AI Report Actually Tell You?

What is the Search Console generative AI report?

As of September 2026, Google Search Console includes a Search generative AI performance report. It shows impressions from generative AI features on Google Search, which today means AI Overviews and AI Mode. Google announced it on the Search Central blog in June 2026. It is the first view of this data from Google itself.

Before this report existed, everyone was guessing. Marketers pulled numbers from third party trackers. They compared those numbers to their own traffic and hoped the story lined up. Now there is a first party source. That changes the conversation in a lot of client meetings we sit in.

It also raises a fair question. Is the data good enough to act on? We have spent time inside the report and read Google's own documentation closely. The short answer is that it is useful, but only if you know what it counts and what it quietly leaves out.

Why does this report matter right now?

It matters because AI answers now sit between your site and a large share of searchers. Without first party data, teams could not tell whether AI surfaces were helping or hurting. This report gives you a number that comes straight from Google, not from a sample or an estimate.

The scale of the shift is easy to underrate. Similarweb's AI search report, published on 29 July 2026, found that AI platforms drew an average of 9.5 billion web visits a month worldwide between June 2025 and May 2026. That is roughly 70 percent growth year over year. People are clearly using these tools.

The harder question is what that means for your traffic. Pew Research Center studied 900 US adults who shared their browsing data in March 2025. When an AI summary appeared, people clicked a normal search result in 8 percent of visits. When no summary appeared, they clicked in 15 percent of visits. That is close to half the clicks.

So the pressure is real, and it is measurable. A report that tells you how often Google showed your links inside those answers is worth learning properly.

What exactly does the report measure?

It measures impressions. Google defines an impression here as the number of times links to your site were shown to a user inside a generative AI feature on Google Search. You can group that data by page, by country, by device, and by date, the same way you slice the normal performance report.

That framing is important. An impression is not a citation in the sense most people mean it. It means Google put a link to your page in front of someone inside an AI answer. Whether they read it, noticed it, or clicked it is a separate matter.

Google also states that when two results from the same site appear in the same generative AI feature, they count as a single impression. So the number is closer to "how many answers included us" than "how many links we earned". We think that is the more honest measure anyway, but it is easy to misread.

What does the report leave out?

It leaves out more than most teams realise. Google says Search Console does not include data from experiments in Search Labs. Anything still being tested there is invisible. Google Discover data sits in a separate report rather than this one. And sites that are excluded from generative AI features will not appear at all.

There are practical limits too. Google notes that not every property has access yet, because the rollout has happened over time. The newest data can be preliminary and may change within hours. The standard 1,000 row limit still applies, so a large site sees only the top slice. Chart totals and table totals can differ because they aggregate differently.

None of this makes the report useless. It does mean you should treat a week of fresh data as a draft rather than a finding. We wait for the numbers to settle before we tell a client anything changed.

Can you separate AI Overviews from AI Mode?

No, and this is the single biggest gap. Google's documentation combines AI Overviews and AI Mode into one set of metrics. There is no breakdown by individual feature. You see the total and nothing underneath it.

That hurts, because the two surfaces behave differently. AI Overviews sit on top of a familiar results page, so a user can scroll past them. AI Mode is a conversation, and the page of blue links is not really there. A page that performs well in one may do nothing in the other.

We have stopped pretending we can tell these apart from Search Console alone. When a client needs that split, we say plainly that Google does not publish it, and we look at behaviour on the landing page instead. Guessing a split and putting it in a slide would be inventing data.

How should you actually use this data?

Use it for direction, not precision. Pull the page level view and find which URLs Google keeps showing inside AI answers. Those pages are the ones Google already trusts for that topic. Then compare them to the pages you assumed would win. The gap between the two lists is the useful finding.

We usually start by exporting the page report and sorting by impressions. Then we read the top ten pages as a set. Almost every time there is a pattern. The winners tend to answer one clear question near the top, in plain language, with a specific number or definition. That is the same shape we describe in our guide to optimising for Google AI Overviews.

The second use is monitoring. Set a baseline now. If the number falls hard over a month, something changed, and you want to know before the traffic report tells you. Our wider notes on measuring AI search traffic cover how we join this to analytics data.

Does this replace third party AI visibility tools?

Not really. It replaces the guesswork about Google specifically. It tells you nothing about ChatGPT, Claude, Perplexity, or Microsoft Copilot, and those are a large and growing share of the market. You still need a second source if you care about the whole picture.

The market is also moving fast enough that a single tool view is risky. Similarweb's July 2026 report found that ChatGPT's share of generative AI web traffic fell from roughly 76 percent a year earlier to about 53 percent. Gemini climbed from under 9 percent to roughly 27 percent. Claude grew from about 2 percent to close to 9 percent.

So the answer engine your buyers use this year may not be the one they used last year. A Google only report cannot see that shift. We treat Search Console as the reliable half of the picture and accept that the other half needs separate tooling.

How do you connect this to real business results?

You connect it by pairing impressions with what happens after the click. Impressions tell you Google showed your link. Your analytics tell you whether anyone arrived and whether they did anything useful. Neither number means much on its own, and the report gives you only the first one.

This is where the click data matters. Pew found that people clicked a source link inside the AI summary itself in just 1 percent of visits. Pew also found that people ended their browsing session on 26 percent of pages with an AI summary, compared with 16 percent of normal results pages. High impressions with flat traffic is a normal outcome, not a bug in your setup.

Because of that, we push clients to value brand presence as well as clicks. Being named in the answer has worth even when nobody clicks. Similarweb reported that US citation rates across the platforms it tracks rose from 1.6 percent to roughly 6.8 percent over that same June 2025 to May 2026 window. Being in that set is the goal.

What should a small team do first?

Do three things. Confirm the report is available on your property, since the rollout reached properties at different times. Export the page level data and store it, because Search Console history is limited. Then pick your five most important pages and check whether they appear at all.

If they do not appear, the work is usually structural rather than clever. Clear question shaped headings. A direct answer in the first few lines under each one. Real numbers with the source named. Clean HTML that a crawler can parse without running JavaScript. Nothing here is new, but AI answers punish vague pages harder than blue links ever did.

If you want the wider setup right first, our Search Console guide covers property verification, the API, and the bulk export to BigQuery that makes long term tracking possible.

Where does this go next?

We expect the report to get more granular over time, because the pressure for a feature level split is coming from every serious publisher and marketing team. Google has shipped more reporting detail before when the demand was loud enough. Until then, treat the single combined number as a trend line rather than a diagnosis.

The teams that will do well are the ones building the habit now. Check the report monthly. Watch which pages Google trusts. Fix the ones it ignores. That work compounds quietly, and it is the same work that helps you in normal search anyway.

If you want a second pair of eyes on your Search Console data, or you are trying to work out why your best pages never show up in AI answers, we are happy to walk through it. You can find us at phoenix.studio.