In this guide · 8 sections
- 01What a WordPress staging site is and when you need one
- 02Host staging vs a staging plugin
- 03How to create a staging site, step by step
- 04Keeping the staging site out of Google
- 05Syncing the database safely: orders, bookings and form entries
- 06Pushing changes to live
- 07Do it yourself or get help?
- 08Frequently asked questions
Short answer
Use your host's one-click staging if it has one, or a staging plugin if not. Password-protect the copy, test updates there, then push only files (themes, plugins) to live. Don't overwrite the live database on a shop or booking site, or you lose new orders.
What a WordPress staging site is and when you need one
A WordPress site has two parts: the files (WordPress itself, themes, plugins, uploaded images) and the database (pages, posts, settings, users, orders and form entries). A staging site copies both to a separate address, often staging.yourdomain.com or a temporary host URL, so you can break things safely.
You need one when:
- You run WooCommerce, a booking plugin or membership site where downtime costs money
- You are updating a major plugin, a page builder, the theme or a big WordPress version
- You are changing PHP version; WordPress recommends PHP 8.3 or greater on its requirements page
- A developer is redesigning pages and you do not want half-finished work showing
For a simple brochure site, a fresh backup before each update may be enough. Our guide on fixing a WordPress update that broke your site shows what to do when an update goes wrong without staging.
Host staging vs a staging plugin
Host-provided staging
Recommended- One click in the hosting panel
- Copy lives on the same server, not inside WordPress
- Push to live, often with files-only or selective options
- Usually on mid-tier and managed WordPress plans
Best for: Anyone whose host includes it.
Staging plugin
- Works on hosts without staging
- Copy often sits in a subfolder of the live site
- Push to live is often a paid feature
- Large sites can time out on cheap shared hosting
Best for: Sites on basic hosting that cannot move yet.
Local copy on your computer
- Free tools run WordPress on a laptop
- No risk to the server
- Moving changes back is manual
Best for: Developers doing bigger rebuilds.
As an example of plan differences, SiteGround's web hosting page lists staging on its GrowBig and GoGeek plans but not on StartUp, as of October 2026. Managed WordPress hosts such as Kinsta list free one-click staging on their plans. Check your own plan's feature list before installing a plugin.
How to create a staging site, step by step
The exact buttons vary by host, but the order is the same everywhere.
Back up the live site first
Take a full backup of files and database, and check you can download it. WordPress's backup documentation explains why both parts matter.
Create the staging copy
In your hosting panel, find Staging and create a copy, or install a staging plugin and run its clone. Note the staging URL.
Lock it with a password
Turn on the host's password protection for staging, or HTTP authentication. Also tick Discourage search engines from indexing this site under Settings > Reading on the staging copy.
Mark it as staging
Many hosts set the WP_ENVIRONMENT_TYPE constant to 'staging' in wp-config.php. WordPress asks hosts to do this, and some plugins use it to switch off emails or payments on the copy.
Turn off outgoing email and live payments
Switch payment gateways to test mode and pause email sending or automation plugins, so customers do not get duplicate emails from staging.
Test the updates
Update plugins, theme and WordPress on staging. Click through the home page, forms, checkout and booking flow on desktop and mobile.
Keeping the staging site out of Google
A staging copy that Google indexes creates duplicate content and can show customers half-finished pages. The 'Discourage search engines' box in WordPress, described on the Reading Settings screen, only asks search engines not to index the site. It is not a lock.
Google's advice on controlling what you share is to password-protect private content, which keeps it out of Google Search too. Its noindex documentation adds that a noindex rule inside robots.txt is not supported. Use the password first and noindex as a backup.
Syncing the database safely: orders, bookings and form entries
This is where staging goes wrong. The staging copy is a snapshot. Every order, booking, comment, new user and form entry on the live site after that moment exists only on live.
| What you changed on staging | What to push | Risk to live data |
|---|---|---|
| Plugin, theme or WordPress updates | Files only (or repeat the updates on live) | Low |
| CSS, theme templates, child theme | Files only | Low |
| New pages or page builder layouts | Selected pages, or rebuild on live | Medium |
| Settings, menus, widgets | Repeat by hand on live, or push selected tables | Medium |
| Full database push | Only on sites with no orders, bookings or entries since the copy | High on shops and booking sites |
On a WooCommerce or booking site, the safest pattern is: test updates on staging, then run the same updates on live during a quiet hour with a fresh backup. Only push files that changed. If you must push the database, put the live site into maintenance mode first, take a new staging copy, make the change, and push immediately so nothing new comes in between.
Pushing changes to live
Before and after you push to live
If something breaks, restore the backup you just took. Our guide on restoring a website backup walks through it. If a plugin you rely on has a published security hole, update it promptly even if staging is not ready; see what to do about a WordPress plugin vulnerability.
Do it yourself or get help?
If your host has one-click staging, a careful owner can follow this guide in under an hour each month. The risk is the database push on a site that takes orders or bookings, and forgetting to switch payments and search settings back.
Our Care plan (S$129 a month) covers monthly updates of WordPress, theme and plugins, daily off-site backups, monitoring and up to an hour of small changes, so updates go on with a backup in place.
Frequently asked questions
Many do, but often only on mid-tier or managed WordPress plans. For example, SiteGround lists staging on its GrowBig and GoGeek plans but not StartUp, as of October 2026. Check your hosting panel for a Staging tool or ask support. If there is none, a staging plugin can create the copy instead.
Only if search engines can find and index it. Password-protect the staging copy, which Google says keeps private content out of search, and tick Discourage search engines from indexing this site on the staging copy only. After pushing to live, check that setting is unticked on the live site.
Yes, if you push only files such as plugins and themes, or repeat the updates on live. Pushing the full staging database replaces the live database, so any orders, bookings, comments or form entries made since the copy was taken are lost. On shops, avoid full database pushes or do them in maintenance mode.
For a small brochure site, a tested backup before each update is often enough, because you can restore if something breaks. For shops, booking sites and anything with daily orders, staging is better, because restoring a backup also rolls back new orders and causes downtime while you fix it.
Yes, the copy should match live as closely as possible, otherwise your test proves little. The exceptions are payment gateways in test mode, outgoing email paused, search engines blocked and a password on the site, so customers never see or get messages from the staging copy.