What is a staging site?
A staging site is a working copy of your live website, usually on a subdomain like staging.example.com or a host-provided URL, where you try out plugin updates, theme changes and redesigns without risking the real site. When the changes work, you push them to production.
For SEO, a staging site has one job: stay invisible. If search engines index it, you get a duplicate of your whole site competing with the original, test content showing up in results, and sometimes customers landing on a half-built checkout. The bigger risk comes later, when settings that kept staging hidden get copied to the live site.
Keeping staging out of search
Google's advice for content that shouldn't be public is to password-protect it, and that is the most reliable option for staging. HTTP authentication, a host's built-in protection toggle, or a login wall stops crawlers and people alike.
The alternatives are weaker:
- noindex works only after Google crawls the page and sees it, and only for Google and other engines that respect it.
- robots.txt
Disallow: /stops crawling, but Google can still index a blocked URL it learns about from links, showing it without a description. - WordPress's Settings → Reading → Discourage search engines adds
noindex, nofollowto every page and a disallow rule to robots.txt. Hydrogen SEO respects it, so every page gets noindex whatever the Robots screen says. Useful, but it's a request, not a lock.
Use password protection, and add noindex as a second layer.
Push-to-live mistakes
Most staging damage happens on launch day:
- Discourage search engines still ticked on production. The live site starts sending noindex, and pages drop out of Google over the following weeks. Check Settings → Reading straight after every push.
- Staging URLs left in the database. Links, image paths and canonical tags still pointing to
staging.example.com. Run a proper search-and-replace, then check a page's source for the old host. - Canonical or hreflang tags referencing staging, which tells Google the real pages are copies.
- A staging sitemap submitted to Search Console by mistake.
The manual action vs algorithmic drop checklist lists the Discourage search engines setting first for a reason.
When staging got indexed anyway
First, lock it with a password so no new URLs get crawled. If staging pages already show in Google, use the Removals tool in Search Console to hide them quickly; removals are temporary, so the password or a noindex is what keeps them out for good. Once Googlebot can no longer see staging content, the copies fall out of the index over time. If the staging host is permanent, consider returning 410 for it once testing ends.
Common questions
Is noindex enough to protect a staging site?
It keeps pages out of Google's index once they are crawled, but anyone can still reach them. Password protection is more reliable and also blocks crawling.
Can a staging site cause duplicate content problems?
Yes. An indexed staging copy duplicates the live site and can compete with it in results until it is removed.
Should I install my SEO plugin on staging?
Yes. Test SEO changes on staging like any other change. Just make sure indexing stays blocked there and is switched back on in production.