Clicks dropped but rankings didn't: how to tell an AI Overview from a core update in Search Console

If a page's clicks fell while its impressions and average position held steady, the most likely explanation is that something on the results page now answers the query before anyone scrolls to you. In 2026 that is usually an AI Overview. A core update looks different: position and impressions fall together, and the drop starts inside a dated rollout window. Search Console can tell the two apart in about ten minutes, as long as you look at more than the clicks line.

Check 1: put clicks, impressions and position on the same chart

Open Search Console → Performance → Search results, tick all four metrics, and filter to the page or query group that lost traffic. Compare the last 28 days with the previous 28, then switch to the 16-month view and compare year over year to rule out seasonality. Google's own guide to debugging traffic drops recommends the same long view.

You will see one of three shapes:

The middle pattern is the one this article is about. It is easy to misread as a ranking problem and "fix" with rewrites that change nothing, because the page already ranks.

Two refinements make the read more reliable. First, segment by search type (Web, Image, News, Discover) before drawing conclusions, since a Discover drop has nothing to do with web rankings. Second, look at queries rather than only at the page total. A page can hold position on its main query and lose a dozen long-tail ones, which averages out to a misleadingly flat position line.

Check 2: match the drop date to a confirmed update

Google's Search Status Dashboard lists every confirmed ranking rollout. Here is everything it shows for 2026, plus the December 2025 core update for a 12-month look-back:

There was no January 2026 or June 2026 core update on the dashboard, whatever some third-party trackers say.

If your drop starts inside one of those windows, or a few days after one ends, that update is the likely cause. Core updates act over a rollout of roughly two weeks, so don't expect a single clean step on the start date. If the drop matches nothing, the cause is site-specific: a deploy, a competitor, or demand moving. And if the shape in Check 1 was the middle one (position held), a matching date is probably coincidence.

Core or spam? The two need different responses. A core update is a reassessment of how helpful your pages are compared with everything else. Google says pages that drop "aren't necessarily 'bad'" and that core updates don't target specific sites (Google on core updates). A spam update means its systems found something that violates a spam policy, most often scaled content abuse, thin affiliation, expired domain abuse or site reputation abuse. Recovery from a spam update starts with removing the violation, not with improving prose.

Check 3: confirm it in the generative AI performance report

Since June 2026 Search Console has a report built for exactly this question. The Search generative AI performance reports show how often your pages appeared in AI Overviews, AI Mode and AI Overviews in Discover, broken down by page, country, device and date. Data starts on 18 May 2026, and Google rolled the reports out to all sites by 31 August 2026.

The pattern that confirms AI absorption: the page's AI Overview impressions rise (or appear for the first time) over the same weeks its clicks in the regular Performance report fall while position holds.

Know the limits before you lean on it:

• Impressions only. The report has no clicks and no queries, so it cannot tell you how much traffic the Overview took. You infer that by lining it up with the regular Performance report.
• Appearance is not citation. An impression means your page was shown in the AI feature. It doesn't tell you whether the answer quoted you prominently or listed you sixth.
• No history before 18 May 2026. For older drops, compare the CTR on your affected queries before and after Overviews started appearing for them, which you can check by searching them yourself.

How big the AI Overview effect is

The measured numbers are large enough that "position held, clicks halved" needs no other explanation.

• Ahrefs compared 300,000 keywords and found the top-ranking page's click-through rate 58% lower when an AI Overview was present (December 2025 data against December 2023, published February 2026). Its April 2025 version of the same study had measured 34.5%, so the effect grew.
• Seer Interactive tracked 3,119 informational queries and found organic CTR on queries with an AI Overview falling from 1.76% to 0.61% (Search Engine Land coverage).

The same Seer study holds the useful half: brands cited in the Overview got about 35% more organic clicks than brands that weren't. The Overview appears either way. Whether you are one of its sources decides which side of that gap you are on.

For the wider zero-click picture, see what is zero-click search.

If it's the AI Overview: what to do

Rewriting a page to rank better does nothing when it already ranks. The work shifts to being one of the sources the Overview draws on.

1. Make sure you're eligible at all. To appear as a supporting link, a page "must be indexed and eligible to be shown in Google Search with a snippet" (AI features and your website). A nosnippet directive or a very short max-snippet value takes you out. So does a page Google dropped from the index, which the Page indexing report will show.
2. Put the answer where it can be found. State the direct answer near the top, in plain sentences, with claims attributed to named sources. Google's AI optimization guide is explicit that you don't need to chop content into tiny pieces or write in a special style for AI, so don't restructure a good page into fragments.
3. Add something the Overview can't get elsewhere. The same guide calls this non-commodity content: first-hand testing, your own measurements, a clear verdict. A page that restates what the top five results already say gives the answer no reason to cite it.
4. Check ChatGPT and Perplexity too. They run their own retrieval, so a page that lost Google clicks may still be cited there, or vice versa. Their crawlers (OAI-SearchBot, PerplexityBot) must be allowed in robots.txt and at your CDN.

What about opting out? Search Console now has a property-level Search generative AI control. Turning it off removes your site from AI Overviews, AI Mode and AI Overviews in Discover, both as a link and as grounding for the answer. Google says it doesn't affect regular rankings, and it reached all websites worldwide on 31 August 2026. It will not bring the lost clicks back, because the Overview still appears for the query, built from other sites. Opting out is a decision about licensing your content to Google's AI features, not a traffic recovery tactic.

If it's a core update: what to do

The honest guidance here is Google's own, and it is less dramatic than most recovery playbooks.

• Self-assess, then improve. Google points to its helpful content questions. Does the page show first-hand experience? Is it more than a summary of what others say? Would you trust it if a stranger had written it?
• Improve before you delete. Google calls deleting content "a last resort, and only to be considered if you think the content can't be salvaged." Consolidating near-duplicates with 301 redirects is usually the better tool.
• Update the substance, not the date. Google specifically warns against changing dates to make pages look fresh when the content hasn't substantially changed. For reviews and comparisons, that means re-checking products, prices and alternatives.
• Ignore word-count and "E-E-A-T score" advice. Google says it has no preferred word count, and that E-E-A-T "itself isn't a specific ranking factor." Named authors and evidence of experience help because they make the page more trustworthy to people, not because a checkbox gets ticked.
• Expect months, not weeks. Google says it "could take several months" for its systems to confirm a site-wide improvement, and that changes can also show up in smaller core updates between the big ones. For sites hit in March 2026, the May 2026 core update (21 May to 2 June) was the first big re-evaluation. Nobody publishes reliable data on how much traffic comes back by week N, so treat any timeline table with that kind of precision as a guess.

If it's a spam update: what to do

Find the policy you are most likely to be violating and remove the violation. Pause any pipeline that publishes AI-generated pages without substantive human review, because mass-produced pages are what the scaled content abuse policy describes. Check Manual actions in Search Console. If there's a notice, fix it and file a reconsideration request. If there isn't, the action was algorithmic and recovery means waiting for the systems to see the change.

That wait is also long. Glenn Gabe's case studies of the August 2026 spam update quote Google saying it "can take months after making significant changes" to recover, and reference one site that came back about five months after cleaning up.

Check 4: rule out the boring causes

Before any of the above, spend fifteen minutes on the causes that are fastest to fix:

• Page indexing report: a sudden rise in excluded or errored pages
• Manual actions: the only check that gives an explicit answer
• Security issues: hacked content or malware warnings, which Google lists as a primary cause of drops
• robots.txt and noindex: a deploy that accidentally blocks Googlebot or adds noindex
• Canonicals and redirects: duplicates or 302s introduced by a CMS change or migration
• Uptime: extended downtime or server errors during the window

Fix anything found here before touching content.

What not to do in the first week

• Don't publish a burst of new content. Google assesses the site overall, so adding more pages of the kind that dropped won't help and can make the picture harder to read.
• Don't rewrite pages that still rank. If position held, the page isn't the problem.
• Don't disavow by reflex. Without a manual action for unnatural links, a disavow file mostly risks discarding links that were helping. Google's systems generally ignore low-quality links rather than penalizing the site receiving them.
• Don't change five things at once. If titles, content, schema and links all change together, you can't tell which one mattered.
• Don't refresh Search Console every hour. The Performance report usually lags about two days. The generative AI report has hourly data, but hourly noise isn't a trend.

FAQ

Your next ten minutes

Open Performance for the page that lost the most clicks. Turn on all four metrics, set the comparison to the last 28 days against the previous 28, and look at the position line. If it held, open the generative AI report for the same page and the same weeks. If its impressions there went up as clicks went down, you have your answer, and the fix is to be the source the Overview quotes. If the position line fell, take the drop date to the table above.

For the citation side of the problem, see why an AI Overview citation disappears and how pages get into AI Overviews.

Sources cited in this piece

• Google Search Status Dashboard: ranking update history, with incident pages linked in the table above
• Google: Debugging drops in Google Search traffic
• Google: Core updates and your site
• Google: Creating helpful, reliable, people-first content
• Google: Spam policies for Google web search (updated 28 Aug 2026)
• Google: AI features and your website
• Google: AI optimization guide (May 2026, updated July 2026)
• Google Search Central blog: Search generative AI performance reports, June 2026
• Search Engine Land: AI performance reports and generative AI control roll out globally, 31 Aug 2026
• Ahrefs: AI Overviews reduce clicks by 58%, 4 Feb 2026
• Search Engine Land on Seer Interactive: AI Overviews drive drop in organic and paid CTR
• GSQI: August 2026 Google spam update case studies

Updated October 1, 2026: refocused on telling AI Overview click loss apart from core and spam updates; added every confirmed 2026 update, the Search Console generative AI report and opt-out control, and Ahrefs' February 2026 CTR figure; removed recovery timelines that had no published basis.