Book a call Free rebuild
Home/Glossary/Hosting/Staging Environment

Staging Environment

August 16, 2022 Updated November 16, 2026 2 min read

Hosting glossaryA staging environment is a private copy of a live website where changes and updates are tested before they go live.

A staging environment, or staging site, is a working copy of a live website kept somewhere visitors cannot reach, usually on a subdomain such as staging.example.com or an address the host provides. It runs the same code, theme, plugins, and ideally the same server setup as the live site, so changes can be tried there first. If an update breaks something on staging, nobody but the team sees it.

In software teams it is one step in a chain: development (or a local copy on a developer's computer), then staging, then production, the live site.

What to test on staging

  • WordPress core, plugin, and theme updates, especially major versions.
  • A PHP version upgrade.
  • New plugins, redesigns, and custom code.
  • Critical journeys after any change: logging in, submitting forms, searching, and for stores, adding to cart and checking out in the payment gateway's test mode.

Two kinds of check are common. A smoke test quickly confirms the main features still work; user acceptance testing has the site owner or client go through the site as a real user would and sign off before release.

Setting one up for WordPress

Many hosts, particularly managed WordPress hosts, create a staging copy in one click and can push it back to live. Plugins can do the same on hosts that do not, and developers often work on a local copy as well. Whichever method you use, the staging site should match production closely: the same PHP version, the same plugins, and similar caching. A staging site that differs from live can pass tests that the live site then fails.

WordPress-specific pitfalls

  • Overwriting live data. The live database keeps changing after you copy it: new orders, comments, form entries, and user accounts. Pushing the whole staging database back to live erases them. For stores and membership sites, push only files, or bring database changes across selectively.
  • Getting indexed. A public staging site can end up in Google as a duplicate of the real one. Password-protect it, and tick "Discourage search engines from indexing this site" in Settings, then Reading.
  • Emailing real customers. A copied database contains real email addresses. Disable outgoing email or route it to a test inbox, and put payment gateways in test mode.
  • Broken URLs. Moving a site between domains needs a search-and-replace that handles serialized data, such as WP-CLI's search-replace; a plain text replacement in the SQL file can corrupt settings.
  • Scheduled tasks and integrations, such as subscription renewals, CRM syncs, or backups to the live storage bucket, can run from staging unless they are switched off.

Limits

Staging cannot reproduce everything. It does not get real traffic, so it will not show how the site behaves under load, and some problems only appear with live data or third-party services. Staging is also not a backup: keep proper backups of the live site, and take a fresh one before pushing any change.

When the changes are ready, our guide to pushing a staging site to live covers the move safely.

HostList

The hosting directory with no paid rankings.

Compare 30,000+ web hosts and MSPs across 120+ countries, ranked by HRI, an independent 0 to 100 rating built from verified data. Find your perfect web host.

More Hosting terms