Your rankings held, your clicks fell, and Search Console won't tell you why. Google has been explicit that no AI-specific reporting is coming to Search Console, since AI Overviews run on core Search systems, so impressions on a page the Overview dominates land in the same rows as ten blue links. If you want to track Google AI Overviews separately from organic rankings, you have to build the separation yourself, out of parts Google never designed for the job. Think of this as the assembly manual: five methods and one scoreboard, plus the traps that make teams misread the whole thing.
Why the split is non-negotiable now
Blended numbers hide opposite stories. AI Overviews appear on roughly a quarter of queries, overwhelmingly informational ones, and where they show, clicks drop by as much as 58%. Since August, Google has also been expanding some Overviews to fill the entire results page, most consistently on definitions. A site can gain rankings and lose traffic in the same month, and a blended dashboard turns that into mush, where nothing looks obviously wrong and everything gets slowly worse.
Split the same data apart and it answers the question your team actually argues about. If it's a ranking problem, you fix content and links. If it's Overview absorption, you change which intents you chase and fight for the citation inside the answer. And if nothing is wrong and the surface just reshuffled, you can stop panicking. Those are three very different Mondays, and only the separation tells you which one you're having.
Method 1: Track three facts per keyword, never one
The foundational move is to stop letting "position 3" stand on its own. For every tracked query, record three facts: your organic rank, whether an AI Overview appears on that results page, and whether your domain is cited inside it. Modern rank trackers detect Overview presence as a SERP feature, and the better ones pick up citations along with it.
Those facts really are independent, which surprises people. You can rank first and be absent from the Overview sitting above you. You can also be cited in the Overview while ranking on page two, because Overview citations stopped correlating tightly with top rankings once AI selection got opinionated. Each combination calls for a different playbook, and averaging them into one visibility score throws the playbooks away.
Method 2: CTR at stable position, split by intent
Search Console gets useful again once you ask it the right question. For pages whose average position stayed flat, what happened to click-through rate over time? Pull the queries with stable positions across two comparable windows, and split them by intent before you read anything.
Teams skip the split, and it's the whole method. Informational queries with an Overview on top are where CTR bleeds, while commercial and navigational queries mostly keep their curves. Say your definition pages show stable positions with sagging CTR and your comparison pages hold both. That's answer absorption on display, mapped to exactly where it operates, and no amount of ranking work will buy those clicks back.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
Method 3: Annotate everything, then overlay
Attributing changes without a timeline is astrology. Keep a running log of the dates that move this system, such as changes to Overview expansion, Google's spam and core updates, AI Mode tests and the AI-engine model releases that shuffle the wider ecosystem. Then lay those dates over your CTR and click curves.
The payoff is speed of diagnosis. If a CTR step-change lines up with the August full-page expansion, there's no need for a forensic project, because the suspect already confessed on the calendar. Teams that annotate spend minutes on questions that cost teams without a log a whole quarterly review. Add each entry on the day the news lands, since a timeline you backfill is a timeline you guessed. Our guide to tracking published articles over time applies the same logging to each article's own timeline.
Method 4: A fixed prompt set, signed out, weekly
No tool sees every answer surface perfectly. For the gaps, use the practitioner method that keeps proving itself in every serious community thread on this topic: a fixed set of queries, checked on the default surface, signed out, every week. The consistency is the entire value. Change the prompts or the conditions between checks and you end up measuring your own curiosity instead of the trend.
Two refinements from the field are worth stealing. Run identity prompts before visibility prompts, asking the engine who your company is and what it does, because whether it knows you at all gates everything downstream. And check the logged-out default on purpose, since that's what buyers see before they've taught Google who they are. One operator in r/aeo described the mature version as a fixed prompt set run weekly across engines, comparing mentions, citations, ranking position and answer consistency in a simple spreadsheet until tooling takes over.
Method 5: One scoreboard, four columns
Put the methods together into a view a Monday meeting can use. Each tracked query gets four columns: organic rank, Overview present, cited in Overview, and CTR trend. That's the whole report. When rank fell and CTR fell, you have a classic SEO problem with classic SEO fixes. When rank held but an Overview appeared without citing you and CTR fell, you either fight for the citation or reweight the intent. And if rank held and you're cited but CTR is soft, you're winning the new surface, and that click was never coming back anyway.
This scoreboard is what RankControl ships as a product. Our tracking pairs AI Overview presence with per-page Search Console data and organic rankings in one weekly view, next to citations across ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews, because the Google split and the AI-engine split are the same discipline applied to different answer boxes. Teams run the manual version above for a month, learn what the columns mean in their category, and then decide whether those weekly hours are worth automating away.
Here's what the manual version costs. Setting up SERP-feature tracking takes an afternoon and the CTR analysis is a repeatable hour, while the weekly prompt-set check runs two to three hours across engines, plus a few minutes of annotation whenever news lands. A focused team can sustain that, but for an agency juggling clients it's brutal, which is why the spreadsheet era of this discipline keeps ending in tooling.
How often does ChatGPT mention your brand?
Most founders have no idea. The answer might surprise you.
A worked diagnosis, start to finish
Suppose a SaaS site notices organic clicks down 30% over eight weeks. The blended dashboard shows the decline and nothing else, so run the workflow.
The Method 1 tracker data shows the top 50 queries holding position. Overviews now appear on 22 of them, up from 9, and the domain is cited in 6. Method 2's stable-position CTR pull puts the entire bleed in the glossary and how-does-it-work cluster, while commercial comparison queries stay flat. The Method 3 overlay puts the step-change in the week full-page expansion reached definition queries, and the Method 4 prompt set confirms the identity prompts come back correct, with the brand appearing in the Overview for 6 tracked questions.
That's a diagnosis in twenty minutes. There's no ranking problem, absorption took the informational click, and the fight worth having is citation share on the 16 Overview queries where the domain is absent. Content effort moves from rebuilding pages that rank fine to making those 16 pages the extractable, verifiable sources the Overview selects, so the same decline now comes with a to-do list instead of a mystery.
What each scoreboard state tells you to do
Each state on the scoreboard maps to a play:
| Scoreboard reads | The play |
|---|---|
| Rank fell, CTR fell | Classic SEO: content, links, technical |
| Rank held, Overview present, not cited | Fight for the citation: direct answers, sources, schema |
| Rank held, cited, CTR soft | Won the new surface; shift the KPI to presence |
| Rank held, no Overview, CTR stable | Defend the ranking; this query still clicks |
The second row deserves its own note, because it's the growth lane most teams miss. Getting chosen into the Overview runs on the same extractability and authority work that wins citations in every other AI engine, so one content improvement pays off across surfaces.
The four traps that corrupt the data
The first trap is averaging across intents. One blended CTR number across informational and commercial queries erases the exact contrast that carries the signal, so split first and read second. The second is measuring while signed in. Your personalized, history-soaked results aren't your market's results, so log out and use a clean profile, and accept that even then you're sampling one region's view.
Single-snapshot conclusions are the third. Overview presence flickers with Google's testing, a keyword's Tuesday Overview may be gone by Thursday, and only the weekly series tells you what's structural.
The fourth is the oldest trap and now the most expensive: blaming rankings for CTR problems. Teams end up rebuilding content that ranks fine because the Overview above it absorbed the click, and the four-column scoreboard exists specifically to prevent that diagnosis.
Separate instruments, one discipline
Google made one page serve two systems and kept the reporting blended, which leaves the separation to you as homework. The homework is doable. Record three facts per keyword and read CTR at stable position split by intent, then keep the timeline maintained and run a fixed prompt set every week, with a scoreboard that keeps the stories apart. Run it all by hand and it works. Or let RankControl's agents run the tracking side every week, from AI Overview presence per keyword through AI citations, while your team spends its hours on the content the answers keep choosing.
Either way, stop reading blended numbers. They were never exactly lying to you, but they average the ranking story and the Overview story into one line that tells neither.
15 hours a week manually. Or 15 minutes with RankControl.
Track citations, monitor competitors, and fix content gaps across every AI search engine. Automatically.
