Shipping your staging noindex straight to production

Shipping your staging noindex straight to production

The single most expensive indexing mistake: staging ships with a global noindex meta tag (or X-Robots-Tag: noindex header, or Disallow: /), the deploy carries it to production, and your entire site silently falls out of the index over a few weeks. Traffic bleeds before anyone notices.

Where it hides:
— A header (X-Robots-Tag) is invisible in page source — easy to miss
— A leftover "Discourage search engines" CMS toggle
— An environment config that didn't flip on deploy

What catches it:
— GSC's sudden spike in "Excluded by noindex tag"
— URL Inspection showing "Indexing not allowed: noindex detected"

The fix: add a post-deploy smoke check that fetches your homepage and a few key URLs and asserts there's no noindex in the meta and the response headers. Run it on every release. Set a GSC email alert for indexing drops as a backstop.

Best for: any team with a staging environment.
Not for: anyone who only checks page source and ignores response headers.