Staging sites: how to review a new website before it goes live
A staging site is a private copy where a new website is built and checked before launch. How to keep it out of Google, what to review, and how to go live.
By Sohail Hussain21 November 20265 min read
A staging site is a private copy of your website, at a separate address, where changes are built and reviewed before the public sees them. A good one is hidden from both the public and search engines, runs on the same setup as the live site, and gets reviewed against a checklist before launch. The two mistakes that cause real damage are letting Google index the staging copy, and carrying its "do not index" setting across to the live site at launch.
Every website redesign and migration we run is built and reviewed on staging, and it is stage four of the website redesign process. This guide covers how to set one up safely, how to review it, and how to go live from it.
How is staging different from the live site?
Most professional setups have three or four environments. They differ in who can see them and what they are for.
| Environment | Who sees it | What it is for |
|---|---|---|
| Local | One developer, on their own computer | Writing and testing code |
| Preview | The team, one link per change | Reviewing a single feature or fix |
| Staging | The team and you, the client | Reviewing the whole site before launch |
| Production | Everyone | The live site |
Platforms such as Vercel create a preview link for every change automatically. Managed WordPress hosts usually offer a one-click staging copy. On a basic shared host, staging is often a subdomain such as staging.example.com with its own copy of the site.
Staging should match production as closely as possible: the same platform version, the same server setup, the same plugins. A site that works on staging and breaks on launch usually differs in one of those.
How do you keep a staging site out of Google?
Google's own documentation is direct on this: robots.txt is not a mechanism for keeping a page out of Google. A page blocked by robots.txt can still be indexed if other pages link to it. The reliable options are a noindex rule or a password.
Best: require a login. Password protection or HTTP authentication keeps out search engines, competitors and curious visitors alike. On Nginx, two lines do it, with a noindex header added as a second layer:
auth_basic "Staging";
auth_basic_user_file /etc/nginx/.htpasswd;
add_header X-Robots-Tag "noindex, nofollow" always;
Good: a noindex header on every response. Google's guide to blocking indexing with noindex covers both the meta tag and the X-Robots-Tag header. The header also covers PDFs and images.
Platform defaults help, with exceptions. Vercel sends X-Robots-Tag: noindex on preview deployments by default, but not when a custom domain is assigned to a non-production branch, according to Vercel's own guide. WordPress's "Discourage search engines from indexing this site" setting, under Settings, Reading, adds a noindex meta tag to every page.
Check the headers yourself rather than trusting a setting:
curl -sI https://staging.example.com | grep -i x-robots-tag
What should you review on staging?
Review the site the way a visitor will use it, then the way Google will read it. A checklist keeps the review complete:
- Content. Every page has real, final copy. No placeholder text, no "Lorem ipsum", no missing images.
- Phones. Each page type opened on a real phone, not just a narrow browser window.
- Forms. Every form submitted, and the message confirmed in the right inbox or CRM. On staging, forms should go to a test inbox so customers never receive test messages.
- Payments and integrations. Tested in sandbox mode, with test keys, never live ones.
- Redirects. The redirect map tested against the staging address. Redirect mapping includes a script for this.
- SEO settings. Titles and descriptions on every page, and canonical tags pointing at the production domain, not the staging one. The canonical tag generator shows the correct form.
- Speed. Key templates measured, bearing in mind that a password-protected site cannot be tested by public tools until the password is lifted.
- Analytics. Either off on staging or sent to a separate property, so test visits do not pollute real data.
Our launch checklist has the full list of 38 checks.
How should you give feedback on a staging site?
Feedback scattered across emails, calls and chat messages is how fixes get lost. Four habits keep it manageable:
- One list, one owner. A shared spreadsheet or tracker, with one person on your side collecting everyone's comments.
- Specific entries. The page URL, the device and browser, what you expected and what you saw. A screenshot helps more than a paragraph.
- Bugs separate from changes. "The form does not send" is a bug. "Can the heading be bigger" is a change. Your contract probably treats them differently; what a website contract should include explains revisions.
- Rounds, not a stream. Review, send the list, wait for the fixes, review again. Two or three rounds is normal.
How do you go live from staging safely?
Launch is the moment staging settings must be undone, and the moment they most often are not. In order:
- Remove the password and the
noindexheader or meta tag from the production site. - Replace the staging robots.txt with the production one, and check it with the robots.txt tester.
- Confirm canonical tags, the sitemap and internal links use the production domain.
- Switch forms, payments and integrations from test to live keys.
- Deploy, or switch DNS, and run the
curlcheck above against the live domain. TheX-Robots-Tagline should be gone.
Keep the staging site running afterwards, protected as before. It is where every future change gets checked. For the first weeks after launch, the week after a migration covers what to watch in Search Console.
Does every site need a staging environment?
Any site that brings in enquiries or sales does. The cost is small, often included in managed hosting, and one broken launch costs more.
A five-page site on a website builder, edited by its owner, is the exception. Wix, for example, keeps edits private until you press Publish, which covers most of what staging is for. A separate staging copy only becomes worth it when changes get larger than a text edit, or when more than one person is making them.
Was this guide useful?