When an AI Overview sits at the top of a Google results page and a user clicks a link inside it to reach your site, a reasonable person expects Search Console to record that as its own thing: an AI Overview click, distinct from a plain blue-link organic click. It does not. Understanding why, and what Google does and does not give you instead, is essential if you are trying to measure how AI search affects your traffic. The blunt version: Search Console cannot separate AI Overview clicks from organic clicks, and the newer AI report helps with impressions, not clicks. Let us walk through exactly what is available.
The short answer
No, Search Console does not distinguish AI Overview clicks from organic clicks. AI Overviews and AI Mode appearances are counted inside the standard Performance report under the Web search type, mixed in with all your other web-search clicks and impressions. Google’s Generative AI performance report adds a dedicated view of how often you appear in AI features, but it reports impressions only, is drawn from that same Web data, and is still a limited rollout (Google Search Console Help). So you can approximate how visible you are in AI features, but you cannot cleanly say “this many clicks came from an AI Overview”.
How Search Console counts AI Overview appearances today
Start with how the data is bucketed. Google confirms that sites appearing in AI features such as AI Overviews and AI Mode are included in the overall Search traffic and reported within the Web search type of the Performance report (Google Search Central). There is no separate search type for AI Overviews sitting alongside Web, Image, Video, and News. From Search Console’s perspective, an AI Overview appearance is just part of your Web presence.
The position logic reinforces this. Google documents that an AI Overview occupies a single position in the results, and all links within that overview are assigned that same position (Google Search Console Help). So an AI Overview does not create a new, separately labelled slot in your data; it folds into the existing position and click accounting.
What the standard Performance report shows, and hides
The practical upshot is that your familiar Performance report shows you totals that already contain AI Overview activity, without telling you how much. Your clicks number includes any clicks that came from links inside AI Overviews, blended with ordinary organic clicks. Your impressions include AI Overview appearances. There is no toggle, filter, or dimension in the standard report that isolates the AI Overview portion of either figure.
This is why teams get confused when they try to “find their AI Overview traffic” in Search Console and come up empty. It is not hidden in a menu you have not found; it genuinely is not broken out. The standard report was built around search types and queries, not around which feature on the page produced the click.
It helps to understand why Google structured it this way. From the search engine’s point of view, an AI Overview is a presentation of results, not a separate channel. The same page that ranks organically can also be pulled into the overview, so drawing a hard line between an “AI Overview click” and an “organic click” for the same URL on the same query would be somewhat artificial. That design choice is defensible, but it leaves marketers without the granularity they want, which is precisely the tension the separate generative-AI view is trying, partially, to resolve.
The new Generative AI performance report: what it adds
Google has responded to the obvious demand with a dedicated Generative AI performance report, which gives a view of your visibility specifically within generative AI features on Search. This is a real and useful addition, because for the first time it lets you see a slice of your AI-feature presence rather than only the blended total. If you have access to it, it is the closest thing to an official AI-visibility view Google offers.
But read its definition carefully before you build a strategy on it. The report tracks impressions, defined as how many times links to your site were shown to a user in a generative AI feature on Google Search (Google Search Console Help). It is about how often you were shown, not a separate ledger of clicks attributed to AI.
What the new report still does not do
Three limits matter. First, it is impressions-focused; it does not hand you a clean count of clicks attributable to AI Overviews as distinct from organic clicks. Second, it draws from the same Web search-type data as the standard report, so it is a dedicated view into existing data, not a wholly separate clicks pipeline. Third, it is a limited rollout: Google is releasing it to a subset of website owners for testing before wider availability, so many properties will not see it yet (Google Search Console Help). Treat it as a valuable impressions lens, not as the clicks breakdown people keep asking for.
Why clicks specifically are the hard part
Clicks are the hardest thing to attribute to AI features, and there is a structural reason. AI answers are designed to satisfy the user in place, so many AI Overview appearances produce an impression and no click at all. Pew Research Center found that users were much less likely to click when an AI summary appeared, around 8 percent clicking a result versus 15 percent without a summary, and only about 1 percent clicking a link inside the summary itself (Pew Research Center). When the defining behaviour of the feature is fewer clicks, a clicks-based metric is both scarce and noisy, which is part of why an impressions view is what Google surfaced first. The click-behaviour shift is unpacked further in click-through rates and AI Overviews.
What you can and cannot see in Search Console
This table sums up the current state.
| Question | Can Search Console answer it? |
|---|---|
| Total clicks including AI Overviews | Yes, blended in the Web search type |
| Only the clicks from AI Overviews | No, not separated from organic |
| How often you appear in AI features | Partly, via the Generative AI report (impressions, limited rollout) |
| AI Overview impressions vs organic impressions, split | No clean split; AI report is a dedicated view of Web data |
| Which query triggered an AI Overview for you | No, not exposed as a dimension |
How AI Overviews change the click you do get
Even the clicks you cannot isolate behave differently. Because an AI Overview answers much of the question, the users who still click are often further along and more intent-driven, and the pages that get cited tend to already rank well, with Ahrefs finding that a large share of AI Overview citations come from pages ranking in the top 10 (Ahrefs). So your blended clicks number can hide a shift in composition: fewer, higher-intent clicks rather than simply more or fewer. Judging AI impact by the raw clicks total alone misses this.
Workarounds to approximate AI-driven impact
Since a clean clicks split does not exist, triangulate. Watch impressions and clicks together: the classic AI fingerprint is impressions holding steady or rising while clicks soften, which suggests you are appearing in answers that resolve without a click. Use the Generative AI report wherever you have access, as an impressions signal. And pair Search Console with independent presence tracking, actually asking the engines your key queries, because that captures presence Search Console never attributes. This blended approach is the same philosophy behind are ChatGPT citations worth tracking: measure presence, not just clicks.
What to measure instead
Reframe the goal. Instead of chasing an AI Overview clicks number that Search Console will not give you, track three things: your impressions trend in Search, your visibility in the Generative AI report where available, and your presence in AI answers via independent checks. Together these tell you whether AI features are growing your visibility even when clicks flatten, which is the real question. The broader mindset shift from clicks to presence is covered in classic SEO versus AI visibility, and the traffic-diagnosis side in why is my ChatGPT referral traffic dropping.
A worked example
Say your Search Console clicks fell 12 percent quarter over quarter while impressions rose. Without understanding the AI Overview accounting, you might panic and assume you are losing rankings. But the blended clicks figure already contains AI Overview activity, and rising impressions with softening clicks is the textbook signature of appearing in AI answers that satisfy users in place. You check the Generative AI report, which you happen to have access to, and see your AI-feature impressions climbing. The correct read is not “we are losing” but “we are increasingly present in AI answers that reduce clicks”, which calls for a presence strategy, not a panic. That interpretation is only possible once you know Search Console is not separating the clicks for you.
Contrast that with the wrong path the same data invites. A team that believes Search Console should show AI Overview clicks separately sees the blended clicks drop, cannot find an “AI” line to explain it, and concludes the AI Overview is stealing traffic it can prove nothing about. They then either chase a phantom penalty or demand a report that does not exist. The team that understands the accounting reads the very same numbers as a healthy shift toward AI presence and invests accordingly. Same data, opposite conclusions, and the only difference is knowing how the clicks are bucketed.
Common misconceptions
The biggest misconception is that AI Overview clicks live somewhere in Search Console if you just find the right filter; they do not, they are blended into the Web search type. The second is that the new Generative AI report is a clicks breakdown; it is impressions, and a limited rollout. The third is treating a clicks decline as pure ranking loss when it may be the AI-in-place effect. The fourth is ignoring impressions entirely and steering only by clicks, which for AI features is exactly the wrong dial. Products and pages that never surface at all are a different diagnosis, covered in products not showing in Google AI Overviews.
The bottom line
Search Console cannot distinguish AI Overview clicks from organic clicks. AI feature activity is counted within the Web search type, the new Generative AI report adds an impressions view rather than a clicks split and is still rolling out, and clicks are the hardest thing to attribute precisely because AI answers reduce them. So stop hunting for a number that does not exist. Track impressions trends, use the AI report where you have it, add independent presence checks, and read the impressions-up-clicks-down pattern for what it is: evidence you are showing up in AI answers, even when the click never comes.
Frequently asked questions
Can I filter Search Console to show only AI Overview clicks?
No. There is no filter in the standard Performance report that isolates clicks originating from an AI Overview. Those clicks are counted within the Web search type together with all other web-search clicks, so you cannot separate them out.
What does the new Generative AI performance report actually show?
It shows impressions, meaning how many times links to your site were shown to a user in a generative AI feature like AI Overviews or AI Mode. It does not provide a clean clicks-versus-organic split, it draws from the same Web search-type data, and it is still rolling out to a subset of properties.
Are AI Overview appearances counted in my normal Search Console data?
Yes. Sites appearing in AI features are included in the overall Search traffic in Search Console and reported within the Web search type of the Performance report. An AI Overview occupies a single position, and all links within it are assigned that same position.
If I cannot see AI Overview clicks, how do I measure AI impact?
Track impressions trends over time, use the generative-AI report where you have access to it, watch for the classic pattern of impressions holding or rising while clicks soften, and pair Search Console with independent presence tracking across AI engines. Triangulate rather than expecting one exact number.
