What's a staging site, and does my small business need one?
A staging site is a private copy of your website. Changes get made and checked there first, and only go on the real site once they work.
Whether you need one depends on one question: what does it cost you if the live site breaks for an afternoon? If the honest answer is "not much", you can probably manage without. If the site takes orders, bookings or enquiries, it's worth having.
The plain version
Most websites that have been around a while have three places they can live.
Development is wherever the person building it works, often their own computer. Things are expected to break there.
Staging is a copy that looks and behaves like the real thing, on a server, at its own address. Something like staging.yourbusiness.co.uk. It's where you click around, fill in the forms and say "yes, that's right" before anything goes live.
Live (or production) is the site your customers actually see.
The point of the middle one is simple. Your customers shouldn't be the first people to find out an update broke the checkout.
What actually goes wrong without one
Nothing exotic. It's usually ordinary work done directly on the live site:
- A plugin or theme update that changes how a page looks, or stops a form sending.
- A "quick tweak" to the menu or layout that looks fine on a laptop and falls apart on a phone.
- A new feature that works with test data and trips over a real customer's odd address.
- Someone editing the wrong page because the live site and the draft looked the same.
Most of these get fixed within the hour. The cost is the hour, and anything that happened during it. On a shop, that's orders.
When you can skip it
Not every site needs one. If yours is five pages, changes a few times a year and nobody buys anything through it, a staging copy is probably more effort than it saves. A good backup taken just before you make a change, and knowing you can restore it, will do the same job.
It starts to earn its keep when:
- the site takes money, bookings or leads,
- more than one person makes changes,
- there's custom code, not just a theme and some settings,
- or it connects to other systems, such as stock, accounts or a CRM.
If you're on Shopify
Shopify has the basic idea built in for the look of your shop. Its help pages suggest you make a copy of your theme before editing, because "it's a good idea to make a backup copy so that you can discard your changes". You duplicate the theme, work on the copy, and publish it when it's ready. Unpublished themes sit in a Draft themes section until then.
That covers the design. It doesn't cover apps, settings or anything that talks to another system, so those still need testing with care.
If you're on WordPress or something bespoke
Some hosts include a staging option in their control panel, so check yours before paying for anything. Otherwise it's a second copy of the site on the same server or a cheap separate one, with a way to copy changes across.
For a bespoke app, staging is really part of how the software is built and released. If your developer doesn't have one, it's a fair question to ask why.
Three things to get right
Keep it out of Google. A staging site that turns up in search results is confusing at best. Google's guide to controlling what you share says that to keep something private, "you need to password protect it". That's the simplest answer for a staging site: put a password on the whole thing.
If you also add a noindex tag, don't block the same pages in robots.txt. Google's noindex guide points out that if robots.txt blocks a page, its crawlers "can't see the tag".
Don't copy every customer across. It's tempting to copy the live database so staging looks real. But that puts a second copy of your customers' details somewhere that's usually less well looked after. UK GDPR expects personal data to be "limited to what is necessary", in the words of the ICO's data minimisation guide. Made-up test customers, or real ones with the names and emails scrambled, are nearly always enough.
Stop it sending real email. A staging copy of a shop or booking system can cheerfully send order confirmations and reminders to real people. Point its outgoing email somewhere harmless, or switch it off, before anyone starts testing.
What to do about it
- Ask whoever looks after your site: "Where do changes get tested before they go live?"
- If the answer is "on the live site", ask what it would take to set up a copy, and whether your host already includes one.
- If you have one, check it has a password on it and isn't showing up in Google. Search for site:staging.yourbusiness.co.uk (with your own address) and see what comes back.
- Check what customer data is sitting in it, and whether it can send email.
For a simple site, this is an afternoon's work. For a bespoke system, a proper staging setup is part of the job, and it's how the team at Dev Partners handle changes in their support and maintenance work: tried somewhere safe first, then released.
Liked that? Get the next one by email
When a security flaw lands that could affect your server, I'll email you what it means and what to do. Plus the odd opinion piece. Not often, no spam.