Blog / How the internet works /
Staging sites: testing changes before they go live
You click “Update” on a plugin on your live site. The page goes white. Customers are mid-checkout. Your phone starts buzzing.
A staging site is the cure for that exact moment. It’s a private copy of your website where you can break things without anyone noticing.
What a staging site is
Think of a theatre rehearsal. The cast runs the whole play on an empty stage, fixes the mistakes, and only then opens the doors to an audience. Your live site is opening night. Staging is the rehearsal room.
Technically, it’s a full copy of your site (files and database) living at a separate address, such as staging.yourdomain.com or a temporary URL from your host. You make a change there, check that everything still works, and then repeat it on the live site, or push the whole thing across.
When you actually need one
Not every edit needs a rehearsal. Fixing a typo doesn’t. But use staging for:
- Major plugin, theme or WordPress core updates, especially page builders and anything touching forms or checkout.
- Design changes that touch templates.
- Adding a new plugin you’ve never run on this site.
- PHP version upgrades on the hosting side.
- Checkout, payment or shipping changes on a shop.
I covered the thinking behind this in WordPress staging sites: how to test changes safely. This post is the shorter, wider version, and it applies beyond WordPress.
How to get one
Through your host
Many hosts include a one-click staging tool: you press a button and get a copy. This is the easiest route, and it usually has a “push to live” button too. Check your hosting dashboard before paying for anything else.
With a plugin
WordPress has plugins that create staging copies on the same server. They work, but they use your hosting space, and a badly configured copy can send emails or run scheduled tasks as if it were the real site.
Manually
Create a subdomain, copy the files, export and import the database, and change the site address. It’s the most work and the most control. Fine for developers, painful for everyone else.
Other platforms
Shopify doesn’t have a staging site in the WordPress sense, but you can duplicate a theme and edit the copy without publishing it. Treat the unpublished theme as your rehearsal room. Hosted builders vary: some offer a preview or draft mode, some don’t.
The risks nobody mentions
A staging site that’s set up carelessly can cause problems of its own.
It can get into Google
If search engines find your staging site, you suddenly have a duplicate of your whole site in the index. Protect it with a password (best), or at least tick the “discourage search engines” setting. The password is the one that actually keeps crawlers out. I went through this in how to keep a WordPress staging site out of search.
It can send real emails
Staging copies sometimes carry on sending order confirmations or newsletters to real customers. Turn off outgoing email on staging, or use a plugin that catches it.
It can take real payments
If your payment gateway is in live mode on the copy, test orders can charge real cards. Switch the gateway to test mode first.
It can go stale
A shop gets new orders every hour. If you copy staging on Monday, work on it until Friday and then push the whole thing to live, you can overwrite Monday-to-Friday orders. For shops, don’t push the database. Repeat the code or settings changes on the live site, or use a tool that merges only files.
A simple routine for a staging session
- Take a backup of the live site before you start. Staging doesn’t replace backups.
- Refresh the staging copy so it matches live today.
- Make the change on staging.
- Test the things that make money or collect leads: the contact form, the checkout, login, search, and the top few pages on mobile.
- Check the front end and the admin. Some problems only appear in the dashboard.
- Apply the same change to live, ideally at a quiet time of day.
- Check live straight afterwards, and keep the backup handy for a day or two.
Write down what you changed. A short change log is the most useful troubleshooting tool a site can have, because the first question in any problem is “what changed?”.
What staging can’t tell you
Staging often runs on the same server with different traffic, so it won’t reveal performance problems that only show under load. It won’t have your real customers’ data either, so some bugs only appear on live. That’s why step 7 matters.
Do small sites need this?
If your site is a five-page brochure that you rarely touch, probably not. A backup and a careful hour is enough. But once the site takes orders, collects leads or runs more than a handful of plugins, a staging copy is cheap insurance. The first time it saves you from a white screen, it has paid for itself.
Key takeaways
- Staging is a private copy of your site for testing changes safely.
- Use it for big updates, design changes, new plugins and anything touching checkout.
- Keep it out of Google with a password, and switch off live emails and payments.
- On shops, never overwrite the live database with an old copy.
- Always keep a fresh backup of the live site as well.
FAQ
Is staging free?
Often yes, if your host includes it. Plugins and managed tools vary in price.
Does staging hurt my SEO?
Only if it’s left open to search engines. Password-protect it.
Should I test on staging or just back up and risk it?
For small low-stakes edits, a backup may do. For anything that touches money or lots of pages, use staging.
Related reading
Next time a big update is waiting, ask yourself one thing: if this goes wrong, how many customers will see it? If the answer is “all of them”, use staging.