Staging Blocks Removed
Also known as Leftover noindex · Staging Disallow
Confirming the production site has no leftover site-wide robots Disallow or global noindex carried over from staging.
What it is
On staging environments teams commonly add a blanket robots.txt Disallow: / or a site-wide noindex meta tag or X-Robots-Tag header to keep the work-in-progress out of search. This check verifies none of those blocks survived into the live launch.
Why it matters
A leftover Disallow: / or noindex is one of the most damaging launch mistakes: it can deindex an entire site and erase organic and AI-search visibility overnight. Because the pages still load normally for users, the problem is easy to miss until traffic collapses.
How to verify
Fetch the production robots.txt and confirm it does not Disallow: / for all user agents, then view-source on key pages for a noindex meta tag. Check the response headers for X-Robots-Tag: noindex and use Search Console's URL Inspection to confirm pages are indexable.
How to fix
Remove the blanket Disallow: / and any global noindex meta tag or X-Robots-Tag from production before or at launch. Make sure deploy pipelines do not promote staging robots rules, then request indexing in Search Console once cleared.
Related terms
- noindex TagA directive, set via meta tag or HTTP header, that tells search engines to keep a page out of their index.
- robots.txtA plain-text file at the site root that tells crawlers which paths they may or may not request.
- XML SitemapAn XML file listing a site's canonical URLs to help search engines discover and prioritize pages for crawling.
- Canonical TagA link element that names the preferred URL for a page so search engines consolidate duplicate or similar versions.
Official references
External, opens in a new tab.
Put this into practice.
Work through every check by hand and turn it into a shareable GEO Score report — or scan your site automatically in seconds.