Why did my Search Console AI impressions drop suddenly?
99Visibility Research · Updated October 21, 2026 · 5 min read
If your AI impressions fell around August 12 to 13, 2026, a Google-side bug that depressed impressions in both the Search and Generative AI performance reports is the first suspect. If the drop started on another date, or hit only some pages, rule out real causes in this order: deindexing, snippet controls, the AI features control in Search Console, and fewer AI Overviews triggering for your queries.
The short answer and the reasoning
A sudden drop in the generative AI report has two kinds of cause: a reporting problem on Google's side, or a real change in whether Google can show your pages.
Start with the date. Google confirmed a bug that depressed impressions in both the Search and Generative AI performance reports from roughly August 12 to 13, 2026. If your drop lines up with that window and shows in both reports at once, the bug is the likeliest explanation. Your site may not have changed at all.
If the drop starts on a different date, or affects some pages and not others, treat it as real until you prove otherwise. Google's AI features documentation says a page must be "indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link in AI Overviews or AI Mode. Anything that breaks indexing or snippet eligibility breaks AI impressions too. Beyond your own site, Google's AI features control can switch you off, and AI Overviews may simply trigger less often for your queries.
What this means: don't rewrite content or add markup in response to a drop. Find which gate closed first.
The August 2026 reporting bug
The bug matters for two reasons.
First, any trend that spans mid-August 2026 compares a depressed period with a normal one. A month-over-month chart running through that window can show a fall that never happened in search results.
Second, the timing overlaps the report's own history. The generative AI report completed its global rollout around August 11, 2026, just before the bug. Many properties have very little clean data from before the affected window. That makes "normal" hard to define.
How to tell bug from reality
- The drop begins on or near August 12 to 13, 2026.
- The classic Search performance report shows a matching dip on the same dates.
- The dip spreads across pages roughly evenly, rather than concentrating on a few URLs.
If all three hold, exclude that window from your comparisons. Check Google's current statements on whether the affected dates were corrected before you report a trend to anyone. Our guide to the generative AI report covers how to set clean comparison ranges.
Real causes to rule out
Deindexing
If Google drops a page from its index, its AI surfaces stop citing it. In Otterly's 2,000 AI blogs experiment, Google deindexed two scaled AI content sites with no manual action shown in Search Console, and Google's AI surfaces then almost never cited them. Removal can be silent. Check index status in URL Inspection for the pages that lost impressions.
Snippet controls
Google documents noindex, nosnippet, max-snippet and data-nosnippet as the on-page controls that keep content out of AI features. They often arrive through a template change. A line like this, shipped by accident, removes a page from AI answers:
<meta name="robots" content="nosnippet">
Also check the X-Robots-Tag HTTP header and any data-nosnippet attributes on main content blocks.
The AI features opt-out
Inclusion in AI Overviews, AI Mode and Discover generative AI is the default. Search Console has a control to opt out, and it is still rolling out to a subset of owners. Child properties default to inheriting from their parent, so an opt-out set on a parent can silently cover yours. Read how the AI features control works, and if you manage several properties, audit inherited controls.
Fewer overviews triggering
Google says AI Overviews often do not trigger at all. If Google shows overviews for fewer of your queries, impressions fall while your pages stay eligible. This is not in your control.
The check order
Work through these in order. Each step is cheap, and the early ones rule out the most.
- Find the start date. Compare it with August 12 to 13, 2026, and with the classic Search report. A match on both points to the bug.
- Find the affected pages. Use the Pages dimension in the generative AI report. A drop on a few URLs points to page-level causes. A sitewide drop points to the bug, a property-level control, or a template change.
- Check index status. Run URL Inspection on the affected pages. Look for exclusion, canonical changes, or a
noindex. - Check snippet directives. Inspect the HTML and HTTP headers for
nosnippet,max-snippet:0anddata-nosnippet. Also confirm robots.txt still allows Googlebot, since no separate robots.txt token controls AI Overviews. - Check the AI features control. Look at the property and its parent. The free Search Console AI control check walks through it.
- Check whether overviews still appear. Search your important queries and see whether an overview shows at all. The AI Overview Checker does this query by query.
If steps 1 to 5 come back clean, the drop most likely reflects Google showing fewer overviews, or showing different links.
What the report cannot tell you
As of October 2026, the generative AI report shows impressions only. Its dimensions are Pages, Countries, Dates and Devices. It has no clicks, no CTR and no position, so it can't tell you whether lost impressions cost you traffic. See whether you can see AI Overview clicks for the workarounds.
It also doesn't separate "Google stopped showing an overview" from "Google showed an overview without you." Both look identical in the chart. Google notes that AI Overviews and AI Mode may use different models and techniques, so a drop on one surface says little about the other.
The next move: once you've ruled out the gates you control, stop editing pages to chase the number. Track the specific queries that matter to you, and judge changes over weeks, outside the bug window.
Did the August 2026 bug affect only the AI report? No. Google confirmed it depressed impressions in both the Search performance report and the Generative AI performance report from roughly August 12 to 13, 2026. That is useful for diagnosis: if your classic Search impressions dip on the same dates, the bug is the likeliest cause. If only the AI report fell, look at AI-specific causes such as the AI features control or fewer overviews triggering.
Can I see which queries lost AI Overview impressions? Not directly in the generative AI report. Its documented dimensions are Pages, Countries, Dates and Devices. You can find which pages lost impressions, then work out which queries those pages serve. Our page on [which searches triggered AI Overview impressions](/questions/search-console-ai-overview-queries) covers what Search Console exposes and where the gaps are.
Will adding schema or rewriting content bring impressions back? There is no evidence it will. Google says structured data isn't required for generative AI search, and Ahrefs' matched-control study found AI Overview citations fell 4.6% after pages added schema. Google's eligibility rule is indexing plus snippet eligibility, with no extra technical requirements. Fix what blocks you: index status, snippet directives, the AI control and Googlebot access.
Does the AI features opt-out affect my regular rankings? Google says the control isn't used as a ranking or inclusion signal for other parts of Search. It covers display in AI Overviews, AI Mode and Discover generative AI features. It is separate from Google-Extended, which governs Gemini training and grounding. Opting out of display also doesn't stop Google using content to power Search more broadly, such as understanding query language.
Sources
This page is AI-assisted. It was written from a verified evidence base and checked against our editorial policy. Engine behaviour changes often; facts are as of October 21, 2026.