If impressions are up, clicks are down and average position is holding, you’re most likely looking at an AI Overviews traffic drop, and some of those clicks aren’t coming back. Recovery doesn’t mean winning back every click. It means finding which pages lost valuable traffic, defending those, getting cited where you can’t win the click, and measuring what the remaining traffic is worth.
How AI Overviews change the click
An AI Overview answers the question near the top of the results page and links a handful of sources inside the summary, pushing the classic results down. For someone who wanted a definition or a quick answer, the search ends there.
That produces a recognizable pattern in Search Console:
- Impressions flat or up. Your page still ranks, and a page linked inside the overview can earn an impression there too.
- Average position flat or better. Nothing is wrong with your ranking.
- CTR and clicks down. Fewer people need to scroll to you.
Two caveats. Search Console doesn’t separate AI Overview or AI Mode traffic; it’s folded into web search totals, and all links in an overview share a single position. And overviews aren’t the only thing taking clicks. Ads, video carousels, “People also ask” boxes and forum results do it too, so check the results page before blaming the overview.
Diagnosing which pages and queries lost traffic
Step 1: Rule out the other causes
- Seasonality. Compare year over year, not month over month.
- Tracking. If GA4 shows the drop but Search Console doesn’t, it’s usually a tag, consent or attribution problem.
- Ranking losses. If position fell, look at competition, algorithm updates or technical issues, which need a different fix.
- Reporting changes. In September 2025, Google stopped supporting the
num=100URL parameter many rank trackers used to load 100 results per page, and many sites saw impressions fall and average position improve with no real change in demand. A year-over-year comparison that crosses that date will be skewed.
Step 2: Compare periods by page
In Search Console, open Performance > Search results, choose Date > Compare, and set the last three months against the same three months a year earlier. Turn on all four metrics, open the Pages tab, sort by the clicks difference and export.
Label each page by pattern:
| Pattern | Likely cause | Next step |
|---|---|---|
| Impressions flat or up, position flat or up, CTR down | AI Overview or another results-page feature absorbing clicks | Check the results page, then triage |
| Position down, clicks down | Ranking loss | Technical and content review, not a GEO fix |
| Impressions down, position stable or better | Less demand, or the 2025 reporting change | Check seasonality and query trends |
| GA4 organic down, Search Console clicks stable | Tracking or consent issue | Audit tags and consent settings |
Step 3: Drill into queries
Click an affected page, then open the Queries tab to see which queries lost clicks. Two filters under Query > Custom (regex) help isolate the searches overviews commonly answer. Question-style queries:
^(what|how|why|when|where|which|who|is|are|can|does|do|should)\bAnd long queries of five words or more:
^(\S+\s+){4,}\S+$If most of the lost clicks sit in question-style and long queries while short commercial queries held steady, that points to AI Overviews.
Step 4: Check the actual results page
For the top 10 to 20 lost queries per page, search in a clean browser session set to your target market. Record whether an overview appears, whether you’re cited, which sources are, and what else sits above you. Overviews don’t show every time, so check twice. Many rank trackers now log overview presence and cited domains.
Queries worth defending vs letting go
Not every lost click was worth having. Pull key events by landing page from GA4’s Landing page report, filtered to Organic Search, for both periods, then sort the lost queries by type:
| Query type | Example | Does the overview finish the job? | Decision |
|---|---|---|---|
| Definitions and quick facts | “what is a UTM parameter” | Usually | Let the click go; aim for the citation |
| Simple how-to | “how to add a user in GA4” | Mostly | Let go unless the page converts |
| Complex how-to and calculations | “how to calculate CAC payback by channel” | Partly; the reader still has to do the work | Defend with a tool or template |
| Comparisons and “best X for Y” | “HubSpot vs Salesforce for a 20-person sales team” | Summarizes, but buyers verify before deciding | Defend hard |
| Pricing and cost | “how much does X cost” | Gives a range; buyers want specifics | Defend with real numbers |
| Your brand and product | “[brand] pricing”, “[brand] vs [competitor]” | Uses whatever sources it finds | Defend; you should be the source |
Letting go doesn’t mean deleting. A definition page cited in overviews still builds visibility and may earn links. You just stop investing in it beyond keeping it accurate.
My rule when I triage these: defend a page if it produced key events or pipeline in the prior period, or if it targets a query one step from a buying decision. Everything else gets a citation check and nothing more.
Getting cited inside AI Overviews
When you can’t win the click, win the citation. It keeps your brand in front of the searcher and still earns some visits.
Google says there are no extra requirements for AI Overviews beyond being indexed and eligible to show with a snippet. On each defended page, I check:
- Snippet eligibility.
nosnippet,data-nosnippetand restrictivemax-snippetvalues limit how your content can appear in AI features and shrink your regular listing too. Remove any added by accident. Blocking Google-Extended in robots.txt doesn’t affect Search, including AI Overviews. - Sub-question coverage. Google says AI Overviews and AI Mode may run several related searches (query fan-out) to build an answer. Pages that also answer the obvious follow-ups, such as cost, time, steps and exceptions, have more chances to be retrieved.
- Answer-first passages. Put a direct 40 to 60 word answer right under a heading phrased the way people search.
- Specific, checkable claims. Numbers, steps, named tools and conditions. Vague copy gives the overview nothing to cite.
- The gap against current sources. Open the overview, read the cited passages and ask what they state that your page doesn’t. Usually it’s a clearer definition, a number or a step you buried.
- Freshness where it matters. Update prices, versions, screenshots and dates on pages where recency is part of the answer.
Most of this overlaps with good SEO. GEO vs SEO covers where the two diverge.
Content formats AI can’t fully replace
A summary replaces information. It doesn’t replace something you use, data only you have, or a judgment the reader trusts. Shift defended pages toward those:
| Format | Why a summary doesn’t replace it | Example |
|---|---|---|
| Calculators and tools | The reader needs their own numbers, not the formula | CAC payback or ROI calculator |
| Templates and files | The value is the file, ready to use | Spreadsheet model, checklist, brief template |
| Original data | The overview can cite a figure, but the full breakdown lives with you | Benchmarks from your own anonymized data |
| Hands-on comparisons | Buyers want proof you’ve used both options | Side-by-side with screenshots and test results |
| Opinionated recommendations | Readers want to know who is advising them | “What I’d choose at your stage, and why” |
A worked example with made-up numbers: a guide for “how to calculate CAC payback” loses half its clicks once an overview shows the formula. You add a calculator and a downloadable model. The overview still gives the formula, but readers who want to run their own numbers now have a reason to click, and the tool earns links.
Keep the core answer on the page as text. A calculator with no explanation is hard to cite.
Measuring value beyond clicks
If organic sessions are your headline KPI, every report will look worse than the business reality. Use a small scorecard instead:
| Metric | Where | What it tells you |
|---|---|---|
| Organic key events and pipeline by landing page | GA4, CRM | Whether the traffic you still get does its job |
| Organic conversion rate | GA4 | Whether remaining visitors are higher intent |
| Impressions on defended queries | Search Console | Visibility, even when clicks fall |
| Citation rate on a tracked query set | Manual checks or a rank tracker | Whether you’re in the answer |
| Branded search impressions | Search Console, filtered to brand terms | Demand the overviews may be creating |
| Self-reported attribution | Forms, sales calls | Buyers who saw you in an answer and came back later |
Another example with made-up numbers: an informational page falls from 8,000 to 5,000 monthly clicks, but trial signups from it go from 40 to 38. The lost visits were mostly readers who wanted the quick answer, so that page doesn’t need rescuing. A comparison page that drops from 1,200 to 900 clicks while demo requests fall from 30 to 18 does.
Report monthly, judge quarterly. For AI assistant referrals in GA4 and prompt tracking beyond Google, see how to track your brand in ChatGPT, Perplexity and AI Overviews.
Adjusting your content roadmap
Use the triage to reset the next two quarters of content:
- Stop briefing standalone pages for simple definitions unless they support a commercial cluster
- Consolidate overlapping informational posts into fewer, stronger pages
- Upgrade defended pages with tools, templates, data or hands-on comparisons
- Build more pages close to the buying decision: comparisons, alternatives, pricing, use cases
- Publish one original data asset per quarter that others can cite
- Re-run the Search Console comparison every quarter, because the queries that trigger overviews keep changing
This is how I run GEO and AI search visibility work: diagnose from Search Console, triage by business value, then ship the upgraded pages rather than hand over a list.
Get it built
If clicks are falling and you can’t tell which losses matter, I can run the diagnosis, triage your pages and build the recovery roadmap. Start with the Growth Audit, $1,500 fixed and credited if we continue. See pricing or get in touch.