How to Recover Traffic From AI Overviews

Once you've identified which pages show the Great Decoupling pattern — impressions flat or up, clicks falling — the natural next question is what to do about it. The honest answer is that there isn't one fix. There are three, and picking the wrong one wastes effort. Rebuilding a page that was never going to earn the click back is just as costly as leaving alone a page you could have easily saved.

The right call comes from asking what's actually broken on that specific page. A page can lose clicks for different reasons — weak citation signals, stale content that no longer matches what the searcher wants, or a query that's simply been permanently absorbed into the answer box. Each of those points to a different action.

Call 1: Defend the click

Defend is the right call when the underlying content is genuinely good, but the page is weak on the signals that earn a citation or extractability inside an AI answer — clear headers, direct answers near the top, up-to-date schema, and clean entity signals. These pages don't need a rewrite. They need to become easier for an AI engine to read, cite, and prefer.

1. Check whether the page answers its main question directly in the first two or three sentences — buried answers get skipped by extraction.
2. Audit citation signals: is your business named consistently, and does your schema match what the page actually says?
3. Strengthen the specific gap. If it's presence or accuracy, that's an audit-and-fix job. If it's a broader visibility gap, that's a strategy job.

Call 2: Repurpose the page

Repurpose is the right call when the content itself has drifted — it no longer matches what today's searcher actually wants, even though it once did. A page that answers a question in a way that's become generic or outdated is easy for an AI Overview to out-perform. The fix isn't better citation signals on stale content — it's new content built around an angle the AI genuinely can't cover: a specific case, current data, or a next step only your business provides.

Call 3: Retire the page (or let the query go)

Some queries are simply not coming back. If a plain factual question is now reliably and completely answered inside the AI Overview, and there's no realistic angle your page could add, spending more effort defending or rebuilding it is money spent chasing a query that's gone. The better move is to redirect that effort — and sometimes the page itself, via an internal link or consolidation — toward content built for a query type AI Overviews can't fully absorb.

This isn't giving up. It's the same discipline as any budget decision: stop spending where the return has structurally changed, and reallocate to where it hasn't.

Why the page-by-page approach beats a blanket policy

It's tempting to pick one strategy and apply it site-wide — rewrite everything, or give up on informational content entirely. Both overcorrect. Some of your best-performing, highest-intent pages are barely touched by AI Overviews and don't need any of this. Some low-effort factual pages were never going to earn much traffic anyway and aren't worth defending. The value is in sorting your specific pages into the right bucket, not applying one rule to all of them.

That sorting depends on first confirming which pages are actually affected — the same impressions-up/clicks-down check covered in the Great Decoupling — and understanding which query types are structurally more exposed, covered in zero-click search. Once you know both, the defend/repurpose/retire call gets much easier to make with confidence.