Staging Sites

A staging site is a private copy of a website used to build and test changes before they go live. For SEO, the main concerns are keeping it out of search results and making sure test settings, such as noindex tags, are not carried over to the live site at launch.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

What a staging site is

Most development teams work across several environments: a local copy on a developer’s machine, a staging site that mirrors production, and the live site itself. The staging site usually sits on a subdomain such as staging.example.com or a separate test domain. It lets you check redesigns, plugin updates, new templates and migrations without risking the live site or confusing real visitors.

Why staging sites matter for SEO

  • Accidental indexing: if Google finds a staging site, its pages can appear in search results and compete with the real site as duplicate content.
  • Leaked information: unreleased products, prices or draft content can become public.
  • Launch errors: blocking rules used on staging are often copied to production by mistake, causing traffic to drop sharply after launch.
  • Testing value: a good staging site lets you crawl and audit SEO changes before release, which is especially useful during a website migration.

How to keep a staging site out of Google

Google recommends password protection as the most reliable way to keep private content out of search. The common options compare as follows:

  • Password protection (HTTP authentication): the best option. Search engines cannot access the pages at all, and nothing needs removing at launch except the login.
  • IP allow-listing: only approved networks can reach the site. Also very effective.
  • Noindex tag or header: tells search engines not to index pages they crawl. Useful as a back-up, but risky if it is copied to the live site.
  • Robots.txt disallow: stops crawling, not indexing. URLs linked from elsewhere can still appear in results without a description, so it is the weakest option.

Testing SEO on staging

  1. Give your crawler the staging login. Most SEO crawlers support HTTP authentication.
  2. Crawl staging and production, then compare titles, canonicals, status codes and internal links.
  3. Check that canonical tags and sitemaps will reference live URLs, not staging ones.
  4. Test page speed and rendering of new templates.

Launch checklist

  • Remove any sitewide noindex tag, X-Robots-Tag header or robots.txt disallow from the live site.
  • Search the code and database for hard-coded staging URLs in links, images and canonicals.
  • Check the live robots.txt file and a sample of pages straight after launch.
  • Inspect key pages in Search Console to confirm Google can crawl them, and watch indexing reports over the following weeks.

If a staging site has been indexed

Add password protection first. Then use the Removals tool in Search Console, for a verified staging property, to hide the URLs quickly while Google processes the change. Removals are temporary, so the protection must stay in place.

Key Takeaways

  • A staging site is a private test copy of your live website.
  • Password protection is the safest way to keep it out of search.
  • Robots.txt alone does not stop staging URLs being indexed.
  • Crawl staging before launch to catch SEO problems early.
  • Always remove noindex and blocking rules from the live site at launch.

Related Terms

Curious how this applies to your website? Request a free SEO check-up, or keep learning in the SEO Encyclopedia.