Deindexing now removes you from AI answers

Losing Google's index now means losing Google's AI answers at the same moment, because AI Overviews and AI Mode only cite pages that the index still holds.

That was not always true in practice. From late 2024 into 2026, sites that were deindexed, including after a manual action, kept appearing in AI Overviews and AI Mode for a few days. Search Engine Roundtable reported in May 2026 that the delay appears to be gone. Glenn Gabe checked a site that had just been removed from the index and found it absent from both AI features. Google has not announced the change, so treat it as an observation from practitioners rather than a documented guarantee.

The timing matters this week. Google's September 2026 spam update began on September 24 and has a rollout window of up to two weeks. Search Engine Journal notes it is the fourth spam update of 2026, after March, June and August, and that the earlier ones finished in under 2 days and 16 hours. Search Engine Roundtable tracked a first wave on September 25 to 27 and a second on September 30. Google has not said which tactics it targets.

#Why the AI features follow the index

Google's documentation on AI features and your website is short on this point. To be eligible as a supporting link in AI Overviews or AI Mode, a page "must be indexed and eligible to be shown in Google Search with a snippet". There are no extra technical requirements, and the usual Search policies apply.

So there is no separate AI eligibility layer to protect. Anything that removes a page from the index, or from snippet eligibility, removes it from the pool those two features draw on. The old lag was a pipeline artifact. With it gone, the AI surfaces and the classic results now fail together.

#Two ways to lose it

The first is the slow path: an algorithmic spam demotion. Google's page on spam updates says a site that fixes its problems "may" improve "if our automated systems learn over a period of months" that it complies. For link spam it is blunter: any ranking benefit those links produced is lost and "cannot be regained". If your AI visibility depended on pages that a spam update demotes, plan for a recovery measured in months, not a reconsideration request.

The second is the fast path, and it often has nothing to do with your content. Gabe published a case study from April 2026 about a YMYL site with roughly 20,000 URLs that was suddenly deindexed. The team had decommissioned an old Azure web app that the www hostname still pointed to. Once Azure released the app name, someone registered it and redirected the www homepage to a gambling site, which pulled about 12,000 clicks in a single day. The site was already gone from search before the manual action showed up in Search Console, which arrived roughly a day later. The reconsideration request was approved within about 24 hours.

Microsoft documents this pattern as a subdomain takeover through a dangling DNS record: a CNAME that still points to a deleted resource can be claimed by anyone who provisions a resource with the same name. Microsoft's own list of consequences is about security and brand damage. For a site that depends on AI citations, add one more: every Google AI answer that cited you stops citing you, with no content change on your side.

#What this does to your AI visibility data

If you track citations across engines, a deindexing event has a recognizable shape. Citations in AI Overviews and AI Mode drop toward zero across unrelated topics on the same day, while engines that rely on a different retrieval index may not move at all. A content or relevance problem looks different: it tends to hit a topic cluster, a page template or one engine at a time.

That distinction saves a lot of wasted work. When AI visibility collapses on Google surfaces only, rewriting pages for "AI readiness" is the wrong response. The first questions are whether the pages are still indexed, whether a manual action exists, and whether every hostname you own still serves what you think it serves.

The reverse also holds. A recovery in AI Overviews should follow reindexing, so if your pages are back in the index and snippet-eligible but still missing from AI answers after a reasonable interval, you are looking at an ordinary competition or relevance question again.

#What to put in place

Check index status next to citations. Pair your AI visibility tracking with a periodic index check on the pages you most want cited. The Search Console URL Inspection tool and the Page indexing report are the authoritative sources. A citation drop with an index drop underneath it is a different incident from a citation drop alone.

Verify every host variant. Gabe's case turned on the www hostname. Add www and non-www, and every subdomain that serves content, as properties in Search Console (or use a domain property) so that manual actions and security issues for any of them reach you.

Audit DNS for dangling records. Put "remove the DNS entry" on the checklist for decommissioning any hosted service, as Microsoft recommends, and review CNAMEs on a schedule. On Azure App Service, the asuid TXT verification record stops another subscription from validating your custom domain.

Annotate the spam update window. Mark September 24 through the announced completion date in your reporting, and remember the window is longer than usual. Compare Google AI features against non-Google engines across that range before you attribute any change to content.

Separate the engines in reports. Report AI Overviews and AI Mode apart from engines that do not draw on Google's index. A blended "AI visibility" number hides the one pattern that tells you a deindexing event happened.

Respond in the right order. For a hijack or a manual action: fix the cause, file the reconsideration request, confirm reindexing, then expect AI citations to return. For an algorithmic spam demotion: clean up against Google's spam policies and budget months.

#The practical takeaway

AI visibility on Google is downstream of indexing, and since the lag closed, it is downstream with no buffer. The teams that read a sudden AI citation collapse correctly will be the ones that check the index, the hostnames and the spam update calendar before they touch a single page.