Site deindexed from Google: how to recover, cause by cause

Prove the site is really deindexed in Search Console, then fix the cause: noindex, robots.txt, a manual action, a hack, a removal request or an expired domain.

If the site dropped out right after a release, start with the deploy triage instead: it covers the staging settings that most often ship to production.

When a site disappears from Google, the recovery path depends entirely on the cause, so prove the deindexing, isolate the cause, then apply the one documented fix for it. A stray noindex needs removal and a request-indexing round that can take a day or two, or up to a week or two. A manual action needs a site-wide fix and a reconsideration review Google says takes several days or weeks. A security issue needs cleanup and a security review, while a temporary removal may only need cancelling in the Removals history.

Work the checks in this order: first confirm the site is genuinely out of the index, then rule out self-inflicted technical causes, then the three externally documented causes: manual actions, security issues and removal requests. The deindex-triage tool runs the technical checks in one pass and marks each cause ruled out or suspect, with the header line or robots rule as evidence.

First, prove the site is actually deindexed

The site: operator looks decisive and is not. Google documents that “The site: operator doesn’t necessarily return all the URLs that are indexed under the prefix specified in the query.” For a bare prefix query it also notes: “It will generally show the shortest URL for the prefix at the top, but otherwise the results are relatively random.” An empty site: result is a warning sign, but per-URL truth comes from Search Console.

Three checks, in order:

  1. The right property. Google’s help article on missing traffic names the classic mistake: “Mixing up http and https is probably the most common reason for “missing” search traffic”. Look at every property you own: both scheme variants, and www and non-www.
  2. The Page indexing report. Google’s debugging guide is direct: “If it’s a site-wide issue, check the Page indexing report.” Look for an index count that collapsed alongside “a corresponding spike in issues detected”, and note which pages fell out: everything, or one template or section.
  3. URL Inspection with the live test on three to five key URLs. Mind its limits: “‘URL is on Google’ doesn’t guarantee that your page is appearing in Search results.” The tool does not check manual actions, security issues or removals.

Separate this from a ranking drop. If pages are still indexed and impressions fell, you have a performance problem, not an indexing one, and the fixes differ completely. Google’s traffic-drop guide lists the main causes as algorithm updates, technical issues, security issues, spam issues, seasonality, and site moves, and notes the shape of a technical drop: “a misplaced noindex tag, which would depend on Google crawling the page, meaning there would be a slower drop in traffic”. For the ranking case, see why organic traffic dropped overnight; for a fuller indexing walkthrough, see the site disappeared from Google.

Rule out self-inflicted technical causes

These are the causes you can check yourself in minutes, and they hide in plain sight because the site works in a browser for every human visitor. Run each check:

Cause How to confirm What the evidence looks like
noindex meta tag curl -s https://example.com/ | grep -i robots <meta name="robots" content="noindex"> in the HTML
noindex response header curl -I https://example.com/ x-robots-tag: noindex in the response headers
robots.txt block curl -s https://example.com/robots.txt Disallow: / or a rule matching key templates, possibly added by a security plugin or staging flag
Canonical to another host curl -s https://example.com/ | grep -i canonical rel="canonical" pointing at a different domain or the wrong www variant
5xx or 403 to Googlebot server-error-5xx in Search Console, crawl stats Googlebot receives 5xx or 403 while a browser receives 200
DNS, TLS or domain expiry rdap lookup for the domain; certificate dates Name servers changed, certificate expired, registration lapsed

Notes on the table:

  • A robots.txt block is invisible in a browser because Disallow only affects crawlers, so test rules rather than eyeballing them: the robots.txt tester does exactly that. Remember the separate effects of noindex and Disallow if you run both.
  • An indexability check (the tool is here) folds the noindex, header and canonical checks into one request per URL.
  • If the browser gets a good page but Search Console shows crawl errors, check what Googlebot itself receives: the crawler diff checker compares what Googlebot and a normal browser get, which is also how you catch cloaked or bot-blocked responses.
  • DNS and TLS failures happen before any HTTP response exists, so there is no status code to debug, only silence. Check the certificate and registration dates with the SSL and domain expiry checker, and if the domain itself lapsed, read what happens when a domain expires for SEO.

Once a technical cause is found, fix it at the source (the template, the plugin, the edge config), not page by page, then move to the re-request step at the end of this article.

Manual actions: fix the whole site, then request review

A manual action is announced in Search Console, in its own report. Two quotes cover the mechanism and the notification: “If a site has a manual action, some or all of that site will not be shown in Google search results”, and: “we will notify you in the Manual actions report and in the Search Console message center”. The cause is always a person, not an algorithm: “Google issues a manual action against a site when a human reviewer at Google has determined that pages on the site are not compliant with Google’s spam policies.”

The report names the specific type, and the type dictates the fix. The documented list includes back button hijacking, third-party spam abuse, user-generated spam, spammy free host, structured data issues, unnatural links to and from your site, thin content with little or no added value, cloaking and sneaky redirects, hidden text and keyword stuffing, cloaked images, sneaky mobile redirects, AMP content mismatch, News and Discover policy violations, and site reputation issues.

Recovery has one non-negotiable: fix everywhere. “Fixing the issue on just some pages will not earn you a partial return to search results.” Google also gates the review on access: “affected pages should not require a login, be behind a paywall, or be blocked by robots.txt or a noindex directive.”

Then file the reconsideration request in Search Console. A good one does three things: “Explains the exact quality issue on your site.” “Describes the steps you’ve taken to fix the issue.” “Documents the outcome of your efforts.” For link actions, note the warning: “Simply disavowing all backlinks without attempting to remove them might lead to rejection of your request.” If you bought the site recently, say so: “let us know in your reconsideration request that you recently acquired the site and that it now no longer violates the policies.”

Timing, in Google’s words: “Most reconsideration reviews can take several days or weeks, although in some cases, such as link-related reconsideration requests, it may take longer than usual to review your request.” While a request is open, do not file another one: “Please don’t resubmit your request before you get a decision on any outstanding requests.”

One more thing to consider before you file: some policy problems produce partial invisibility without ever appearing in the Manual actions report. The spam policies page states plainly: “Sites that violate our policies may rank lower in results or not appear in results at all”, and that Google detects them “both through automated systems and, as needed, human review that can result in a manual action”. Named examples include scaled content abuse, where “many pages are generated for the primary purpose of manipulating search rankings and not helping users”, and expired domain abuse, where “an expired domain name is purchased and repurposed primarily to manipulate search rankings by hosting content that provides little to no value to users”. If you acquired the domain recently, find out how it was used before you bought it.

Security issues: clean the site, then request a review

The Security issues report is where a hacked site shows up. Google’s scope statement: if an evaluation finds that your site “was hacked”, or that it behaves in a way that could harm a visitor or their computer, “the Security issues report will show Google’s findings.” The categories are “Hacked content”, “Malware and unwanted software”, and “Social engineering”. Aside from visibility, affected pages “can appear with a warning label in search results or an interstitial warning page in the browser when a user tries to visit them”.

The report lists example affected URLs, and Google cautions on scope: “This list is not necessarily complete, but just a sample of pages on your site affected by the selected issue.” So clean the whole site, not just the sample: remove injected scripts, close the entry point, update the software that let the attacker in.

When everything is clean, request a review from inside the report. Review time: “A review can take from a few days to a few weeks to complete.” Do not jump the queue in the other direction either: requesting a review before the cleanup is done “can cause longer turnaround time for the next request, or even get you marked as a repeat offender”. And resist the panic move during cleanup: “we don’t recommend blocking your entire site, or blocking URLs that you’ll eventually want indexed.”

Check the Removals tool history

A removal request hides pages from results, which looks exactly like deindexing from the outside. It is easy to overlook, because a request filed by someone outside your team can hide pages too.

First, your own filings: check the Removals history table in Search Console. To undo one: “Click the menu button next to the request and select Cancel request.” Two properties to know: “A successful request lasts only about six months”, and “The request usually takes up to a day to process, and is not guaranteed to be accepted.” A prefix removal on https://example.com/ covers the whole site across http, https, www and non-www, so one careless request can hide everything.

Second, someone else’s request. Google’s missing-traffic article is explicit: “See if someone has filed a successful URL removal request on your site. If so, you’ll have to cancel or dispute the request to appear in search again.”

Last, the limits of any removal: “Blocking a URL does not prevent Google from crawling your page, only from showing it in Search results.” So the pages stay crawlable while hidden, and what you need after cancelling is for Google to process the change.

After the fix: the timescales Google documents

For technical fixes on specific pages, use URL Inspection and its request-indexing action, after the live test passes. Google’s own framing of speed: “Indexing typically takes only a day or so, but can take much longer in some cases”, or “Indexing can take up to a week or two”. Expect caps and gates: “There is a daily limit to how many index requests you can submit”, “Submitting a request does not guarantee that the page will appear in the Google Index”, and “You cannot request indexing if the page is considered to be non-indexable in the live test”. Fix the live-test failure first; requesting cannot override it.

For site-wide fixes, resubmitting changed URLs one by one is the wrong move; submit the fix and let validation run. In Search Console’s fix-validation flow: “Validation and re-indexing can take a week or two”. For recrawl of larger changes: “Crawling can take anywhere from a few days to a few weeks”, and patience is enforced: “requesting a recrawl multiple times for the same URL won’t get it crawled any faster.”

One caution applies across every cause: “some changes can take effect in a few days, while others could take several months”, and “there’s no guarantee that changes you make to your website will result in noticeable impact in search results”. Plan comms around ranges, not dates.

The full sequence in one place:

1. Confirm property variants: http/https, www/non-www
2. Page indexing report: how much went missing, which templates
3. URL Inspection + live test on 3-5 key URLs
4. curl -s https://example.com/ | grep -i robots   (noindex meta)
5. curl -I https://example.com/                    (X-Robots-Tag, status)
6. curl -s https://example.com/robots.txt          (Disallow /, staging refs)
7. Check rel=canonical host on key templates
8. Crawl stats: 5xx/403 trend against the drop date
9. RDAP + certificate dates: expiry, registrar or nameserver change
10. Manual actions report: empty?
11. Security issues report: empty? If not: clean everything, then request review
12. Removals history: cancel your own requests, dispute others'
13. Fix at source, validate or request indexing, then stop and wait

Keep it from happening again

Recovery ends when nothing else can quietly drop the site, and the checks above are cheap to automate. stillindexed re-checks up to 25 monitored URLs per site every 30 minutes on Starter, or 15 minutes on Agency, so a new noindex, a canonical change, a redirect or a 5xx pings you by email and Telegram instead of being discovered at the next traffic review. robots.txt is read hourly with a confirmation re-read before alerting, sitemaps and TLS certificates are checked daily, and domain expiry weekly. There is a 30-day trial, 3 sites, no card required. Then walk the audit once before the next deploy: the post-deploy SEO checklist covers the release-day version of step 4 through 9.

Sources

Questions

How do I know if my site is deindexed rather than just ranking badly?
Check the Page indexing report in Search Console for a site-wide fall in indexed pages, then run URL Inspection live tests on key URLs. The site: operator is unreliable: Google documents that it does not necessarily return all indexed URLs for the prefix. In a ranking drop, indexed counts stay stable and clicks decline; in deindexing, indexed pages disappear.
How long does recovery from a deindexed site take?
It depends on the cause. Google says crawling can take a few days to a few weeks, validation and re-indexing can take a week or two, reconsideration requests take several days or weeks, and security reviews take from a few days to a few weeks. Link-related reconsideration requests can take longer than usual.
Do I need a reconsideration request to get my site back in Google?
Only if a manual action caused the deindexing: that happens when a human reviewer at Google judged pages non-compliant with spam policies. Fix the issue site-wide, then file a reconsideration request that explains the exact quality issue, describes your fix steps and documents the outcome. Fixing only some pages does not earn a partial return.
Someone filed a removal request on my site. Can I undo it?
If you filed it, open the removal history, click the menu button next to the request and select Cancel request. If someone else filed a successful request, Google's guidance is that you must cancel or dispute it for pages to appear again. Temporary removals also expire on their own after about six months.
Why does URL Inspection say the URL is on Google but the page gets no traffic?
URL Inspection checks indexability on a per-URL basis, not everything that affects visibility. Google states that 'URL is on Google' does not guarantee the page appears in Search results, and the tool does not check manual actions, security issues, or temporary removals. Cross-check the Page indexing report, the Manual actions report and the Security issues report.