<b>Q: Our staging site got indexed by Google during the rebuild — how bad is it and how do I fix it?</b>

<b>Q: Our staging site got indexed by Google during the rebuild — how bad is it and how do I fix it?</b>

Deep breath — this happens constantly and is very fixable.

Short answer: it's a duplicate-content nuisance, not a penalty. Clean it up calmly.

Long answer: a public staging URL with the finished site is a near-perfect duplicate of production, which can confuse which version Google trusts. The instinct is to slap robots.txt Disallow on staging — but if pages are already indexed, blocking the crawl means Google can't see your removal signal and they linger.

Do this instead:

— add <code>noindex</code> via meta or X-Robots-Tag (do NOT also block in robots.txt yet)
— let Google recrawl and drop the pages
— then put staging behind HTTP auth or an IP allowlist so it never recurs

Next step: remove any robots.txt block on staging, add noindex headers, and request removal in Search Console to speed it along. Lock it behind a password afterward.