Shahid Ali.WhatsApp

field note

Can you see AI Mode traffic in Search Console?

AI search

Shahid AliUpdated September 1, 2026all posts

Can you see AI Mode traffic in Search Console?

The short answer is that AI Mode traffic is already in your Search Console data and you cannot separate it out. Both halves of that sentence surprise people, usually in the same conversation. (Since 31 August that answer has a new half: impressions now get their own report, clicks still do not. The dated update below covers what changed.)

There is no AI Mode filter, no AI Overviews search type, and no search appearance row for either. Google documents where the data goes and how it is counted, which is enough to reason about, and stops well short of letting you isolate it.

Where the data actually sits

Google’s AI features and your website documentation is direct about this. Sites appearing in AI features such as AI Overviews and AI Mode are included in the overall search traffic in Search Console, reported in the Performance report, within the Web search type.

So the clicks and impressions you already look at include AI surfaces. They have not been withheld and they are not arriving later. They are folded into the same rows as classic blue links, and the Web search type is where they are.

That is the whole answer to “where do I find it”. Everything else is about what the numbers mean once you know they are mixed in.

How each one is counted

The counting rules are in Google’s impressions, position and clicks documentation, and the two features are not treated identically.

AI Overviews. A click on a link to an external page inside the AI Overview counts as a click. Standard impression rules apply. Position is the interesting one: the AI Overview occupies a single position in results, and every link inside it is assigned that same position. Ten links, one position, shared.

AI Mode. Clicks and impressions work the same way. Position follows the same methodology as a normal results page rather than collapsing to one value, and carousel or image blocks inside AI Mode use the standard position rules for those elements. There is one extra rule that matters more than it looks: if a user asks a follow-up question inside AI Mode, that is treated as a new query, and all the impression, position and click data in the new response is counted against that new query.

Neither. Search Console excludes data from Search Labs experiments, because those are still in development.

How Search Console counts each one AI Overviews AI Mode Click Link to an external page Link to an external page Impression Standard impression rules Standard impression rules Position One position, shared by every link Same as a results page Follow-up Not applicable Counted as a new query Search Labs Excluded from Search Console Excluded from Search Console

What that does to your numbers

Three consequences follow from the rules above, and all three show up as things people misread.

Average position gets compressed. If your page is one of ten links inside an AI Overview and that block sits at the top, every one of those links records the same strong position. A page can therefore report a better average position than the click behaviour suggests, because being in the block and being the link someone chose are different things.

Impressions rise faster than clicks. An impression means a user saw, or could have seen, a link. Inside an AI answer, being seen and being clicked have drifted much further apart than they were on a list of ten blue links. That produces the pattern I wrote about in lots of impressions but no clicks, and it now has a second cause on top of the old ones.

Query counts can move without demand moving. The AI Mode follow-up rule means one person’s single research session can register as three or four distinct queries. Nothing about search volume changed; the unit of measurement did.

What you can still do

You cannot filter for AI. You can still compare, and comparison is most of the value anyway.

Compare the same pages across the same weekdays over a long window, and watch the ratio of impressions to clicks rather than either number on its own. A page whose impressions hold while its clicks fall is behaving differently from a page losing both, and the two need different responses. Google’s own advice on this points to the debugging search traffic drops documentation for the general method, which is unchanged by AI features.

The second thing worth doing is checking real results by hand for your top queries. It takes ten minutes, it tells you whether an AI Overview is even present, and it is the only way to know whether the block is the explanation for anything. Data cannot tell you what the results page looked like. Looking at the results page can.

The limits of this on a small property

I ran the numbers on this site before writing, which is the honest way to test whether advice like this survives contact with a small property. Across 1 to 28 August 2026 it recorded 283 impressions and 3 clicks. At that volume there is nothing to analyse. A single AI Overview appearing or disappearing on one query moves a bigger share of the total than any change I could make to a page.

I am saying that because the analysis above needs volume to work, and a lot of writing about AI in search skips the part where the method needs enough data to be a method. If your property is in that range too, the right move is to keep publishing, keep the comparison window long, and treat week-on-week swings as noise until the base is bigger.

The other reason to know all this is that it settles a question clients ask constantly. There is no separate AI optimisation to do, and Google says as much: no additional requirements and no special optimisations to appear in AI Overviews or AI Mode. I went through that argument in do I need to optimise for AI Overviews, and the measurement side is the same story. The reporting is not hidden from you. It is merged, and merged is not the same as missing.

Update 1 September 2026: the generative AI reports are now worldwide

When I wrote this post, “no filter, no search type, no search appearance row” was the whole story. It no longer is. Google has added a note to its June announcement of the Search generative AI performance reports: “As of August 31, 2026, we’ve rolled out these insights to all websites worldwide.” The same note now sits on the report’s help page.

What the worldwide rollout gives you is a dedicated report in Search Console, one for Search and one for Discover, showing impressions from generative AI features: AI Overviews and AI Mode for Search, plus generative AI features in Discover. You can group them by page, country and date, Search adds a device breakdown, and the date granularity runs from hourly to monthly. The direct route is Performance and then the generative AI entry, or the report’s URL.

Three limits are worth being precise about, because they define what this report can and cannot settle:

  • Impressions only. The report carries no click data, so the click half of this post is unchanged: clicks from AI surfaces still sit merged in the Web search type, and you still cannot separate them. That limit matters more than it did, now that AI Overviews auto-expand on some queries and the impression count is the only thing that moves.
  • No per-feature split. AI Overviews and AI Mode are reported together as generative AI features. The counting differences described above still happen upstream, and you still cannot tell the two apart in the numbers.
  • A threshold applies. The help page says sites that have not received enough impressions in generative AI features may not see the report at all, and sites that opted out via the Search generative AI control will not accumulate the data that would populate it.

That last clause is worth checking before you conclude your report is broken, because the control is set at property level and inherits down to subdomains and paths. How the Search generative AI setting works covers where it lives and what it does and does not cover.

That last point is the small-property caveat from earlier in this post wearing a new coat. I pulled this property’s performance data again on 1 September through the Search Analytics API, which still returns only the merged web view: 606 impressions and 3 clicks across the trailing 28 days. At that volume, a dedicated AI impressions report has nothing to say yet, and Google’s threshold means small properties may not even be shown one. The advice stands: the report is worth opening monthly, and the merged comparison method above is still where the actual decisions come from.

Since the reporting will not tell you whether AI Mode is naming you, the measurement has to be built by hand. AI search visibility explains what to measure instead, and how to track brand mentions in AI search is the procedure.

The question that always follows is whether analytics can fill the gap. It cannot, and Google’s own channel definitions say so: tracking AI Overview traffic in GA4 sets out why the clicks arrive indistinguishable from ordinary organic ones.

Sources

Message me on WhatsAppRead the guides