Google says its indexing systems are fine. SEO teams say pages are vanishing. Both can be right, and the gap between those two truths is where costly mistakes happen.
Since late April 2026, reports of pages disappearing from Google's index have been steady. No manual actions. No crawl errors. Pages just sliding into "Excluded" or "Crawled – Currently Not Indexed" in Search Console and staying there. Pedro Dias, a former Google employee, kicked off the thread by asking whether others were seeing elevated deindexing rates. The answer, from dozens of site owners, was yes.
John Mueller's response: nothing unusual. He described the movement as ordinary.
Site owners didn't find that reassuring. But Mueller might not be wrong. The problem is that "deindexing" has become a catch-all term for at least five distinct problems, and most teams aren't separating them before they react.
Five Problems Wearing the Same Name
"My pages are gone" can mean several things. The fix changes completely depending on which one you're dealing with.
True deindexing: A URL that was indexed now isn't. URL Inspection confirms it's gone and gives a reason. This is the scenario everyone fears, and it's the one worth confirming before you assume it.
Ranking loss: The page is still indexed but showing up for fewer queries at lower positions. After the May 2026 Broad Core Update (May 21–June 2, volatility score 78/100), this is the more common outcome. In a dashboard, a ranking cliff looks identical to a deindexing event. It isn't.
Canonical consolidation: Google keeps the content but credits a different URL. Your chosen page shows as "not selected." Common on ecommerce sites with variant URLs and faceted navigation.
Technical blocking: A stray noindex tag, a robots.txt misconfiguration, or a server error quietly pulling pages. No algorithmic judgment involved. Martin Splitt has walked through how pages move from discovery to indexing; most "missing" pages fail at a step you can name.
Reporting artifact: Google's Data Anomalies page documents a logging error that misreported impressions from May 2025 through late April 2026. The fix rolled forward only, so the correction looks like a drop. Plus, a confirmed Search Console links report glitch has been adding noise. Clicks weren't affected by the impression error, which makes click data your steadier signal right now.
The Context Making Everything Louder
Google's 2026 update calendar has been relentless. A spam update and core update in March. The May Broad Core Update. Then the June 2026 Spam Update (June 24–26), targeting scaled AI abuse and low-value content. Google reported thousands of low-value sites deindexed in the March spam update alone.
Layer on AI Overviews, which now appear in about 20.5% of US searches. When an AI Overview shows up, top-ranking pages lose between 34.5% and 64.4% of their clicks. Pages remain indexed. Traffic drops anyway. For a marketing team watching dashboards, that looks like deindexing. It's demand displacement.
These forces stack. A core update reshuffles rankings. An AI Overview absorbs clicks on queries you still technically rank for. A GSC reporting bug distorts your impression baseline. Each one is a different problem with a different response, and lumping them under "deindexing" guarantees you'll fix the wrong thing.
The Real Risk: Acting Before Diagnosing
Some teams are already adding noindex tags to "reset" pages, restructuring URL paths, or filing emergency tickets. All of it rests on a chart that may be a reporting artifact. Each move can turn a temporary problem permanent.
The diagnostic sequence matters:
- Step 1: Use URL Inspection on a sample of affected URLs. Not site: searches (unreliable for index status), not aggregate GSC counts (subject to reporting bugs). Per-URL inspection.
- Step 2: Cross-reference click trends in GSC with GA4 organic sessions. If clicks and sessions are stable but impressions dropped, you're probably reading the reporting fix, not a visibility loss.
- Step 3: Check for technical causes. Robots.txt blocking key pages, stray noindex tags, server errors returning 5xx to Googlebot. Rule these out before assuming algorithmic behavior.
- Step 4: If pages are genuinely deindexed, look at the content. Google's been clear about deprioritizing content that repeats what's already on many other sites. Gary Illyes has said a high volume of "Crawled – Currently Not Indexed" URLs "could hint at general quality issues." Commodity B2B SaaS content is especially exposed.
GSC's 16-month history limit means you can't always look back far enough for a clean baseline. If you don't have independent crawl monitoring, this is the quarter to set it up.
What This Means for Content Strategy
The hypothesis worth testing: the bar for index inclusion is rising, and sites running large volumes of similar pages are on the wrong side of it. That's still a hypothesis, not a confirmed policy change. But the signal from three spam updates and two core updates in six months points in one direction.
Content with first-person experience, original data, and clear author identity has been more resilient through these cycles. Scaled commodity content has not. If 70% of paid B2B SaaS links are being ignored (a claim circulating in the SEO community), the investment case for volume link-building weakens further.
The trade-off is real: consolidating thin content reduces your indexed page count before it improves your ranking quality. That's uncomfortable to explain to a CMO watching a dashboard. But it's better than the alternative, which is watching Google make the consolidation decision for you.
Google says it sees nothing unusual. That might be accurate from where they sit. From where marketing teams sit, the landscape looks different: core updates compressing rankings, AI Overviews absorbing clicks, reporting bugs distorting baselines, and spam updates culling low-value pages. None of those require a new deindexing policy to explain the pain. The pain is real. The diagnosis just needs to be specific.
