What 9 Months of AI Overview Data and 51,000+ Tracked Events Reveal

Most brands still don't have a clear picture of how much traffic AI Overviews are sending them. Google hasn't given us a clean signal for AI Overview traffic in Search Console, making it difficult to know how much organic traffic is coming from AI Overviews, which content is driving it, and how accurately that traffic is being reported. This connects with Questions That Reveal Your Real Search Performance when the same signal needs a clearer operating decision.

Since September 2025, I've been capturing AI Overview referral data for one of the brands I manage in the transportation industry. From September 2025 to June 2026, we recorded 51,200 tracked events across 1,661 cited snippets.

The tracking setup, and why it works

The methodology is straightforward, but most teams haven't implemented it. When a user clicks on a cited snippet inside a Google AI Overview, Google sometimes appends a #:~:text= fragment to the destination URL. We created a custom. The search implication is whether the section improves the evidence around the page, not simply whether it adds more wording. Clear entities, crawlable structure, internal links, and useful context are what make the topic easier to evaluate.

The risk is usually hidden in the execution layer. A page can look fine to a human and still fail for an automated visitor if the form, call to action, rendering path, or confirmation step is not accessible enough for the agent to complete the task.

Certain topic types got cited

Transfer time content and pricing content are already being cited frequently with clear upward momentum. The play there is to refresh and expand the existing content. Destination guides are underperforming relative to what the data. The search implication is whether the section improves the evidence around the page, not simply whether it adds more wording. Clear entities, crawlable structure, internal links, and useful context are what make the topic easier to evaluate.

22.4% of AI Overview traffic is being misattributed to Direct

This was the most striking finding. When we started plotting the dataset on a GA4 exploration report, we noticed that a meaningful portion of traffic arriving via AI Overviews was being attributed to the Direct channel rather than Organic. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path. The same pattern also shows up in AI Is Merging Paid and Organic Visibility, where the practical question is how the signal becomes visible.

The reporting question is whether this signal changes a decision. If it only creates another number in a dashboard, it adds noise. If it helps separate profile activity, website visits, calls, bookings, and direction requests, it can make local performance easier to understand.

AI Overviews are driving 7.53% of organic sessions, but it's volatile

Using the same first party dataset, we built a percentage metric to track what share of our total organic sessions came from AI Overviews each period. From September 2025 to June 2026, 7.53% of organic sessions came from AI Overviews. At. For search teams, the important part is not the headline movement by itself. It is whether the shift changes which communities, forums, video surfaces, or publisher pages now satisfy the query better than the old ranking pattern.

The useful check is whether this improves the system behind search performance, not only the words on the page. Internal links, crawlable content, clear entities, current evidence, and a sensible page structure all help the recommendation become easier to trust.

The caveats you should know

Two important limitations with this approach:. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.

The practical value is in connecting the idea to an observable signal. That means deciding what should be checked, what would prove the issue is real, and where the team should make the smallest useful improvement first.

The #:~:text= identifier isn't exclusive to AI Overviews

The same fragment is used by Featured Snippets and People Also Ask results. So some portion of what we're capturing may bleed from those formats. We did run the exercise in Ahrefs to check our Featured Snippet exposure, and at the time of. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.

The metric compares events to sessions

Our custom dimension in GA4 is event scoped, not session scoped. The AI Overview share percentage therefore compares events against sessions, which isn't an ideal comparison. It's better than nothing, and it's directionally accurate, but. The search implication is whether the section improves the evidence around the page, not simply whether it adds more wording. Clear entities, crawlable structure, internal links, and useful context are what make the topic easier to evaluate.

What this means practically

If you're not tracking this yet, start. The setup isn't complex, and the signal, imperfect as it is, is the best first party data you'll get until Google decides to surface this natively. A few things to take away from nine months of. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path. A useful companion note is It’s Layering on Top, because it looks at a nearby part of the same system.

The tracking setup, and why it works in practice

Introduction Most brands still don't have a clear picture of how much traffic AI Overviews are sending them. Google hasn't given us a clean signal for AI Overview traffic in Search Console, making it difficult to know how much organic. For search teams, the important part is not the headline movement by itself. It is whether the shift changes which communities, forums, video surfaces, or publisher pages now satisfy the query better than the old ranking pattern.

What the visibility signal actually changes

What the visibility signal actually changes: what 9 Months of AI Overview Data and 51,000+ Tracked Events Reveal: the Practical Angle should be treated as a visibility signal, not a standalone headline. Introduction Most brands still don't have a clear picture of how much traffic AI Overviews are sending them. Google hasn't given us a clean signal for AI Overview traffic in Search Console, making it difficult to know how much organic traffic is coming from.

What the visibility signal actually changes: the practical question is whether the page, brand evidence, and surrounding content make the answer easier to trust. If that support is weak, search systems can still understand the topic but fail to connect it confidently to the brand.

What the visibility signal actually changes: that is why the response should begin with an audit of the evidence already on the site before creating a new asset. The fastest improvement is often a clearer page, a better internal link, or a stronger explanation of why the brand belongs in the answer.

Where the evidence needs to be tested

Where the evidence needs to be tested: a single study or ranking observation should not become a strategy by itself. It should become a diagnostic prompt: which source is being trusted, which query pattern is affected, and which part of the site would make that trust easier to earn?

Where the evidence needs to be tested: that keeps the response grounded. The goal is to improve the evidence chain around the topic rather than publish another summary that repeats what every other page already says.

Where the evidence needs to be tested: the important distinction is between a useful signal and a fashionable talking point. A useful signal changes the brief, the page structure, the linking plan, or the measurement view.