Most website disasters follow the same script. Someone clicks “update” on the live site, a layout breaks or the checkout stops working, and nobody notices until a customer rings. A staging site exists to stop that happening.
It isn’t complicated, and plenty of hosting plans include one. Yet a lot of small business websites are still updated live, with fingers crossed.
What a staging site is
A staging site is a private copy of your website: same design, same content, same plugins, same settings. It lives at a separate address that the public and search engines can’t reach. You make changes there first, check that everything still works, and only then apply them to the real site.
The real site is usually called the live or production site. A third term you may hear is a development site, which is where new features are built from scratch. For most small businesses, live and staging are the two that matter.
What can go wrong without one
Websites are made of many moving parts from different suppliers. The core software, a theme, a set of plugins, the server’s own software. Each is updated on its own schedule, and an update to one can clash with another.
When that happens on a live site, visitors see it. The damage ranges from a slightly broken layout to forms that silently stop sending, payment pages that fail, or a blank screen. And the faults that do the most harm are the quiet ones. A contact form that stopped delivering emails three weeks ago doesn’t announce itself.
When you need a staging site
Use one for anything that could change how the site works:
- Updates to WordPress itself, your theme or your plugins, particularly major versions.
- Updates to the server software, such as a new PHP version.
- Adding or removing a plugin.
- Design or layout changes.
- Anything touching a checkout, a booking system or an important form.
You don’t need one to fix a typo, publish a blog post or swap a photo. Routine content edits are fine to make live.
How the process works
- Copy. Live is copied to staging so the two match.
- Change. The updates or new work are applied to the copy.
- Test. Someone checks the important pages, on a phone as well as a computer. Forms are submitted. A test order is placed.
- Back up. A fresh backup of the live site is taken.
- Push. The changes are applied to live, either by pushing staging across or by repeating the same steps.
- Check again. The same tests are run on the live site.
Step six is not optional. Something that worked on the copy can still behave differently on the live server.
The catch with shops and busy sites
There’s one trap to understand. Your live site keeps changing while you work on the copy: new orders, new customer accounts, new form entries, new comments. If you then overwrite the whole live site with staging, including its database, those can be lost.
For a brochure site this rarely matters. For an online shop or a site with bookings it matters a great deal. The usual answers are to push only the files and not the database, to repeat the changes by hand on live once they’ve been proven safe, or to pause orders briefly during the switch. Ask whoever manages your site which approach they use.
Staging answers “will this break?” before your customers do.
Keeping the copy private
A staging site needs a few safeguards of its own:
- Password protect it so the public can’t stumble on it.
- Block search engines. You don’t want a duplicate of your whole website turning up in Google. Just as important, make sure that block is not carried over to the live site when changes are pushed.
- Stop it sending emails to real customers. Test orders and automated reminders should go nowhere.
- Use test mode for payments.
- Remember it holds real data. A copy of your site includes a copy of your customer records, so it deserves the same care and shouldn’t be left lying around once it’s no longer needed.
Questions to ask your host or agency
- Does my hosting plan include a staging site, and how do I get to it?
- Are updates tested there before they go live, or applied straight to the live site?
- How are changes moved across, and what happens to orders placed in the meantime?
- How often is the live site backed up, and how long would a restore take?
- Who checks the site after each update, and what do they check?
If the answer to the second question is “straight to live”, it’s worth a conversation.
How we handle it
Under our website maintenance and support plans, updates are backed up and checked before and after, and larger changes are tested away from the live site first. The environment itself comes as part of our website hosting.
