Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is a Staging Site? A Plain Explanation

What Is a Staging Site? A Plain Explanation

Short answer

A staging site is a private copy of your live site where you test changes before visitors see them. It runs at its own address, hidden from search engines, so you can test updates, redesigns, and new code safely.

Key takeaways

  • A staging site is a private copy of your live site for testing changes before visitors see them.
  • Each staging copy is a separate WordPress install with its own address.
  • Kinsta gives every install one free Standard staging environment; WP Engine includes one per site.
  • Staging sites are hidden from search engines by default on most hosts.
  • Always back up the live site before pushing staging changes to production.

What is a staging site?

A staging site is a private copy of your live site where you test changes before visitors see them.

It holds the same theme, plugins, content, and settings as the live site, but it runs at a different address. You can break things there, fix them, and try again, all without touching the site your readers use.

Kinsta describes its staging environment as completely separate from the live production site, and built for testing new WordPress versions, plugins, code, and general development work. That is the whole point: a safe place to try changes first.

How does a staging site differ from your live site?

A staging site looks the same as the live site, but it is a separate install with its own address, and search engines cannot see it.

WP Engine groups a site into up to three environments: Production, Staging, and Development. Each environment is a separate WordPress install, and changes in one never affect the others. Only Production can be taken live with a custom domain.

The address gives it away. A Kinsta staging site lives at an address such as stg-sitename-environmentname.kinsta.cloud, while a WP Engine staging site uses environmentname.wpenginepowered.com. WordPress.com builds the staging address by adding staging- plus four random characters in front of the live address.

The staging copy also runs with different settings. Kinsta turns off full-page caching and OPcache on staging by default, since the copy is for testing, not for serving readers. If you run a speed check there, expect slower numbers than on the live site.

What can you test on a staging site?

You can test plugin updates, theme changes, new code, design work, and WordPress core updates.

Plugin updates are the most common job. Update the plugin on staging, click through the pages it affects, and check that forms, checkouts, and menus still work. If something breaks, you fix it on staging and the live site never notices.

Core updates belong on staging first too. WordPress 7.1.4 came out on 28 October 2026 as a security release, and Patchstack counts 22 vulnerabilities fixed across 17 advisories in that release. A staging copy lets you confirm the update works with your theme and plugins before you apply it live.

You can also test a redesign, a new checkout flow, or a PHP version change. Kinsta lists new WordPress versions, plugins, code, and general development work as the main uses for its staging environments.

How do you create a staging site?

Use your host's one-click staging if it has one, or a staging plugin if it does not.

On Kinsta, each WordPress install includes a free Standard staging environment. Open the site in MyKinsta, click the environment name, and pick “Create new environment”. You then choose Standard or Premium and pick one of three setups: clone an existing environment, install a fresh WordPress, or create an empty environment.

The two types differ in power: Standard gives you 2 PHP threads, 1 CPU, and 8 GB RAM. You can add up to 5 Premium staging environments per site.

FeatureStandard stagingPremium staging
CPU112
RAM8 GB8 GB
CDNNoYes

On WP Engine, open the Sites page, pick your site, and click “Add environment”. A site holds up to one environment of each type, for a total of three. Pick Staging as the type, give it a name, and wait for the setup email.

On WordPress.com, staging needs the Business or Commerce plan. Any administrator can create one staging site per production site from the hosting dashboard, by opening the Production drop-down and picking “+ Add staging site”. The WordPress.com staging guide lists what copies over and what does not.

If your host has no staging tool, a plugin can build the copy. WP Staging has more than 100,000 active installations on WordPress.org and clones the site into a subfolder of your hosting account.

Our guide to how to set up a staging site for WordPress walks through the host and plugin routes step by step.

How do you move changes from staging to live?

Push the staging copy to live from your host dashboard, or copy the changed files and database by hand.

Kinsta calls this a push: when your changes work on staging, you push the environment to live from the MyKinsta dashboard. WP Engine calls it a copy: pick the staging environment, open the copy tool, and copy it to production.

WordPress.com lets you sync the database and the file system between staging and production in both directions. Syncing the database also replaces the user list on the destination site, so add users to production before you create or refresh the staging copy.

Take a backup of the live site before you push. A push overwrites the live files and database with the staging versions, so any orders, comments, or signups that arrived on the live site after you made the copy can be lost.

Our guide to how to back up a WordPress site covers the backup step.

How do you keep a staging site out of search results?

A staging site should block search engines, and most hosts do this for you.

Kinsta turns off indexing on staging sites by default, using the “Search Engine Visibility” setting in “Settings → Reading” plus an X-Robots-Tag: noindex, nofollow, nosnippet, noarchive header on the staging address. These headers cannot be removed from Kinsta staging URLs.

WordPress.com hides staging sites from search engines in all cases, whatever the robots.txt file or the site visibility setting says. A custom robots.txt file cannot make a staging site show in search results there.

Check the setting yourself after you create the copy. Open “Settings → Reading” on the staging site and confirm the box to discourage search engines is checked. Also check that the staging address does not appear in your sitemap or in links from the live site.

When should you refresh a staging site?

Refresh the staging copy whenever the live site has changed since you made it.

A staging copy goes stale fast. New posts, new orders, and new settings on the live site are not in the copy, so a test on an old copy can miss a real problem. Refresh it before any big job, such as a redesign or a WooCommerce update.

Kinsta offers a selective push to update staging from live without deleting the copy, which keeps your staging backups in place. You can also delete the staging environment and create a fresh clone of the live site.

WordPress.com splits storage 50/50 between the production and staging sites, so a large media library leaves less room on each side. Keep the staging copy lean by removing test uploads you no longer need.

Our guide to how to test a WordPress backup shows how to use a staging copy to confirm a backup restores cleanly.

What mistakes should you avoid with staging sites?

The most common mistake is letting the staging copy send live emails or post to social media.

A cloned copy holds your live settings, so a scheduled email, a social sharing plugin, or a cron job can fire from staging as if it were live. Kinsta warns that social scheduling plugins should be turned off on staging, or they may share posts with the staging address attached.

A second mistake is testing with an old copy. If the live site changed after you cloned it, your test results may not match what happens live. Refresh the copy first.

A third mistake is pushing a WooCommerce staging copy to live without care. WordPress.com warns that syncing a staging site to production can wipe out orders and customer details that arrived on the live site after the copy was made.

Pause new orders, compare the data, and restore from a backup if anything goes missing.

A fourth mistake is using the staging copy as a backup. A staging site is a test copy, not a backup, and deleting it is permanent.

WordPress.com notes that deleting a staging site removes all its data and files, and a new staging site starts as a fresh clone rather than restoring the old one.

A fifth mistake is skipping the live check after a push. Open the live site, check the pages you changed, and confirm the version number. Our guide to how to check WordPress version shows where to look.

Our guide to how to update WooCommerce safely covers the store-specific checks.

Frequently asked questions

Can a staging site replace a backup?

No. A staging site is a full copy of your site for testing, while a backup is a saved snapshot for recovery. A staging copy goes stale as the live site changes, and deleting it is permanent, so it cannot replace a real backup.

Do I have to pay extra for a staging site?

Yes, most hosts include staging on their plans. Kinsta gives every install one free Standard staging environment, and WP Engine includes one staging environment per site. WordPress.com offers staging on Business and Commerce plans. If your host has no staging tool, a plugin can build one.

How often should I refresh a staging site?

Staging copies go stale as the live site changes, so refresh the copy before any big job such as a redesign or a WooCommerce update. A test on an old copy can miss a real problem, so start each major test with a fresh clone.

Will a staging site show up in Google?

No. Most hosts hide staging sites from search engines by default, and Kinsta adds a noindex header that cannot be removed. Check Settings and then Reading on the staging copy to confirm the box to discourage search engines is checked.

Can I build a staging site with a plugin?

Yes, but only if the copy is on the same server setup as the live site. A plugin such as WP Staging clones the site into a subfolder of your hosting account, and the free version needs a separate push-to-live step, which is a Pro feature.

What happens to new orders when I push a staging site live?

Pause new orders, compare the data, and restore from a backup if anything goes missing. Syncing a staging copy to production can wipe out orders and customer details that arrived on the live site after the copy was made, so take a backup of the live site first.

Sources

  1. Staging environment Kinsta
  2. Sites and Environments WP Engine
  3. How to create a staging site WordPress.com Support
  4. WP STAGING plugin WordPress.org
  5. WordPress 7.1.4 security release Patchstack

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.