Search Console Doesn't Separate AI Overviews Traffic, Google Documentation Confirms

What the Documentation Says, and What It Doesn't Say

The "AI features and your website" page from Google Search Central was updated on December 10, 2025, and is the official reference for how AI Overviews and AI Mode behave from the perspective of content publishers. The part that matters to growth teams is in the performance measurement section: sites that appear in these AI responses "are included in Search Console's overall Search traffic" and "reported in the Performance report, under the Web search type."

This is the opposite of what this article's original premise assumed. According to the documentation itself, there is no dedicated "search appearance" filter for AI Overviews that separates this traffic from classic organic results. Clicks and impressions generated by an AI response are added, without visible distinction, to the Web metrics that any site has already been tracking for years.

Why Google Doesn't Isolate This Number

The technical explanation is on the page itself: AI Overviews and AI Mode may use a technique called query fan-out, in which the system fires off multiple related searches across different subtopics and data sources to assemble a single response. A click that lands on your site may originate from one of these sub-searches, not from the original query the user typed.

In addition, AI Overviews only appears when Google's systems judge that it adds value over classic search, and it "frequently isn't triggered." Since AI Overviews and AI Mode use different models and techniques from each other, the set of links shown varies from one feature to another. Separating this source would require exposing internal decision logic that Google has historically not detailed even for technical SEO.

No Extra Technical Requirement, But the Bar Stays the Same

Eligibility to appear as a supporting link in AI Overviews or AI Mode follows a simple bar: the page needs to be indexed and eligible to appear in search with a snippet, meeting Google Search's standard technical requirements. There's no additional checklist. In practice, the best practices that already applied to traditional SEO remain the path forward:

• Allow crawling in robots.txt and in any CDN or hosting infrastructure
• Make content easy to find via internal links
• Ensure a good page experience
• Keep important content available in text format
• Support the text with quality images and videos, when it makes sense
• Ensure structured data matches the visible text on the page
• Keep Merchant Center and Business Profile information up to date

Structured data here isn't a ticket into AI Overviews: it's part of the same package of fundamentals that already underpinned rich results and featured snippets. Anyone treating this as a separate "GEO requirement" is repackaging an old practice under a new name.

How to Approximate Before-and-After Measurement Today

Without a dedicated filter, the way forward is combining indirect signals within what Search Console already offers. A reasonable roadmap for a growth team:

1. In the Performance report, keep the filter set to search type: Web (that's where all of this is counted) and compare the same date range before and after a relevant change, such as adopting structured data in an article template.
2. Segment by country (Brazil) and, if volume allows, by device, since AI Overviews tends to behave differently between mobile and desktop.
3. Watch the behavior of long-tail and informational queries, the search profile most associated with AI Overviews according to Google's own documentation.
4. Look at CTR and average position together, not in isolation: a drop in CTR with a stable position is the most common sign that an AI response is capturing the click before the user reaches the list of links.
5. Cross-reference the data with Google Analytics, focusing on time on site and navigation depth for sessions coming from organic search.

This last point has direct support from the source. Google itself states that clicks originating from pages with AI Overviews tend to be higher quality:

We've seen that when people click from search results pages with AI Overviews, these clicks are higher quality (meaning, users are more likely to spend more time on the site).

Google Search Central, official documentation

If CTR drops but average session time rises for the same set of pages, that's an indication (not proof) that part of the traffic lost at the click level is being offset by more qualified visitors coming from AI Overviews.

Controlling Appearance Is Different From Measuring Appearance

It's worth separating two problems that the documentation treats as a single topic but that call for different tools. Measuring impact is the challenge this article addresses; controlling whether content enters an AI response or not has specific, well-documented mechanisms:

None of these controls generates a separate performance data point. They decide whether the page can be used, not how much traffic it generated through this channel.

What Remains Open

The documentation links to other materials on "how AI Overviews and AI Mode are counted in Search Console's overall data" and on how to combine Search Console and Analytics, but it doesn't provide, on its own, a reporting dimension that separates this traffic. As of December 2025, there's no sign that Google intends to open up this breakdown. For growth teams in Brazil, this means treating GEO as a trend reading over the Web set, cross-referenced with Analytics and with long-tail query behavior, rather than as an isolated metric with a closed number at the end of the month.