Why do pages drop out of the index weeks after being indexed?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 77
Because indexing is not a one-time admission. Google keeps recrawling and re-evaluating pages, and a page indexed in its first weeks can be dropped on a later pass if something about it, or about how Google judges it, has changed. The delay is the gap between crawls, not a delayed reaction to the day you published. Before treating it as a drop, though, confirm it really is one: a page that still sits in the index but ranks lower can look like it vanished in a traffic chart.
Causes on your side
These are the ones to rule out first, because each has a clear fix:
| Cause | What Google does | Where you see it |
|---|---|---|
| A noindex added by a template, plugin, or release | Removes the page once it recrawls and sees the rule | Page indexing status URL marked ‘noindex’ |
| The page now returns a 4xx error | Drops indexed URLs that return a 4xx status | Not found (404) status |
| The server returns 5xx errors for a stretch | Indexed URLs "are preserved in the index, but eventually dropped" if errors persist | Server error status, Crawl Stats host status |
| A canonical now points elsewhere, or a near-twin appeared | Google shows the other URL instead | Duplicate statuses |
| A robots.txt rule now blocks the page | Google can no longer fetch the content, but a blocked URL can stay listed, possibly without a description, if links point to it; a block is not a removal | robots.txt report; URL Inspection |
Both status-code rows come from Google’s HTTP status code documentation.
Causes on Google’s side
If none of the above applies, one explanation is that the page was re-evaluated and not kept, though the status alone does not prove it. Search Console’s Page indexing help calls the “Crawled – currently not indexed” status “a common message for many sites” that “doesn’t necessarily indicate an issue”, which fits movement in both directions. A core update can also change how pages are assessed; Google’s core updates guidance describes those changes as broad and not aimed at specific pages, and pages that sat near the line before the update can land on the other side of it afterwards. If that is what happened, the page’s content did not change, but its standing relative to everything else did.
How to investigate a drop
- Inspect the URL and confirm it is not indexed, and note the status Google gives.
- If the status points to noindex, an error, a redirect, or a duplicate, fix that cause and request indexing once.
- If the status is Crawled – currently not indexed, check the Google-selected canonical and the rendered HTML first, then compare the page with its indexed siblings and with what ranks for its query; the checks in what to do first when a page says crawled, currently not indexed apply. If the losses line up with a core update, read why Google deindexes pages during a core update.
- Check whether a core update finished in the weeks before the drop; a match in dates is context, not proof of the cause.
A page that fell out because of a technical cause can return once the cause is fixed and Google recrawls it; a page that fell out on re-evaluation needs to become a better answer first.
Add a comment