Your site dropped out of Google after a deploy: here's the triage

If pages vanished from Google right after a release, check these first, in order: (1) a noindex meta tag or X-Robots-Tag header shipped from staging, (2) robots.txtDisallow: /, (3) canonicals pointing to the staging or wrong domain, (4) a password or maintenance page, or a 4xx or 5xx, (5) the sitemap removed or broken.

Enter your domain and the triage runs those checks now, with the evidence for each.

Six fetches: the homepage as Googlebot and as a browser, robots.txt, the sitemap, one TLS handshake and one registry lookup, spaced two seconds apart. Expect about ten seconds.

Worked example

Illustrative result for a reserved example domain. Your triage replaces it.

Found it: noindex on the homepage

Each confirmed check below is enough on its own to keep the site out of Google. Fix those first, in the order listed.

Domain
example.com
Homepage resolved to
https://www.example.com/
Tally
1 confirmed · 1 suspect · 7 ruled out
Checked
Thu, 22 Oct 2026 09:00:00 GMT

Crawling: can Googlebot reach the site?

Google crawls first. If the domain, the certificate, robots.txt or the server stops Googlebot here, nothing after this point matters.

  1. ruled outDomain registration

    Registered for another 212 days.

    • RDAP expiry: 2027-05-22
  2. ruled outTLS certificate

    Valid for www.example.com, 61 days left.

    • Host: www.example.com
    • Valid until: 2026-12-22
  3. ruled outrobots.txt answers

    robots.txt answers 200.

    • GET https://www.example.com/robots.txt
    • Status: 200
  4. ruled outrobots.txt rule for the homepage

    Googlebot is allowed to crawl /.

    • Path evaluated: /
    • Googlebot: allowed
    • User-agent *: allowed
  5. suspectHomepage as Googlebot vs a browser

    Googlebot's user agent gets 403 while a browser gets 200. Check the Crawl stats report in Search Console for the same errors from real Googlebot.

    • Googlebot user agent: 403 at https://www.example.com/
    • Browser user agent: 200 at https://www.example.com/

    Next: Crawler versus browser · Search Console: Blocked due to access forbidden (403) · Search Console: Server error (5xx)

  6. ruled outRedirects from the homepage

    1 redirect(s), staying on example.com.

    • 301 https://example.com/
    • 200 https://www.example.com/

Indexing: does the homepage ask to be left out?

A page Google can fetch can still tell it not to index, or name another URL as the one to index instead.

  1. confirmednoindex on the homepage

    The homepage tells Google not to index it (x-robots-tag (*): noindex). Google drops a page from results once it recrawls and sees this.

    • meta robots: none
    • meta googlebot: none
    • X-Robots-Tag: noindex

    Next: X-Robots-Tag checker · Search Console: Excluded by 'noindex' tag

  2. ruled outCanonical on the homepage

    The canonical points at the homepage itself.

    • Final URL: https://www.example.com/
    • rel=canonical: https://www.example.com/

Discovery: can Google find the rest?

A sitemap helps Google find URLs. A broken one is worth fixing, but on its own it does not remove indexed pages.

  1. ruled outSitemap

    Served and parseable, 48 entries.

    • URL: https://www.example.com/sitemap.xml
    • Source: declared in robots.txt
    • Status: 200
    • Entries: 48

How do I confirm the site is actually deindexed?

A site:yourdomain.com search is a rough first look, not proof. The reliable answer is in Search Console: run URL Inspectionon the homepage and a few key pages, and open the Pages report to see which reason is growing since the deploy date (for example "Excluded by 'noindex' tag" or "Blocked by robots.txt"). The live test shows what Google gets from the page now.

Which deploy changes deindex a site?

  1. noindex shipped from staging. A meta robots tag or anX-Robots-Tag: noindex header meant for preview builds reached production. Platform fixes: Vercel,Netlify,Webflow,WordPress,Shopify. Check one URL with thenoindex checker.
  2. robots.txt Disallow: /. The staging robots.txt was deployed. Platform fixes: Netlify,Webflow,WordPress,Shopify.
  3. Canonicals to the staging or wrong domain. A base URL environment variable still points at staging. Platform fixes: Vercel,Netlify,Webflow,WordPress,Shopify.
  4. A password page, maintenance page, 4xx or 5xx. The release left the site behind a lock or serving errors to Googlebot. Platform fixes:Shopify password page,Vercel redirects,Netlify redirects.
  5. The sitemap removed or broken. A missing sitemap does not remove indexed pages on its own, but it slows discovery of the fixed ones. Migration fixes:WordPress,Webflow,Shopify.

How do I fix it and get reindexed fast?

Revert or fix the one setting the triage confirmed, deploy, and run the triage again until every check is ruled out. Then, in Search Console, request indexing for the homepage and the most important pages, and resubmit the sitemap so Google finds the rest. Fix robots.txt and noindex together: Google says a page blocked by robots.txt never shows it its noindex rule. The full recovery walk-through is in site deindexed from Google: recovery.

How long until Google reindexes?

Google does not promise a time. Its recrawl guide says a request does not guarantee inclusion instantly or at all, and that repeat requests for the same URL do not speed it up. Pages come back as Google recrawls them and finds the fault gone. Track progress in the Pages report rather than with repeated requests.

How do I stop it happening on the next deploy?

Run the post-deploy SEO checklist on every release. Put the check in CI with stillindexed Canary or from your editor with the MCP server, so a build that ships noindex fails before it goes out. And watch production on a schedule: thefree noindex monitor alerts when a noindex, robots.txt block or canonical change appears.

If the drop did not follow a deploy, start withwebsite disappeared from Google: six checksor the full deindex triage tool.

FAQ

Can a staging site get my production site deindexed?

Yes, in two ways. If production pages carry a canonical that names the staging host, Google is being asked to index staging instead. And if a staging noindex or robots.txt is deployed to production, Google is told to drop or stop crawling the real site. Google notes that a noindex behind a robots.txt block is never seen, so fix both before asking for a recrawl.

Will requesting indexing in Search Console speed it up?

It helps once the fault is fixed: URL Inspection has a Request indexing button for individual URLs. Google says there is a quota for these requests, that requesting a recrawl several times for the same URL will not get it crawled any faster, and that a request does not guarantee inclusion in results. For many URLs, submit the sitemap instead.

Does Google penalize accidental noindex?

No. Google describes noindex as a rule you set to keep a page out of its index, and it honours it. A manual action is something else: Google issues one when a human reviewer finds pages that break its spam policies. An accidental noindex removes pages until Google recrawls them without it; it does not put a penalty on the site.

Staging leaks in the other direction too: seestaging site indexed by Google.

Google documentation used on this page