What is AI Overviews traffic loss?<\/h2>\n
AI Overviews traffic loss is a decline in organic clicks caused by Google's AI Overview answering a query directly, while your page's ranking position stays the same.<\/strong> Demand is unchanged, your impressions hold, but users read the AI summary and don't click through. It is a click-side<\/em> loss, not a ranking-side<\/em> loss.<\/p>\n That distinction is the whole game. A ranking drop reduces clicks because fewer people see you or you sit lower on the page. AI Overviews traffic loss reduces clicks even though nothing about your position changed\u2014the AI answer absorbs the intent above the blue links. Because both end in the same symptom, teams routinely misdiagnose one as the other and spend months rewriting content that already ranks fine. Getting the attribution right is the difference between a citation strategy and a wasted quarter.<\/p>\n Both problems produce the same headline number: clicks down.<\/strong> Open GSC, see clicks falling on an informational query, and your instinct is to check rankings\u2014but the loss may have nothing to do with position.<\/p>\n The click-side pressure is well documented. Pew Research Center found users clicked a traditional result in just 8% of searches with an AI summary, versus 15% without one<\/strong>\u2014roughly half as often\u2014and clicked links inside<\/em> the summary only 1% of the time, from its analysis of 68,879 U.S. Google searches<\/a>. Ahrefs measured the same effect at scale: an AI Overview correlated with a 34.5% lower click-through rate<\/strong> for the top organic result across 300,000 keywords<\/a>. None of that touches your ranking. It is why a page can hold position 2 and still bleed clicks\u2014and why raw click trends alone can't tell you which lever to pull.<\/p>\n AI Overviews also don't hit every query equally. They trigger most on informational and how-to searches<\/strong>\u2014the top-of-funnel queries most content teams built their traffic on\u2014and far less on transactional or navigational ones. If your losses cluster on "what is," "how to," and "best way to" queries while your product and pricing pages hold, that pattern itself points toward AI absorption rather than a sitewide ranking problem.<\/p>\n Position in GSC is no longer a clean signal, because AI Overviews change how impressions and position are counted.<\/strong> When your URL appears in an AI Overview, Google assigns that AI Overview a single position, and every link inside it inherits that same position. When the same URL<\/em> also appears as a blue link, GSC records it as one impression at the topmost position<\/strong>, per Google's documentation on impressions and position<\/a>.<\/p>\n Here is the trap. If you are cited inside an AI Overview near the top and<\/em> your organic blue link has slipped to position 8, GSC may report an average position of ~1\u2014not 8. Your reported position can look stable or even better<\/strong> while your real organic rank quietly falls. So the popular "position unchanged, therefore AI Overviews" test can fire on a page whose ranking actually dropped, and can miss a genuine slip that an AI citation is masking. Any method that leans on reported position as the truth inherits this blind spot. The fix is to stop trusting position as a verdict and start using it as one input among several.<\/p>\n The common diagnostic says: if impressions stay within \u00b115% and clicks fall more than 20% while position holds, blame AI Overviews.<\/strong> It is a fine first filter and correctly flags many clean cases.<\/p>\n It breaks in two situations. First, the mixed case<\/strong>: an AI Overview appears and<\/em> your ranking drops in the same period. Impressions may still look stable, so the test blames AI Overviews and hides the ranking problem you also need to fix. Second, the position-blending case<\/strong> described above, where a citation inflates your reported position and a real slip goes unseen. Both failures share a root cause: the naive test treats raw clicks and reported position as independent, trustworthy facts. They aren't\u2014clicks depend on position, and position is now contaminated by AI features. To separate the two forces cleanly, you need to compare actual clicks against the clicks a given position should<\/em> deliver.<\/p>\n The CTR-deficit method attributes lost clicks by comparing actual clicks to the clicks your reported position should have earned.<\/strong> CTR deficit is defined as: The insight is that a ranking drop explains itself<\/em>\u2014move from position 3 to 7 and your clicks fall to roughly what position 7 normally earns, so the deficit stays small. AI Overviews traffic loss does the opposite: your position stays put but clicks collapse far below its normal yield, producing a large deficit at a stable position<\/strong>. That gap is the fingerprint. Instead of eyeballing three columns and hoping, you get a single percentage per query that says how much click loss the position cannot<\/em> account for. Run it in four steps.<\/p>\n Use your own site's historical click-through rates by position, not a generic industry curve.<\/strong> Export 12\u201316 months of query data from GSC, ideally weighted toward periods and queries where AI Overviews were absent, and average CTR at each whole position (1, 2, 3, 5, 8). Your baseline might look like 28% at position 1, 15% at position 2, 11% at position 3, 6% at position 5, and 2.5% at position 8.<\/p>\n Build it separately for desktop and mobile<\/strong>, and for branded versus non-branded<\/strong> queries\u2014branded CTRs run far higher and will distort a blended curve. This baseline is what "normal" means for your site, and every deficit calculation depends on it.<\/p>\n Multiply each query's impressions by the baseline CTR at its reported average position to get expected clicks.<\/strong> A query with 12,000 impressions at position 1.4 (baseline \u2248 25%) has an expected 3,000 clicks. Compare that to the actual clicks GSC reports for the same query.<\/p>\n Do this at the query level<\/strong>, not the page level\u2014AI Overviews trigger per query, so a page can lose clicks on one query and hold them on another. Pull impressions, clicks, and average position for your top 50\u2013100 queries over a 90-day window against the prior year.<\/p>\n A high CTR deficit only means AI Overviews traffic loss when the position is stable; when position moved, the deficit must be read against that move.<\/strong> This 2\u00d72 turns two numbers\u2014position change and CTR deficit\u2014into a verdict, and it is where the mixed case finally gets its own box.<\/p>\nWhy AI Overviews traffic loss looks exactly like a ranking drop<\/h2>\n
![\"Line](\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/07\/1784286455764-0-55764-1.jpg\")
<\/figure>\nThe signal most guides get wrong: what GSC actually counts<\/h2>\n
The naive test\u2014and where it breaks<\/h2>\n
The CTR-deficit method: attributing click loss with a number<\/h2>\n
1 \u2212 (actual clicks \u00f7 expected clicks)<\/code>, where expected clicks = impressions \u00d7 your baseline CTR at that query's reported position<\/code>. In plain terms, it is the share of your position's rightful clicks that never showed up.<\/p>\n\n
Step 1: Build your position-CTR baseline<\/h3>\n
Step 2: Compute expected versus actual clicks<\/h3>\n
Step 3: Cross-tabulate deficit with position change<\/h3>\n
![\"Decision](\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/07\/1784286455764-0-55764-2.jpg\")
<\/figure>\n