Deindexing: Why Google Drops Pages From Its Index

Deindexing is when Google removes pages it had previously indexed. It is a different problem from a page that never made it into the index, and it is diagnosed differently: you are explaining a loss of pages that were already working, not troubleshooting a launch. If your pages have never appeared in search, start with Why Isn’t My Page Indexed? instead. This guide covers the opposite case: pages that ranked, then vanished.

What is deindexing?

A deindexed page is one that Google had in its index and has since dropped. In the Page Indexing report it typically moves from indexed to a not-indexed reason code, most often “Crawled: currently not indexed”. The page may still be crawled; Google has simply decided to stop keeping it in the index.

Deindexing can hit a single page, a section of a site, or an entire domain. The scale is a clue to the cause: a handful of pages points to page-level quality or technical issues, while a sudden site-wide drop points to a manual action or a misconfiguration applied across the site.

How do you confirm a page has been deindexed?

Before diagnosing a cause, confirm the loss is real. Search Console reporting lag can make a stable site look like it is shedding pages.

• Check the trend, not the day. In Indexing > Pages, look at the indexed-page count over weeks. A sustained decline is a real signal. A single-day dip that recovers is almost always a reporting artefact.
• Inspect a live URL. Run the URL Inspection tool on a specific page you believe has dropped. It reports the current index status directly, rather than relying on the aggregate count.
• Run a site: check. Searching site:yourdomain.com/path for an affected URL shows whether Google still returns it. Treat this as a rough confirmation, not a precise count.

If the trend is flat and inspection shows pages still indexed, you are looking at a reporting blip and there is nothing to fix.

Why does Google deindex pages that were ranking?

Once you have confirmed a genuine drop, the cause is usually one of four.

A manual action

Check Security & Manual Actions > Manual actions in Search Console. A manual penalty for spam, cloaking, or guideline violations can remove pages or a whole site from the index. This is the only cause Google flags explicitly, and it comes with a stated reason and a reconsideration path. If there is no notice here, the cause is algorithmic or technical.

An algorithmic quality reassessment

Core and spam updates re-evaluate content Google already holds. A page that previously cleared the quality bar can fall below it as the threshold moves or competing content improves, dropping to “Crawled: currently not indexed” with no change on your side. Google has become more selective about what it retains, especially thin, near-duplicate, or unedited auto-generated content.¹ There is no manual-action notice for this, which is what makes it hard to diagnose.

Content decay

Pages age. Information goes stale, the query behind the page shifts, or fresher competitors overtake it, and Google stops seeing the page as worth indexing. This is gradual rather than sudden. Refreshing the content, consolidating overlapping pages, and re-establishing the page’s distinct value is the remedy. See content pruning for how to decide what to update, merge, or remove.

A technical regression

A site-wide noindex pushed live by mistake, a robots.txt change that blocks a directory, persistent 5xx errors, or a mishandled migration can deindex pages in bulk. These are the fastest to confirm and fix: work through the reason codes in Why Isn’t My Page Indexed?, because the same blockers that stop a page being indexed will also drop one that already was.

What does “Google is deindexing pages” in 2026 mean?

Through 2026, many site owners reported previously-indexed pages moving to “Crawled: currently not indexed” with no manual action, crawl error, or spam notice.¹ Google has not confirmed any change in indexing behaviour; John Mueller’s response to the reports was that “some sites go up, some sites go down” and that he saw “nothing exceptional”.² Analysts are split between two readings: an acceleration of Google’s quality and freshness filtering in response to the volume of AI-generated content, and a Search Console reporting artefact rather than a true removal.

The practical takeaway holds whichever is correct. Where Google has not confirmed a cause, treat a drop as a prompt to audit content quality and freshness, not as evidence of a bug to wait out. Avoid bulk “fixes” until you have isolated which pages dropped and what they share.

How do you recover deindexed pages?

Recovery follows the cause:

• Manual action: fix the underlying violation, then file a reconsideration request.
• Quality reassessment: improve the affected pages so each answers a distinct question with genuine depth, or consolidate thin overlapping pages into stronger ones.
• Content decay: update, re-verify, and reconsolidate; re-establish the page’s reason to exist.
• Technical regression: remove the blocker (noindex, robots rule, server fault), then request indexing via URL Inspection to queue a priority crawl.

In every case, indexing is a decision Google remakes on each crawl. Resolving the cause does not guarantee re-inclusion, and recovery can take several crawl cycles to register.

Deindexing vs never being indexed

The two are easy to confuse because they share reason codes and remedies, but the starting point differs and so does the diagnosis.

	Never indexed	Deindexed
Situation	A new or recent page won’t get in	An established, ranking page dropped out
First check	Reason code in the Page Indexing report	Indexed-page trend over time; manual actions
Most likely cause	Intentional exclusion, discovery, or crawl gap	Penalty, algorithmic reassessment, decay, or regression
Guide	Why Isn’t My Page Indexed?	This page

Footnotes

1. June 2026 Google Webmaster Report — Search Engine Roundtable ↩ ↩²

2. Google Is Deindexing URLs at Higher Rates Since April 2026 — Writtenly Hub ↩