Why changes should go on a staging site first

A staging site is a private copy of your website where a change can fail without a customer seeing it. What it catches, the one way it can hurt you, and what to ask your host for.

A developer updates a plugin on your website on a Thursday afternoon. They click round the home page, it looks fine, and they move on. On Monday you notice there have been no online orders since Thursday. The payment page has been failing for four days, and nobody saw it because nobody tried to buy anything except your customers.

A staging site is the thing that would have caught it. Most WordPress hosts can give you one, and a lot of small business sites go without because nobody asked.

What a staging site is

A staging site is a full copy of your website, kept at a separate private address, often something like staging.yourbusiness.co.uk. It has the same theme, the same plugins, the same pages and a copy of the same database. Customers never see it and Google should not either.

The idea is that every change happens twice. First on staging, where somebody makes the change and then tests it properly. Then on the live site, once the copy has proved the change works. If something breaks on staging, nobody loses an order and nobody sees a broken page. You fix it there, or you decide not to make the change at all.

It also gives a developer somewhere to work that is not your shop window. Rebuilding a page, trying a new plugin or changing the theme on a live site means customers watch the work happen, mistakes included.

The faults it catches

The faults worth worrying about are the quiet ones. A white screen gets noticed in minutes. These do not.

A checkout that stops at the payment step. Online shops on WordPress usually run on WooCommerce, with a separate plugin connecting it to Stripe, PayPal or your bank. Those pieces get updated by different people on different days. Now and then an update to one leaves the others out of step, and the basket works, the address form works, and then the payment step fails or spins forever. The site looks healthy to anybody who stops short of paying. On staging, with the payment plugin in test mode, somebody puts a test order through after the update and sees the failure before a customer does.

A menu that stops working on phones. Somebody changes the theme, or updates it, or adds a plugin that loads its own scripts. On a desktop the menu across the top looks fine. On a phone the menu is the little three-line button in the corner, and after the change tapping it does nothing. More than half your visitors are probably on a phone, and none of them can get past the home page. The person who made the change checked it on their laptop. On staging the checklist includes a phone, so it gets found.

A contact form that sends nothing. A change to the email settings or a form plugin update can stop enquiries arriving without any error on screen. Our post on contact forms that stop sending email covers why. Submitting the form on staging and checking where the message lands takes two minutes.

All three share a pattern. The site loads, the dashboard looks normal, and the fault shows up only when somebody does the thing a customer does.

Copying down is safe, pushing back up is not

This part of staging causes real damage, so it is worth understanding before you use one.

Your WordPress site has two halves. The files are the theme, the plugins and the images. The database holds everything else: your pages and posts, your settings, and on a shop every order, customer account and stock level. On most sites the database changes all day long, because customers keep using the site while you work.

Copying the live site down to staging is safe. It takes a snapshot of both halves and puts it somewhere private. Nothing on the live site changes. Do it as often as you like, and do it before each round of testing so staging matches what customers are using.

Pushing the staging database back up to the live site is the dangerous direction. It replaces the live database with the copy. Suppose staging was copied on Monday and pushed back on Friday. Every order taken between Monday and Friday is gone, along with every enquiry, every new customer account, every review and every stock change. The customer has paid and you have no record of the order. Some hosts put a “push to live” button right next to the staging controls, and it is easy to press without reading what it does.

The safe way back up is to repeat the change on the live site rather than copy the result across. If staging proved that a plugin update works, run the same update on the live site. If you changed a setting, change the same setting on live. Where a hosting panel offers to push changes up, choose the option that copies files only and leaves the database alone, and take a backup of the live site first. Our post on what website backups should do covers what a usable backup looks like.

Two smaller things to get right on the copy. Staging has a copy of your customer list, so stop it sending emails, or a test order can email a real customer a confirmation for something they never bought. And keep the payment plugin in test mode, so a test order cannot take real money.

When you do not need it

Staging is for changes with some weight to them. A routine plugin update on a brochure site with a backup behind it does not need a rehearsal, and our post on whether to click Update All explains why updating promptly is safer than waiting. Fixing a typo on the About page does not need one either.

Use staging for anything that touches the checkout or the payment plugins, a theme change or theme update, a major version of a big plugin such as WooCommerce or a page builder, a change of PHP version, and any work a developer is doing over more than an afternoon.

What to ask your host

Most decent hosts can provide staging. Ask them these four questions:

  • Can I have a staging copy of my site, and how do I refresh it from live? Refreshing should be a button or a quick request, not a project.
  • Is the staging site hidden from Google and the public? It should be behind a password or at least marked noindex, or Google may find two copies of your site.
  • Does staging stop sending email? If it does not, ask how to switch it off.
  • When I push changes back, does it copy the database? You want a way to push files only, or a clear warning before the database goes across.

If the answer to the first question is no, that tells you something about the hosting. On a cheap shared plan, staging is often missing or locked to a higher tier.

The short version

A staging site is a private copy of your website where changes get tested before customers meet them. It catches the faults that do not announce themselves, like a checkout that fails at the payment step or a menu that stops opening on phones. Copy the live site down as often as you like, and never copy the staging database back over live.

If you would rather somebody else ran the copy and did the testing, our Care & Hosting plan includes it for £49 a month, and we move your site across for free.

Would you rather somebody sorted this for you?

We look after websites for £49 a month — hosting, updates, backups, security and small changes. Moving an existing site over is free. Or get a free review first and we will tell you what is actually wrong with the one you have.

Get a free website review See Care & Hosting