One day your page is bringing in traffic. The next, it's gone — not ranking lower, but gone. It doesn't appear for its own title. It doesn't appear for your brand name. Search site:yourdomain.com/that-page and Google returns nothing. The page has effectively vanished from search.
This is more alarming than a normal ranking drop, but it's also, in many cases, more fixable — because a page falling out of the index usually has a specific, identifiable cause. The key is to diagnose why it was removed before you try anything, because the recovery path and the timeline depend entirely on the reason.
First: Demoted or Actually Deindexed?
These look similar in your analytics — traffic craters either way — but they're different problems with different fixes.
Demoted means the page is still in Google's index; it just ranks far lower than before. It still shows up if you search its exact title or a very specific phrase from it. You lost position, not presence.
Deindexed means the page is no longer in the index at all. Google won't show it for anything, because as far as search is concerned it doesn't exist.
Run two quick checks to tell them apart:
- Search site:yourdomain.com/the-exact-url in Google. If the page appears, you're demoted. If nothing comes back, you're likely deindexed.
- Open the page in Search Console's URL Inspection tool. It will tell you directly whether the URL is on Google, and if not, it usually gives a reason.
Everything below assumes the page has genuinely dropped out of the index. If it's only demoted, the fix is about content quality and competitiveness rather than getting back in.
Why Pages Get Removed From the Index
There are three broad causes, and they recover on very different schedules.
1. A Technical Signal Is Telling Google to Drop It
This is the most common cause — and the best-case scenario, because it's fully in your control and fast to fix. Something on the page or site is actively instructing Google to remove it, often by accident after a redesign, migration, or CMS change:
- a noindex tag or header left on the page,
- a robots.txt rule blocking the URL,
- a canonical tag pointing somewhere else, so Google indexes the "other" page instead,
- the page returning a 404/410 or a server error when Googlebot visits,
- the URL changed and the old one wasn't redirected.
URL Inspection will usually surface these directly ("Excluded by 'noindex' tag," "Blocked by robots.txt," "Not found (404)," and so on). Fix the technical signal, confirm the live page returns a normal 200 status and is indexable, then request indexing. Recovery here is the fastest of all — often a few days to two weeks once Google recrawls the corrected page.
2. A Quality Judgment: "Crawled – Currently Not Indexed"
If URL Inspection shows no technical error but the page still isn't indexed — often flagged as Crawled – currently not indexed — Google made a value judgment. It fetched the page, decided it didn't earn a spot, and left it out.
Two things matter here. Crawling and indexing are separate decisions: seeing Googlebot recrawl the page does not mean it's coming back — the indexing verdict happens afterward, and repeated crawls with no status change are normal. And since Google merged its helpful-content system into core ranking, this status points to a quality or duplication problem the large majority of the time, not a bug. Thin, scaled, or near-duplicate content is the usual trigger.
The fix is not technical — it's making the page genuinely worth indexing. The test isn't "is this good," it's "does this offer something the pages already ranking for this topic don't." Once you've made a substantial improvement, realistic recovery is roughly one to four weeks: Google typically re-evaluates within one to fourteen days, and quality-demoted pages tend to sit on the longer end, especially if you also add internal links from indexed pages. The hard truth: a page can stay in this state indefinitely if its underlying value never actually changes.
3. A Penalty: Manual Action or Algorithmic Demotion
Sometimes a page (or a whole section) drops because of an enforcement action. There are two kinds, and telling them apart is essential because the recovery process is completely different.
A manual action is a human decision — a Google reviewer flagged a policy violation. You'll see a notice in Search Console under Security & Manual Actions describing the exact problem. This is the more tractable case: fix the specific violation named in the notice, then submit a reconsideration request, which is the only official way to get a human penalty lifted. Google usually responds in two to six weeks, and if accepted, visibility returns over the following weeks — often around two months end to end.
An algorithmic demotion is automatic and invisible. No notice appears; a core or spam update simply re-scored your site around a known update date. There's no reconsideration request — recovery depends on improving the site and waiting for Google's systems to re-evaluate. Because the site-wide quality classifiers refresh on Google's schedule rather than yours, this is the slowest path: commonly four to six months or more, frequently gated by the next core-update cycle. You can rebuild immediately, but Google only re-inspects on its own rounds.
Recovery Timelines at a Glance
- Technical removal (noindex, robots.txt, canonical, 404, server error): a few days to ~2 weeks after the fix is live and recrawled.
- "Crawled – currently not indexed" / quality: ~1–4 weeks after a genuine content improvement.
- Manual action: ~2–6 weeks after a solid reconsideration request; roughly 2 months in total.
- Algorithmic demotion (core/spam update): ~4–6 months, often aligned with the next update.
What Actually Helps — and What Wastes Time
Things that move the needle:
- Fix the real, specific cause. Diagnose with URL Inspection first; don't guess. A technical block and a quality problem need opposite responses.
- Request indexing once after the fix is live — then leave it alone. Resubmitting the same URL repeatedly does not push it up any queue.
- Add internal links from already-indexed pages to the recovering URL. It's one of the strongest signals for pulling a page back in.
- Confirm the live page is actually indexable (returns 200, no stray noindex, self-referencing canonical) before you wait on anything.
Things that waste time or backfire:
- Deleting or rewriting the whole site in a panic. Sweeping changes make it impossible to learn what worked, and for algorithmic drops they won't register until the next evaluation anyway.
- Disavowing links after a core update. Core updates are about content, not links — wrong lever.
- Reacting mid-rollout. Updates take days to weeks to finish. Wait for the rollout to complete, let it settle a few days, then read your data.
- Refreshing Search Console hourly. Recrawls aren't verdicts. Once the fix is in, the most productive thing is often to stop tinkering and let Google's next evaluation catch up.
Bottom Line
A page removed from Google's index is a diagnosis problem before it's a recovery problem. Find the cause — technical block, quality judgment, or penalty — and the timeline becomes predictable: fastest for technical fixes, longest for site-wide algorithmic demotions. Google is explicit that indexing is never guaranteed on any timeframe, but once you've addressed the actual reason substantially and honestly, getting back in is usually a matter of when, not if.