What Is a Staging Site and Why Does My Developer Want One?

A staging site is a private copy of your website where your developer can test updates and changes before they touch the live site your customers see. It is the same pages, design and plugins, on a separate address that is hidden from search engines and usually behind a password. If an update breaks something on the staging copy, nobody outside the business ever knows. If it works, the same change is applied to the live site with confidence.

Why the live site is a bad place to experiment

A modern website is built from a core system, a theme and a dozen or more plugins, each updated by a different author on their own schedule. Most updates are fine. Some are not, and the one that is not takes down the contact form, the checkout or the whole site at an hour nobody is watching. On a site with no staging copy, every update is applied live and the first person to find the problem is a customer. A staging site moves the surprise somewhere harmless.

Larger changes are riskier still. A redesign, a new booking system or a change to the way the site sends email can take days to get right. Doing that on the live site means customers see it half built. Doing it on staging means they see nothing until it is finished.

How it is used

The usual cycle is simple. Copy the live site to staging. Apply the updates or make the changes there. Check the pages that matter, especially the forms, the checkout and anything that sends email. If it all works, apply the same updates to the live site, or push the staging copy over the live one. If it does not, fix it on staging first, with the live site untouched.

Good hosting includes a staging feature that creates and refreshes the copy in a few clicks. Without it, a developer has to build one by hand each time, which is why it was skipped on so many older sites.

What it costs you

Usually nothing beyond a hosting plan that includes it, and a little more of the developer’s time per update because they test instead of hoping. Against the cost of a broken checkout over a long weekend, that is cheap. The staging copy should be refreshed from the live site before each round of work so it reflects current content, and it should be protected so neither customers nor search engines stumble across it.

What to do next

Testing updates on a staging copy before they reach the live site is standard practice in our website care and hosting service, which is why sites under it rarely break after an update. For what happens when updates go live without a check, our post on why your contact form is not sending you emails covers one of the usual results.

Does a staging site affect my Google ranking?
Not if it is set up properly, hidden from search engines and behind a password. An unprotected copy can confuse Google, which is why it must be protected.

Can I see the staging site myself?
Yes. Ask your developer for the address and password. It is a good place to review changes before you approve them going live.

Do I need one for a small brochure site?
It is less critical, but still useful, because even a five page site has a contact form that an update can break.

If this is happening in your business and you would like it sorted, call DM1 on (08) 6202 6012 or send us a message. We look after IT, Microsoft 365, websites and domain names for Perth small businesses.

Need IT help? Chat with us
DM1
DM1 Assistant
Perth IT Support Guide
Scroll to Top