Hosting · Guide
How to Set Up a WordPress Staging Site
Short answer
To set up a WordPress staging site, use your host's staging tool to clone the live site into a private copy, or build the copy by hand on a subdomain with its own database. Test the change on staging, check the pages and features it touches, then push files only, the database only, or both to live. Password-protect the copy so visitors and search engines cannot reach it.
Key takeaways
- A staging site is a private copy of your live site with its own files and database.
- SiteGround offers staging on GrowBig and GoGeek plans, and WP Engine includes it with all plans.
- Password-protect staging so visitors and search engines cannot reach the test copy.
- A database push overwrites live orders and comments written since the copy was made.
- SiteGround runs an automatic backup each time you push a staging version to production.
What is a WordPress staging site?
A staging site is a private copy of your live site where you test changes before they reach visitors.
The copy has its own files and database, so a broken update or a bad edit stays on staging. Your live site keeps working while you test.
Use staging for plugin and theme updates, redesigns, and any change you cannot undo in one click. Small text edits do not need it.
A staging copy is not a backup. It is a place to test, and it goes stale as soon as the live site changes, so refresh it before each round of testing.
WP Engine groups each site into up to three environments: Production, Staging, and Development. Each one runs on its own, with separate files, database, domain, and cache, so a change in one never touches the others.
Where do you create a staging site?
Most managed WordPress hosts include a staging tool in their panel, and a staging plugin or a manual copy covers hosts that do not.
| Route | How it works | Best when |
|---|---|---|
| Host staging tool | One-click copy in the hosting panel | Your host offers it |
| Staging plugin | Plugin clones the site to a subfolder | Your host has no tool |
| Manual copy | Copy files and database to a subdomain by hand | You need full control |
Check your plan first. SiteGround offers staging on its GrowBig and GoGeek plans, and WP Engine includes staging with all of its WordPress hosting plans.
If your host has no staging tool, a plugin or a manual copy still works. The steps below cover all three routes.
Kinsta gives every WordPress install a free standard staging environment, separate from the live site. You can add up to 5 Premium staging environments if you need more resources or more test copies.
How do you create a staging site on SiteGround?
In SiteGround's Site Tools, open WordPress, then Staging, pick your install, and create a staging copy.
- Log in to SiteGround and open Site Tools for the site you want to copy.
- Go to WordPress, then Staging, and pick the install from the list.
- Click Create Staging Copy, name the copy, and confirm.
- Wait for the copy to finish, then open its admin panel from the staging list.
SiteGround creates the copy on a subdomain such as staging1.yoursite.com. SiteGround's own tutorials describe the copy as a full clone of the live site on a staging subdomain.
Password-protect the staging copy before you share its address. SiteGround's Site Tools has a Protected URLs section under Security for exactly this.
SiteGround's staging list also lets you replicate a copy, rename it, or destroy it when you finish. Replicating is handy when you want a second copy to try a risky change.
How do you create a staging site on WP Engine?
In WP Engine's User Portal, open your site, add a staging environment, and copy production into it.
- Log in to the WP Engine User Portal and open Sites.
- Select your site and choose Add Staging.
- Name the environment and click Create Environment.
- Copy production into staging so the copy holds your real content.
WP Engine groups each site into three environments: Production, Staging and Development, each with its own files, database, domain and cache.
Log in to staging with the same credentials as the live site. The copy is a full clone, so your users and passwords carry over.
WP Engine sends an email when the copy finishes. Wait for it before you log in, or you may land on an empty environment.
WP Engine suggests Staging for minor changes such as plugin updates, and Development for larger work such as building a new theme. Only one environment of each type can exist per site.
An environment name cannot change, and it cannot be reused even after you delete the environment. WP Engine builds the temporary address from that name, such as somesite.wpenginepowered.com.
How do you build a staging copy by hand?
Copy the live files to a subdomain folder, copy the database to a new empty database, and point the copy at both.
- Create a subdomain such as staging.yoursite.com and a new empty database.
- Copy all WordPress files into the subdomain folder.
- Export the live database and import it into the new one.
- Edit wp-config.php in the copy with the new database details.
- Update the siteurl and home rows in the copy's wp_options table to the staging address.
WordPress.org's Moving WordPress guide covers the same moves: new database details in wp-config.php and the siteurl and home rows in wp_options. The Codex guide to moving WordPress covers the same file and database copy for a new location.
Block search engines from the copy with a password or a noindex setting. A staging copy that Google can find may show up in search results.
Back up the live site before you start. See how to back up WordPress.
What should you test on staging before going live?
Test the exact change you plan to ship, plus the pages and features that change touches.
- Update the plugin, theme or WordPress core version and watch for errors.
- Click through the homepage, checkout or contact form, and search.
- Check the site on a phone screen as well as a desktop.
- Confirm forms still send and logins still work.
Test with the same content and settings as live. A staging copy with an old database can hide problems that appear only with current data.
For store updates, follow how to update WooCommerce safely on staging first.
For a PHP change, read how to update the PHP version in WordPress before you touch the live site.
Kinsta turns off full-page caching and OPcache on staging by default, so pages may load slower than on live. Turn caching on under Caching, then Server Caching, if you want to test with it enabled.
Turn off social scheduling plugins on staging. Kinsta warns they may share posts using the staging URL, which can skew your analytics.
How do you push staging changes to the live site?
Push from staging to live with your host's deploy button, choosing whether to send files only, the database only, or both.
SiteGround's staging tool offers Full Deploy and Custom Deploy, so you can push everything or pick which tables go live. SiteGround also runs an automatic backup each time you push a staging version to production.
A database push overwrites live data written since the copy was made, including new orders, comments and form entries. For a busy store, push files only and move the changed settings by hand.
After the push, open the live site and check the pages you changed. If anything breaks, restore the backup made before the push.
If you keep backups with a plugin, see how to restore a backup with UpdraftPlus.
WP Engine's Copy Environment tool moves content between environments, but it does not copy portal settings. Redirect rules, SSL certificates, and cache exclusions stay behind, so check them after a copy.
When should you refresh or delete a staging copy?
Refresh the copy when it no longer matches live, and delete it when the change is shipped and you no longer need it.
A staging copy goes stale fast on a busy site. Recreate it from live before each new round of testing so you test against current content.
Delete old copies when you finish. Each copy uses disk space and can confuse search engines or visitors if it stays public.
If you run several sites, keep one staging routine for all of them. See how to manage multiple WordPress sites.
Kinsta lets you refresh staging with a selective push from live, so you keep your staging backups. You can also restore a backup from production to staging, which keeps any custom domain you added.
On shared WP Engine plans, you cannot add a custom domain to Staging. Premium plans can add one, so check your plan before you promise a client a branded staging address.
What mistakes should you avoid?
These five mistakes cause most staging accidents.
- Testing on live because staging felt slow to set up.
- Pushing the staging database over a live store and wiping new orders.
- Leaving staging open to the public and to search engines.
- Pushing without a fresh backup of the live site.
- Testing against an old copy and missing a bug that only current data shows.
Deleting an environment on WP Engine does not touch the others, but only Owner-level users can do it. WP Engine keeps 30 days of backups, so contact support if you deleted one by mistake.
Frequently asked questions
Do I need a staging site for a small blog?
Not for small text edits, but yes for updates and redesigns. A plugin or theme update can break a layout or a form, and staging lets you catch that before visitors do. If your host includes staging free with your plan, use it for every update.
Can visitors find my staging site?
Only if you leave it open. A staging copy has a public address, such as staging1.yoursite.com, so anyone with the link can open it. Password-protect it in your hosting panel and add a noindex setting so search engines ignore it.
Does a staging site cost extra?
It depends on the host and plan. SiteGround includes staging on GrowBig and GoGeek plans, and WP Engine includes it with all of its WordPress hosting plans. Some budget hosts have no staging tool at all, in which case a plugin or a manual copy is the free route.
Can I use a staging site to build a new site?
Yes. Build the new design on staging while the old site stays live, then push it to production when it is ready. This is one of the best uses for staging, since visitors never see the half-finished work.
What happens to new orders when I push staging to live?
A database push overwrites them. The push replaces the live database with the staging copy, so orders, comments and form entries made since the copy was made are lost. For a live store, push files only and move the changed settings by hand.
Sources
- How to manage your Staging copies? SiteGround Tutorials
- How to clone a WordPress site SiteGround Tutorials
- How To Create And Use WPEngine Staging Environment BlogVault
- Moving WordPress Developer.WordPress.org
- Manage Sites and Environments WP Engine Support
- WordPress Hosting - Staging Environments Kinsta Docs
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.
Thanks — we review requests within 3 business days.
