Staging, Production and Not Mixing Them Up

What the second copy is for

Staging is a duplicate of your site, on the same hosting or nearby, that nobody outside can see.

Its purpose is narrow: somewhere to make a change that might break something, look at the result, and fix it before anybody notices.

Plugin updates, a theme change, a new page template, a payment integration, or anything a developer describes as needing testing.

For a small business site that is a genuine improvement, because the alternative is finding out about a broken checkout from a customer.

The problem it introduces

Two copies of a site diverge immediately and continuously.

Somebody edits a page on the live site while a developer is working on staging. An order arrives on live that does not exist on staging. Somebody changes a price in one place.

By the time the staging work is finished, the two databases differ in ways nobody has tracked.

Copying staging over live then destroys everything that happened on live in the meantime, which is how businesses lose a fortnight of orders or a page somebody spent a day writing.

That is the failure worth designing around, and it is more common than anything staging prevents.

The rules that prevent it

• Content is edited on live only, never on staging.
• Structural changes are made on staging first.
• Copying runs one way: live to staging, to refresh it.
• Changes go back as files or a specific change, not a whole database.
• Staging is refreshed from live before each piece of work.
• Nobody works on staging for more than a few days.

The third and fourth are the whole discipline. A full database copy from staging to live is the action that loses work, and it should be treated as something requiring a deliberate decision rather than a routine step.

Keep staging short-lived

The practice that keeps divergence manageable.

A staging copy that has existed for four months is not a test environment, it is a second site nobody can reconcile.

Refresh it from live at the start of each piece of work, do the work, apply the result, and let it go stale until next time.

Where a project genuinely runs for weeks, refresh the content periodically so the gap does not grow, and accept that the reconciliation at the end will need care.

The longer staging lives, the more the eventual merge resembles a migration, which is a much larger job than anybody planned for.

A worked example

A business had a staging site created for a redesign, which ran for about six weeks.

During that period they published four blog posts, updated their prices, and added two staff to the team page, all on the live site.

When the redesign was finished, the developer copied staging over live, which was the straightforward way to deploy it.

The four posts, the prices, and the staff changes all disappeared, and the old prices were live for two days before anybody noticed.

Nobody had done anything unreasonable. There had simply been no rule about which copy was authoritative for content.

They rebuilt the missing content from a backup, and adopted one rule afterwards: content lives on production, and staging is refreshed from it rather than the other way round.

Keep it out of search

A separate risk that is easy to prevent and frequently missed.

A staging site that search engines can reach produces duplicate versions of every page, and occasionally the staging copy appears in results instead of the real one.

Block it properly: a password on the whole environment is the reliable method, since instructions to search engines are requests rather than guarantees.

Check by searching for a distinctive phrase from your site and seeing whether two copies appear.

The same applies to any old copy left on the server after a rebuild, which is the version of this that persists for years.

Do not let staging send email

The mistake that reaches customers, which makes it worse than the others.

A staging copy is a full site with a working database, including customer records, order history, and whatever automated messages the live site sends.

Test an order on staging and it can send a genuine confirmation to a real customer, and a scheduled campaign can go out twice.

Disable outgoing mail on staging as a matter of course, or route it to a single test address.

Ask whoever sets staging up to confirm this specifically, since it is not always handled by default and the consequence is a real message to a real person.

You may not need one

Worth saying, because staging is sometimes recommended for sites that do not warrant it.

A small brochure site, on a host with reliable one-click backups and restores, can reasonably make changes on the live site and roll back if something breaks.

The exposure is a few minutes of a broken page on a site that receives a modest number of visits, which is a proportionate risk.

Staging earns its place where a break costs money immediately: a shop, a booking system, or a site producing enquiries continuously.

Below that, a tested backup and a willingness to restore is a simpler arrangement with fewer ways to go wrong.

The counter-case

The rules above can be too rigid for how small businesses actually work.

Occasionally content genuinely does need creating on staging, because a redesign changes what content is possible, and forcing it onto live is impractical.

Where that happens, the answer is not to abandon the rule but to name the exception explicitly, list what was created on staging, and move those specific items deliberately rather than copying everything.

There is also a cost in discipline: a business that finds the rules onerous will bypass them under pressure, which is worse than a simpler arrangement it would actually follow.

Adopt the one rule about direction, and let the rest be judgement.

The arrangement

1. Edit content on live only.
2. Make structural changes on staging first.
3. Refresh staging from live before each piece of work.
4. Copy back as specific changes, not a whole database.
5. Password-protect staging so it stays out of search.
6. Disable outgoing email on staging.
7. Delete it when the work is finished.

Step four is the one that prevents lost work, and it should feel like a decision rather than a routine step.

Staging appearing in search is covered in the staging site nobody blocked from Google.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.