Two months of deindexing reports. Thousands of pages moving into "crawled, currently not indexed" buckets. Site owners watching entire properties vanish from Search Console without a manual action or crawl error in sight. And Google's official response? John Mueller says he doesn't see anything exceptional.
That gap between what operators are reporting and what Google is acknowledging should concern any B2B marketing leader whose pipeline depends on organic visibility. Not because the sky is falling, but because misdiagnosing the problem leads to the wrong fix. And the wrong fix, applied at scale, can turn a recoverable drop into a permanent loss.
The Signal in the Noise
The current wave traces to a late-April question from Pedro Dias, a former Google employee, who asked whether others were seeing pages leave the index at a higher rate. The response was overwhelming: site owners across industries described the same pattern. Pages that had been indexed for years moved into "excluded" status without explanation. Some accounts described whole properties flipping to "crawled, currently not indexed" rather than a handful of URLs.
The status doing the most work in these reports is "crawled, currently not indexed." It means Google fetched the page and chose not to index it. That differs from a page Google has discovered but not yet crawled. The distinction matters because the remediation paths are different. One is a crawl priority issue. The other is a quality signal.
Marie Haynes examined roughly 40 sites and found a pattern: the pages being deindexed were ones Google would be unlikely to serve to searchers anymore. Old blog posts. Thin pages. Content that paraphrases information written elsewhere without adding original value. One supplement site dropped from 27,000 indexed pages to 15,000. A local service business lost 20% of its pages, many of which appeared to be AI-written or rewritten commodity content.
Here's the complication: when Haynes inspected some of those "deindexed" pages manually, Google reported them as indexed. They weren't deindexed at all. They just weren't ranking.
Ranking Loss Is Not Deindexing
This is where the diagnosis gets expensive. A page that loses impressions still sits in the index. A page that drops from position three to position forty still exists in Google's database. The Search Console report says "crawled, currently not indexed," but a site: query shows the URL. The reporting and the reality don't match.
Glenn Gabe's case study of a site that was genuinely deindexed shows what actual removal looks like: a complete disappearance from site: queries, a manual action arriving days later, and a clear cause (in that case, AI-generated content in a YMYL niche). That's different from what most of these reports describe.
Google's 2026 ranking calendar has been dense. A spam update and a core update ran in March. A broad core update ran in May. SE Ranking's analysis of the May update found Reddit gaining top-three positions across all 20 niches they tracked, while YouTube thinned out of regular links. Amsive's analysis of the March update found aggregators and user-generated content platforms losing visibility while first-party brand sites gained.
The same kinds of sites moved in opposite directions across two updates. That's not deindexing. That's reranking. And reranking is recoverable if you understand what changed.
The CFO Question
For B2B marketing leaders, the question isn't whether Google is behaving strangely. The question is: what's the exposure, and what's the remediation cost?
Recent analysis of B2B organic discovery shows that while global search volumes continue rising, the volume of clicks exiting the SERP to external B2B websites is declining. AI Overviews now appear on roughly 25% of queries. Zero-click searches account for about 60% of all Google searches. The traditional inbound model, where you publish educational content and Google delivers discovery traffic, is under structural pressure independent of any deindexing event.
That means the pages you're worried about losing may not have been driving pipeline anyway. Before you panic about Search Console status codes, run the math: which of those "deindexed" URLs actually generated qualified traffic in the last 90 days? Which ones converted? If the answer is "none," the deindexing report is noise. If the answer is "our top five lead-gen pages," you have a real problem that requires a different response.
The Diagnostic Sequence
When a client reports deindexing, I run the same sequence every time:
First, verify the claim. Run a site: query for the affected URLs. If they appear, they're indexed. The Search Console report may be lagging or misclassifying.
Second, check for actual ranking loss versus index removal. Pull the impression and click data for those URLs over the past 90 days. A page that went from 1,000 impressions to 50 impressions is a ranking problem. A page that went from 1,000 impressions to zero with no site: result is an index problem.
Third, assess content quality through Google's lens. The "crawled, currently not indexed" status typically appears when Google determines a page doesn't provide sufficient standalone value. Weak internal links, thin content, search intent mismatch, near-duplicate content, or structured data errors can all trigger it. Gary Illyes has said a high number of these URLs "could hint at general quality issues."
Fourth, model the business impact. If the affected pages weren't driving conversions, the remediation priority is low. If they were, you need to understand whether the issue is content quality, technical signals, or competitive displacement before you act.
What Not to Do
The worst response to a deindexing report is to start submitting URLs for reindexing at scale. If Google chose not to index a page because it assessed the content as low-value, requesting reindexing doesn't change the assessment. It just wastes crawl budget and signals that you don't understand the problem.
The second-worst response is to delete or redirect pages that are actually still indexed but ranking poorly. A page that dropped from position five to position thirty can recover. A page you deleted cannot.
The third-worst response is to assume the problem is technical when it's actually editorial. Most "crawled, currently not indexed" issues resolve when you improve the content, strengthen internal linking, and clarify the page's purpose. They don't resolve when you tweak robots.txt or submit another sitemap.
The Forecast Adjustment
If your organic traffic forecast assumes stable indexation, you need a sensitivity table. What happens to pipeline if 10% of your indexed pages move to "crawled, currently not indexed"? What if 20%? What's the CAC impact if you have to backfill that traffic with paid?
The answer probably isn't catastrophic. Most B2B sites have significant content bloat: old blog posts, thin category pages, commodity content that ranks for nothing and converts no one. Google removing those pages from the index is a cleanup, not a crisis.
The pages that matter, the ones with original research, proprietary data, or genuine expertise, are not the ones getting deindexed. They're the ones Google is trying to surface more prominently as it filters out the noise.
If your content portfolio is mostly noise, that's the problem to solve. Not the Search Console status code.
