Recovering a Page That Has Suddenly Gone Not-Indexed

A page that used to rank, used to drive traffic, used to be in the index — and is suddenly not. This is one of the highest-impact SEO incidents because every day the page is out, you lose the traffic and rankings it produced. This article is the focused recovery workflow for that specific situation, in roughly the order it makes sense to follow.

Confirm the page is actually not indexed

Search for the exact URL in Google. Use Search Console's URL inspection tool. Both should produce consistent answers about whether Google has the page indexed. If the URL inspection says the page is indexed but the search shows no result, the indexing is fine and the issue is something else (ranking drop, query change, etc.).

Check the page is reachable

Visit the URL yourself. Does it load? Does it return a 200 status? Use a tool like curl or Postman to check the headers — sometimes a page loads in a browser but returns a 5xx for bots due to a misconfiguration. A page that is unreachable to Google for any reason will get dropped from the index.

Check the canonical tag

The most common cause of a previously-indexed page becoming not-indexed is a canonical tag pointing to a different URL. A recent template change might have added the wrong canonical. Inspect the page source for and confirm it points to itself (or to the intended canonical destination).

Check the noindex meta tag

The second most common cause is a noindex meta tag, usually added by a CMS misconfiguration or a deploy mistake. Look for in the page source. Also check the X-Robots-Tag in the HTTP response headers, which is functionally equivalent but easier to miss.

Check robots.txt

A robots.txt rule that was added recently might be blocking the page. Use Google's robots.txt tester or just read the file and check if your URL matches any Disallow rules. Robots.txt blocking does not directly cause deindexing but prevents Google from re-crawling, which has a similar effect over time.

Check Search Console for explicit signals

Search Console's URL inspection tool will tell you why a specific URL is not indexed if Google has a specific reason. The reason categories include "Excluded by 'noindex' tag," "Page with redirect," "Crawled, currently not indexed," "Discovered, currently not indexed," and others. Each category points to a specific cause.

"Crawled, currently not indexed" is the most ambiguous category — Google crawled the page but chose not to index it. The cause is usually content quality or insufficient signals; the fix is harder than the configuration-level causes.

Check for manual actions

If multiple important pages have gone not-indexed simultaneously, check Search Console for manual actions. A manual action affecting indexing is the most severe diagnosis and requires the manual-action reconsideration workflow rather than the standard recovery workflow.

Check the sitemap

Confirm the URL is in your sitemap and the sitemap is submitted to Search Console. A URL that disappears from the sitemap will eventually get dropped from the index even if it remains live.

Request reindexing

Once you have identified and fixed the underlying cause, use Search Console's URL inspection tool to request reindexing of the specific URL. This is essentially free and tells Google to recrawl sooner than it would naturally. Most pages return to the index within 1-3 days after this request when the underlying cause is configuration-level.

Recovery timeline expectations

Configuration-level causes (canonical tags, noindex tags, robots.txt) typically recover within 1-7 days of the fix plus reindex request. Content-quality causes ("Crawled, currently not indexed") recover slower — sometimes 30-60 days — and may not recover without substantial content improvement. Manual actions recover after Google reviews the reconsideration request, typically 2-4 weeks.

When the page does not come back

If you have fixed the obvious causes and the page still does not return to the index after 30 days, the cause is likely content quality. The page is one Google has decided is not worth indexing, regardless of the on-page signals. Recovery requires substantive content improvement — making the page genuinely better than what currently ranks for the target query.

How to prevent this happening unnoticed

A continuous site monitor tracks indexability of every page and alerts on changes. Without this, you might not notice a critical page went not-indexed for weeks. UtilitySEO and similar tools make this the default behaviour rather than a feature you have to configure.

The recovery workflow is mostly checklist work. The unusual part is the speed it can be done — if you catch the issue within hours and fix it within hours, the impact is minimal. If you catch it weeks later, the impact compounds. The workflow itself is the same regardless of when you catch it; the urgency is the variable.