In short
A page is deindexed when Google removes it from search results after previously including it. The causes, roughly in order of frequency: a noindex tag or robots block introduced by a change; the URL now redirecting, erroring or being canonicalised to another page; Google reassessing the page as low-value or duplicate; a site-wide quality or spam judgement; a manual action; or a hack that replaced or injected content. Search Console's URL Inspection tool reports the specific status; start there before assuming a penalty.
First, confirm it is actually gone
Search for the exact URL in Google, and for a distinctive sentence from the page in quotes. If either returns it, the page is indexed and has lost rankings, which is a different problem with a different diagnosis. If neither does, run the URL through Search Console's URL Inspection tool. It states whether the URL is on Google and, if not, the reason. Most of the rest of this piece is what those reasons mean.
Cause 1: you told Google to remove it
A noindex meta tag or X-Robots-Tag header, added by a plugin update, a theme change, a CMS setting, or a developer who copied staging configuration to production. Or a robots.txt rule that now blocks the page, which does not remove it directly but stops Google from seeing that it is still fine. Or a removal request submitted in Search Console by someone on the team.
URL Inspection reports "Excluded by noindex tag" or "Blocked by robots.txt". Remove the directive, request indexing, and the page returns within days. This is the most common cause and the least dramatic; check it before anything else.
Cause 2: the URL changed or broke
The page now redirects, and Google indexed the destination instead. The page returns a 404 or a 410 after a migration or a CMS slug change. The page returns a 5xx error, or a soft 404, where the server says 200 but the content is an error message. Or a canonical tag now points at a different URL, so Google indexes that one and drops this one.
URL Inspection shows "Page with redirect", "Not found", "Soft 404", "Server error", or "Alternate page with proper canonical tag". Fix the redirect, restore the page, correct the canonical, or accept that the destination page has taken its place. Our migration checklist exists because this cause follows most site changes.
Cause 3: Google reassessed the page
Google periodically re-evaluates whether a page is worth keeping. Thin pages, near-duplicates of other pages on the site or elsewhere, pages with content that has been superseded, and pages Google now judges to add nothing get dropped, especially after core updates. The status is "Crawled, currently not indexed", the same one new pages receive when Google declines them, and the reasoning is the same.
The fix is editorial: make the page substantively better, consolidate it with the pages it overlaps, or accept that it was not earning its place. Requesting indexing without changing the page rarely helps.
Cause 4: the site was reassessed
Many pages dropping at once, around the date of a core update or a spam update, with no technical change on your side, points to a site-level judgement. The Helpful Content system and its successors demote and sometimes deindex large portions of sites that appear to exist for search engines rather than readers, and the scaled content abuse policy targets sites with large volumes of low-value pages regardless of how they were produced.
Check the timing against Google's published update history. The recovery is to remove or improve the low-value pages across the site and wait for the next update; it takes months, and partial cleanups rarely suffice.
Cause 5: a manual action
A person at Google reviewed the site and applied a penalty. Search Console's Manual Actions report says so explicitly, names the reason, and lists the affected pages or the whole site. Pure spam, unnatural links, thin content with little added value, cloaking, and hacked content are the common categories.
Fix the named problem thoroughly, document what was done, and submit a reconsideration request. Reviews take days to weeks. A manual action is the only cause that comes with a notification, which makes it the easiest to identify and among the slowest to resolve.
Cause 6: the site was hacked
Injected pages, spam content added to existing pages, redirects to other sites, or cloaked content shown only to Googlebot. Google detects these, deindexes affected pages, shows a warning in results, and reports it in Search Console's Security Issues report. The site owner often does not know until the traffic disappears.
Clean the site completely, patch the vulnerability, and request a review through the Security Issues report. Then read our note on keeping a site patched, because the same hole will be found again.
The diagnosis in order
- URL Inspection on an affected page: read the status.
- Manual Actions and Security Issues reports: any entries?
- Pages report: how many URLs dropped, and under which reason?
- Timing: does the drop coincide with a site change, a deploy, or a Google update?
- Content: is the page, honestly, worth indexing?
Most single-page removals are causes 1 and 2 and are fixed the same day. Most multi-page removals are causes 3 and 4 and are fixed over months. If the reports are ambiguous, book a call and we will read them with you; the pattern is usually clear from the Pages report.
Common questions
How do I check if a page has been deindexed?
Search Google for the exact URL and for a distinctive sentence from the page in quotes; if neither returns it, run the URL through Search Console's URL Inspection tool, which states whether it is on Google and gives the specific reason if not. Do not rely on the site: operator alone, which is incomplete.
How long does it take to get a page reindexed?
After fixing a directive or a technical error, days, and faster if you request indexing through URL Inspection. After improving a page Google judged low-value, weeks to a couple of months, as it must be recrawled and reassessed. After a site-wide quality judgement, months, usually until the next core update.
Does deindexing mean my site has been penalised?
Usually not. Most deindexed pages were removed by a noindex tag, a redirect, an error, or Google's ongoing reassessment of thin or duplicate content, none of which is a penalty. A manual action appears explicitly in Search Console's Manual Actions report; if that report is empty, the cause is elsewhere.
Why did Google remove my whole site from search?
Site-wide removal is usually a site-wide noindex or robots block introduced by a change, an expired domain or certificate, a hosting outage during crawling, a hack, or a manual action for spam. Check URL Inspection on the homepage, the Manual Actions and Security Issues reports, and whether the site is reachable, in that order.
Can I request that Google reindex a page?
Yes, through URL Inspection's request-indexing option, which queues a recrawl, or by resubmitting the sitemap. It works only after the cause is fixed; requesting indexing for a page that still carries a noindex tag or that Google judged low-value changes nothing. Requests are limited per day, so use them for the pages that matter.
