The situation
Organic clicks dropped, and "AI Overviews ate it" became the explanation in the room within about five minutes - repeated in the next three meetings without anyone opening Search Console to check.
Why it's a real problem
If the real cause was a ranking loss, a technical issue, or seasonality, blaming AI Overviews means the actual problem goes unaddressed while everyone waits for a channel shift that was never the cause. You are one leadership meeting away from a strategy built on an unverified assumption, in either direction.
What we implement
We join your Search Console position and impression data with segmented AI referral traffic and AI crawler-log activity, at the query level, to test the AI Overviews explanation against the alternatives - a specific slice of AI traffic measurement, not a general audit.
What you get
- A tested answer instead of a shared assumption, with the method attached so it can be re-run next quarter.
- Query-level visibility into which pages lost clicks to an overview versus a ranking or seasonality shift - not a single property-wide verdict.
- A defensible answer for the next time this comes up, instead of re-litigating the same guess every quarter.
Illustrative scenario
A publisher convinced a core algorithm update caused a click drop might find, on inspection, that the pattern lines up query-by-query with AI Overview appearance instead - the queries that lost clicks are exactly the ones that gained an overview. (Illustrative scenario - not a measured result.) The other direction is just as possible; that is why it gets tested rather than assumed.
Where this leads next: if AI Overviews genuinely is the cause on a set of queries, the overlap between existing SEO strength and overview citation - covered in the AI Overviews guide - is the next thing worth reading.