Did Your AI Overview CTR Really Crash 61%—or Did Google Just Show You More Often?
- All things tech
- May 19
- 6 min read

You open Search Console, see “CTR down 61%,” and your soul briefly leaves your body. Before you start drafting the “Google killed SEO” group chat message, take a breath and do the least dramatic thing possible: check your impressions and clicks by month. Seer Interactive looked at 5.47M queries across 53 brands and found something super awkward for panic—CTR fell hard from Q3 to Q4, but clicks barely moved . So… did performance actually crash, or did Google just put your pages in front of way more eyeballs?
The “61% CTR drop” headline: what it is (and what it isn’t)
That “CTR down 61%” number looks like your site just face-planted off the SERP. But CTR is a ratio, not a mood. It’s literally:
CTR = clicks ÷ impressions
So if Google starts showing your result way more often (impressions spike) and clicks stay about the same, your CTR can fall off a cliff… even though your traffic didn’t. That’s the whole trap with AI Overviews (AIO): they can change what “normal” visibility looks like overnight, and CTR takes the blame.
Seer Interactive’s study is the reason this headline is everywhere. They looked at brand-cited pages in AI Overviews across 5.47 million queries and 53 brands and found the attention-grabbing part: CTR fell 61% from Q3 to Q4.
Here’s the part people skip when they’re panic-scrolling: clicks “barely moved.”So the story isn’t “your SEO stopped working.” It’s closer to “Google changed how often it puts you in the room.”
What the headline is
A big, blended, quarter-over-quarter number that reflects a real shift in AI Overview visibility. Seer’s data shows impressions ramping hard in Q4, which changes the math on CTR.
What the headline isn’t
It’s not proof that:
Your content suddenly got worse
Your rankings collapsed
Your clicks dropped 61%
Because CTR can drop for a “good” reason (more impressions) or a “bad” reason (fewer clicks), and that 61% doesn’t tell you which one happened until you break it down.
If you’re trying to make sense of your own Google Search Console AI Overviews CTR drop, treat that scary percentage like a smoke alarm—not the fire itself. The fire (if there is one) shows up when you look at impressions and clicks together, month by month.
Month-by-month: September calm, October impression tsunami, November… weirdness
If that 61% number felt like a jump-scare, zoom in. The month-by-month view is where the story stops being “SEO is doomed” and starts being “wait… what exactly changed on the SERP?”
Seer broke out brand-cited pages in AI Overviews by month, and the pattern is hard to miss.
September: the “normal” baseline
September looks like what you’d expect when things are steady:
Impressions: 15.8M
Clicks: 398,798
CTR: 2.52%
Nothing to argue with here. Solid visibility, solid click-through rate, life is fine.
October: impressions go wild, clicks shrug
Then October shows up like Google hit a big red button.
Impressions: 33.1M (about double)
Clicks: 400,271 (basically the same as September)
CTR: 1.21%
So if your Search Console report screams “CTR dropped,” it’s not automatically a content problem. October is what “impression growth outpacing clicks” looks like in real life. Seer calls it a math issue, not a performance collapse.
November: visibility up again… but clicks drop
November is where it stops being a clean math story and gets awkward.
Impressions: 39.5M
Clicks: 301,783
CTR: 0.76%
That’s “more showing, less going.”
And Seer’s point is painfully relatable: something pulled clicks down while visibility increased, and their dataset can’t say exactly why.
If you’ve been staring at your AI Overviews CTR drop thinking, “Okay, but what did I do wrong?”—this is why the next step isn’t rewriting your top pages. It’s figuring out whether your impression spike came from Google showing AI Overviews on more queries… or from you showing up on more of them.
Before you blame your content: the thing Seer can’t prove (and why it matters)
Here’s the maddening part: even with millions of queries, Seer still can’t answer the question you actually care about.
When October impressions spiked, Seer couldn’t determine what caused it. Not “didn’t try.” Literally can’t tell from the data.
They call out two explanations, and both make perfect sense:
Option A: Google expanded AI Overviews coverage (you got swept up)
Google may have started showing AI Overviews for more queries where your brand was already being cited.
In that case, your “AI Overviews impressions” jumping isn’t really you winning. It’s Google putting the same players into more games.
Option B: You earned more AI Overview citations (you actually improved)
The other possibility: your SEO work led to more brand citations inside AI Overviews, which naturally increases impressions for brand-cited pages.
Same outcome in Search Console. Totally different meaning.
Why this matters (aka: don’t let a dashboard roast you)
Because this is where a lot of teams make a bad call, fast.
If you assume it’s Option B when it’s actually Option A, you might:
celebrate “visibility growth” that’s basically a Google UI change
scale a content plan based on a mirage
If you assume it’s Option A when it’s actually Option B, you might:
rewrite pages that are doing fine
kill a strategy that’s starting to earn citations
Seer’s takeaway is basically: your reporting can’t always separate “we got better” from “Google changed the game board.”So before you rip up your content calendar, you need to look at this at a query level and a month level, not one blended CTR line that’s yelling at you in all caps.
How this lines up with other studies (aka: you’re not imagining the CTR pain)
If you’ve been watching your AI Overviews CTR slide and thinking, “Cool cool cool, is it just me?” — it’s not just you.
Different datasets, different countries, different methods… and they keep bumping into the same annoying theme: when AI Overviews show up, people click less.
1) Ahrefs: AI Overviews aren’t “rare” anymore
Ahrefs looked at a massive set of results (146 million) and found AI Overviews showed up on about 21% of searches (a 20.5% trigger rate).
That matters because a CTR drop isn’t just a weird edge case if AIOs are popping up on a chunky slice of queries. If your site leans informational (guides, definitions, “how to” stuff), you’re basically living where AIOs like to hang out.
2) SISTRIX: even position #1 can get smacked
SISTRIX reported that in Germany, when AI Overviews appeared, the #1 organic result’s CTR dropped 59%.
So yeah—“but we rank first!” isn’t the shield it used to be on an AIO SERP.
3) Pew Research: real users, real fewer clicks
Pew found Google users clicked 8% of the time when an AI summary appeared, versus 15% without.
That’s not a rounding error. That’s a behavior shift.
The practical takeaway (so CTR doesn’t mess with your head)
Treat “CTR down” as a prompt to separate these two stories:
Visibility went up (impressions increased because AIO coverage expanded, or you got cited more)
Traffic went down (clicks fell because the AIO answered enough for people to bounce)
CTR alone can’t tell you which story you’re in. You’ve gotta track impressions and clicks like two separate characters, not one blended score that ruins your day.
What to do next: a simple Search Console workflow so you don’t spiral
At this point, you’ve got enough evidence to do the calm, grown-up thing: stop staring at blended CTR and start slicing your Google Search Console data like you actually want answers.
Seer’s own takeaway is basically “don’t lump Q4 together and freak out.” The months behave differently, so your analysis has to match that.
Step 1: Segment by month (yes, it’s that basic)
In Search Console → Performance → Search results, set the date range to a single month (ex: Oct 1–31), then repeat for the next month.
Why: Seer points out that the scary Q4 CTR headline is a blend of different month-level patterns, and you only see that when you separate the months.
Quick checks to record each month:
Impressions
Clicks
CTR
(Optional) Average position
Put them in a simple sheet. No fancy dashboard needed.
Step 2: Classify what’s happening (so you stop arguing with vibes)
Once you have month-by-month totals, bucket what you’re seeing:
Impressions up + clicks flat = classic “visibility expanded faster than demand”
Impressions up + clicks down = “people are seeing you, then not choosing you”
Seer explicitly warns that a falling CTR doesn’t automatically mean you’re losing clicks, so this is how you confirm what’s real.
Step 3: Add one extra metric: citation coverage
CTR tells you how often people click. It does not tell you whether AI Overviews are actually featuring you.
So add a metric that answers: How often are we cited vs. just shown?
Seer calls out the need to separate visibility, clicks, and citation coverage before making big decisions about AI Overview exposure.
A simple way to track it (low-tech on purpose):
Pick a stable set of queries you care about (brand + non-brand).
Check the SERP manually (or with your usual tracking tool) and log:
AIO present? (Yes/No)
Your brand cited in AIO? (Yes/No)
Your page linked/cited? (URL)
It’s a little annoying. It’s still less annoying than rewriting half your site because one percentage looked scary.



Comments