23SEOGEO · Weekly focus ·
Rankings up, clicks down: investigate AI Overviews and scope
When rankings improve but clicks fall, compare impressions and CTR for the same query, page, market, device and window before attributing the loss to AI Overviews.
the 23SEOGEO team · Updated
The short answer
Better rankings do not guarantee more clicks. Compare impressions, clicks, CTR and average position for the same query and page, then examine seasonality, device, market, result layout and observed AI Overviews. Average position is an aggregate, not a fixed placement for one keyword. Only an observed result page helps assess AI Overview effects; a traffic drop alone is not attribution.
From question to reviewable evidence
Locate the loss
Locate a real click decline by query and page.
- Keep country, device and dates comparable
- Review impressions, clicks, CTR and average position separately
Full action and acceptance checklist
Locate the loss
Locate a real click decline by query and page. Keep country, device and dates comparable · Review impressions, clicks, CTR and average position separately
Original GSC export and scope.
Review real Search Console queriesInspect the SERP
Observe the layout for real queries before selecting a page to change. Record whether an AI Overview appears · Keep originals and edits; no bulk TDK changes
Observed SERP and one-page change plan.
Analyze the current SERPReview separately
Compare search clicks and AI referrals separately. Use actual publication as D0 · Extend observation for small samples
Same-page, same-query review and site referral window.
Review AI traffic and conversions
Break down average position before comparing samples
Fix one site and comparable windows, then break down Search Console by query and page rather than relying on homepage totals. Better average position may reflect changes in query, country or device mix. If impressions decline, clicks may fall even when CTR rises. Query rows are subject to privacy and read limits, so their sum may differ from totals. No returned rows means no records, not an unindexed page; check index status separately.
AI Overview attribution needs an observed result page
Choose a query with an actual click change and inspect the result page under comparable market, language and device conditions. Record time, AI Overview presence, ads and other elements, and whether your URL appears. The image here is conceptual, not that query’s SERP. One observation cannot represent an entire window, and a visible link is not a click. Without matching SERP evidence, retain AI Overviews as an unverified hypothesis alongside demand changes and technical issues.
Improve answer value and the post-click next step
Check whether the page directly answers the query and its title accurately describes the content. Add real product conditions, audience, exceptions, comparison evidence and contact paths. Avoid exaggerated clickbait or withholding answers to force visits. Google AI features rely on indexable pages and SEO foundations; content does not need a duplicate AI-only page. Change one page at a time, keeping originals and the actual publication date rather than conflating several changes.
Review search clicks and AI referrals separately
Search Console describes its Google Search scope; AI referral tracking describes source visits collected for an authorized website. Do not sum them as total customers. Clicking contact is not a completed enquiry or sale. Starting at the actual publication date, review the same query and page at D+14 and D+28, extending observation when samples are small. These are team checkpoints, not a Google ranking cycle or an automatically scheduled service.
Investigating a click change
| Observed change | Check first | Do not assume |
|---|---|---|
| Position improves, impressions fall | Query demand and country/device mix | AI Overviews caused all losses |
| Impressions stable, CTR falls | Observed SERP, title and intent | All titles need replacing |
| Clicks stable, enquiries fall | Contact path and business records | A search penalty |
| No GSC query records | Read limits and index inspection | The page is not indexed |
Related questions
- Can AI Overviews reduce traffic when rankings improve?
- Why are rankings up but clicks down?
- How should an AI Overviews traffic drop be investigated?
Common questions
Do AI Overviews always reduce website traffic?
No universal conclusion follows. Inspect queries, SERPs and comparable windows; a decline alone does not prove its cause.
Is average position a fixed keyword rank?
No. It is an average within the selected scope; break it down by query, page and device.
Should I create separate pages for AI Overviews?
Not for that purpose. Improve readability, answers and facts on existing pages first.
Sources
- Google: AI features and your website
SEO foundations and AI-feature eligibility; no citation or lead guarantee.
- Google: Helpful, reliable, people-first content
For reviewing whether a page serves readers, not an endorsement of a platform score.
- Search Console: Performance report
Scope of queries, pages, clicks, impressions and average position.
- Google: Debugging search traffic drops
Investigate technical, demand and scope changes rather than attributing every loss to AI.