All articles Updates

WordPress Staging: How to Test Changes Safely Before They Go Live (2026)

What a WordPress staging site is, when you need one, three ways to create it, the settings that prevent costly mistakes and how to go live without losing orders or form entries.

WP Beekeeper Team · 12 min read
Two laptops showing the same website, with an arrow from the staging copy to the live site

Every WordPress site owner knows the moment: an update is waiting, a new plugin looks useful, the theme needs a change. On a live site, every one of these is a small gamble. Most of the time nothing happens. Sometimes the layout breaks, the checkout stops working or the site shows a critical error, and your visitors see it before you do.

A staging site removes the gamble. It is a private copy of your website where you can test updates, plugins, design changes and PHP upgrades without anyone noticing. If something breaks there, you fix it calmly. If everything works, you apply the same change to the live site.

This guide explains what a WordPress staging site is, when you really need one, the three ways to create it, the settings that prevent embarrassing mistakes and, most importantly, how to bring your changes live without overwriting new orders or form entries.

Key takeaways

  • A staging site is a private copy of your live WordPress site for testing changes before they go live.
  • Use staging for major updates, new plugins, theme or design changes, PHP upgrades and anything that touches the checkout.
  • The easiest way is one-click staging from your host. Plugins and a manual copy on a subdomain are the alternatives.
  • Always hide staging from Google, block outgoing emails and put payments into test mode.
  • The hardest part is going live: on sites with orders, bookings or form entries, never overwrite the live database with the staging one.
  • For routine minor updates, a backup right before the update plus a visual check afterwards is often enough. Staging is for the risky changes.

What is a WordPress staging site?

A staging site (also called a staging environment or test site) is a complete copy of your WordPress website: the same files, the same database, the same plugins and theme. It runs on a separate address, for example staging.yourdomain.com, and is not visible to visitors or search engines.

The idea comes from software development, where code usually moves through three environments: development (where it is written), staging (where it is tested under real conditions) and production (the live site). For most WordPress sites, two are enough: staging and live.

A staging site is not the same as a backup. A backup is a snapshot you restore when something has already gone wrong. Staging is where you find out before anything goes wrong.

When you need a staging site

Not every change needs staging. Testing every small plugin update on a copy would turn maintenance into a full-time job. This is how we decide:

ChangeStaging recommended?Why
Minor plugin or core updates (security and bug fixes)Usually notLow risk. A backup right before and a check afterwards are enough
Major updates of page builders, WooCommerce or membership pluginsYesThese often change behaviour, templates or the database
A new plugin with many featuresYesConflicts with existing plugins are common
Theme change or redesignYesYou need to see every page type before visitors do
PHP version upgradeYesOld plugins and custom code can stop working completely
Changes to checkout, payments or bookingAlwaysEvery error costs real money
Custom code or functions.php changesYesOne typo can take the whole site down
Text and image changesNoUse drafts and previews instead

Three ways to create a WordPress staging site

MethodEffortBest forWatch out for
One-click staging from your hostMinutesMost sites on managed WordPress hostingCheck how “push to live” handles the database
Staging plugin15 to 30 minutesHosts without built-in stagingLarge sites can hit server limits, copies may live in a subfolder
Manual copy on a subdomain1 to 2 hoursDevelopers who want full controlSearch-and-replace of URLs in the database must be done correctly

Option 1: Staging from your host

Many managed WordPress hosts, including Hostinger, SiteGround, Kinsta and WP Engine, offer staging in their control panel. You click “create staging”, the host copies files and database to a separate address and protects it from search engines. Later you push the changes back with another click.

This is the fastest and safest option if your host offers it. Before you use the push function for the first time, find out exactly what it copies: only files, or files and the database? Some hosts let you choose which tables to push, which matters a lot for shops (more on that below).

Option 2: A staging plugin

Plugins such as WP Staging create a copy of your site inside your existing hosting, usually in a subfolder. The free versions are fine for testing. Pushing changes back to the live site is often a paid feature. On large sites, check your disk space and server limits before you start, and delete the copy when you no longer need it, because a forgotten staging copy is one more WordPress installation that needs updates.

Option 3: A manual copy on a subdomain

  1. Create a subdomain such as staging.yourdomain.com and a new empty database.
  2. Copy all WordPress files to the subdomain folder.
  3. Export the live database and import it into the new one.
  4. Update wp-config.php on the copy with the new database name, user and password.
  5. Replace every occurrence of the live URL with the staging URL in the database. Use a tool that handles serialised data (such as WP-CLI search-replace), not a plain text replace.
  6. Protect the subdomain with a password and set it to “discourage search engines”.
  7. Log in and check that links, images and the admin area point to the staging address.

Staging, local development and backups: what is the difference?

ToolWhere it runsWhat it is for
Local developmentOn your own computer (for example with LocalWP or DevKinsta)Building new features and themes without any server
Staging siteOn a server, under a private addressTesting changes with real content and server settings before going live
BackupStored copy, not runningRestoring the site after something has gone wrong
Live siteOn your server, under your domainWhat your visitors and customers use

Many developers use all three: they build locally, test on staging and keep backups of the live site. For site owners who do not write code, staging and backups are what matters.

Staging for agencies with many sites

For an agency, keeping a staging copy of every client site up to date is a lot of work: every copy needs disk space, needs to be refreshed before each test and is one more installation to keep secure. In practice, agencies with dozens of sites use staging selectively: for major updates of a plugin used across many sites, they test once on a representative site, then roll the update out to all sites with a backup and a visual check on each. That is the approach behind our fleet-wide update service and our offer for agencies.

Settings every staging site needs

A staging site is a full copy of your live site, including everything that talks to the outside world. Without these settings, your test copy can send emails to customers, process real payments or show up in Google next to your real site.

  • Hide it from search engines. Enable “Discourage search engines” under Settings → Reading and, better still, protect the whole site with a password. A staging copy indexed by Google creates duplicate content.
  • Block outgoing emails. Order confirmations, newsletters and form notifications must not reach real customers. Use an SMTP plugin in test mode or a mail-logging plugin that stops sending.
  • Put payments into test mode. Switch Stripe, PayPal and other gateways to sandbox keys.
  • Disable scheduled jobs that act on real data. Subscription renewals, CRM syncs, stock imports and automated newsletters can run twice, once from each site.
  • Turn off caching and CDN rules that point to live. Otherwise you test old cached pages and wonder why nothing changes.
  • Mark it visibly. A coloured admin bar or a “STAGING” notice prevents you from editing the wrong site by accident.

How to test updates on staging

This is the workflow we use for updates that are too risky to install directly on a live site:

  1. Refresh the staging copy from the live site, so you test against current content and plugin versions.
  2. Take note of the current versions and look at the changelogs of the major updates.
  3. Install the updates on staging in the right order: plugins, theme, WordPress core, translations.
  4. Clear all caches on staging.
  5. Check every important page type on desktop and mobile: home, a landing page, a blog post, contact page, shop, cart and checkout.
  6. Test the forms and run a test order or booking.
  7. Check the PHP error log for new warnings.
  8. If everything works, take a backup of the live site and apply the same updates there in the same order.
  9. Check the live site again, the same way.

Our guide on how to update WordPress safely explains the update order and the checks in detail.

Pushing staging to live without losing data

This is where most staging accidents happen. While you were testing on staging, your live site kept working: new orders came in, customers registered, forms were submitted, comments were posted. All of that is in the live database, not in the staging one.

If you push the staging database to live, all of that is gone. For a brochure site that changes once a month, that may not matter. For a shop, it is a disaster.

Type of siteSafe way to go live
Brochure site, little activityPush files and database, but check that no form entries or comments were added on live in the meantime
Blog with commentsPush files only, repeat content changes on live, or push only the posts and options tables
WooCommerce shopNever push the full database. Push files, then repeat settings changes on live by hand
Membership or booking siteSame as shops: files only, settings repeated on live
Plugin and core updatesDo not push at all. Repeat the same updates on live after a backup

The simplest rule: use staging to find out what works, then repeat the change on live. Pushing a whole site back is a convenience that only works for sites whose data does not change.

Common staging mistakes

  • The staging site is indexed by Google because nobody protected it.
  • Customers receive test order emails from the staging copy.
  • A real payment is processed on staging because the live payment keys were copied.
  • The staging database is pushed to a shop and a day of orders disappears.
  • The staging copy is never updated again and becomes a forgotten, vulnerable WordPress install on the same server.
  • Tests are run against an old copy, so the live site behaves differently.

Do you always need staging?

Staging is the right tool for risky changes. For the routine work, most sites need something else: a reliable backup taken right before every update and a check of the important pages afterwards, with a quick way back if something changed. That covers the vast majority of updates, and it costs a fraction of the time.

That is exactly how WP Beekeeper works: it takes a full backup before every update, installs updates in the right order, compares screenshots of your pages before and after and flags anything that looks different. For the big changes, like a PHP upgrade, we test on a staging copy first. Read more in our guide to updating PHP and our PHP upgrade service, which is always tested on staging, or about fleet-wide updates for agencies with many sites.

Routine updates without staging stress.A full backup before every update, a visual check of every page afterwards and one-click restore if anything changed. From 29 euros per site and month.

See how it works →

Staging checklist

  • Staging copy refreshed from live before testing
  • Hidden from search engines and password protected
  • Outgoing emails blocked
  • Payment gateways in test mode
  • Scheduled jobs that touch real data disabled
  • Caching off or cleared
  • Updates tested in the right order
  • Key pages, forms and checkout checked
  • No staging database pushed to a site with live orders or entries
  • Old staging copies deleted when no longer needed

Sources and further reading

Frequently asked questions

What is a WordPress staging site?

A staging site is a private, complete copy of your live WordPress website on a separate address. You use it to test updates, plugins, design changes and PHP upgrades before you apply them to the live site, without visitors or search engines seeing it.

How do I create a staging site in WordPress?

The easiest way is the one-click staging function many managed WordPress hosts offer in their control panel. Alternatives are a staging plugin such as WP Staging, or a manual copy of the files and database on a password-protected subdomain.

Is staging included in WordPress hosting?

Many managed WordPress hosts include staging, often in their mid-range and higher plans. Cheaper shared hosting plans often do not. Check your host’s control panel or plan comparison for a “staging” feature.

How do I push a staging site to live?

For simple sites, your host or staging plugin can copy files and database back to live. For shops, membership and booking sites, never overwrite the live database: push only files, or repeat the tested changes on the live site after a backup.

Will a staging site affect my SEO?

Only if search engines can find it. Always protect the staging site with a password and enable “Discourage search engines”. An indexed staging copy creates duplicate content and can show up in Google next to your real site.

Do I need staging for every WordPress update?

No. Minor plugin and core updates are usually safe with a backup right before the update and a check of key pages afterwards. Staging is worth it for major updates of critical plugins, theme changes, new plugins, PHP upgrades and anything that touches checkout.

Can I test a PHP upgrade on a staging site?

Yes, and you should. Switch the staging copy to the new PHP version first, check every important page and the error log, fix incompatible plugins or code, and only then switch the live site.

Conclusion

A staging site is the safest place to make mistakes. Use it for the changes that can really break your site: major updates, new plugins, redesigns and PHP upgrades. Protect it from Google and from your customers, and be careful when going live, especially if your site takes orders or bookings. For everything else, a reliable backup before each update and a visual check afterwards keep your site safe without the extra work.

Let your WordPress maintenance run itself.Backup first, updates in the right order, a visual check of every page and a clear monthly report. Try WP Beekeeper free for 14 days, no credit card needed.

Start your free trial →