How to use a WordPress staging site to test changes safely

What a staging site is for

A staging site is a copy of your live site on a separate address, hidden from the public. You make changes there first, check that everything works, and only then apply the same changes to the live site. If something breaks, it breaks where nobody is looking.

It is most useful for:

• Major plugin or theme updates, especially ones the developer flags as significant.
• Switching themes or rebuilding pages with a builder such as Elementor.
• Trying a new plugin you are not sure about.
• Changing the PHP version or other server settings.
• Larger design changes that take several days to finish.

For small content edits, such as correcting a phone number or publishing a blog post, staging is unnecessary. Work on the live site with a recent backup in place.

Think of staging as insurance for changes that are hard to reverse or that touch many pages at once. The more your site earns for you, and the more moving parts it has, the more that insurance is worth.

Ways to create a staging copy

Host-provided staging

Some hosts offer a staging tool in the control panel that copies your site with one click and can push changes back. If yours does, read its documentation carefully, especially what "push to live" overwrites.

A staging plugin

Several plugins can clone your site into a subfolder or separate area on the same hosting. They are convenient, but the copy shares your server, and pushing changes back to live is often a paid feature. Check what the free version actually does before relying on it.

A subdomain you set up yourself

Create a subdomain such as staging.yourbusiness.co.uk with its own database, then copy the site across with a migration or backup plugin. This gives you full control and works on most hosting, but takes more effort.

A local copy on your computer

Free tools such as Local or similar desktop apps run WordPress on your own computer. This is ideal for developers testing code or themes, and nobody else can see it. It is less useful for showing changes to a client or colleague.

Which to choose

If your host offers staging, start there, as it is designed for your server. If not, a subdomain copy is the most realistic test because it runs on the same hosting setup as your live site. Keep local copies for development work. Whatever you use, make sure the staging copy runs the same PHP version and similar settings as live, or your test results may not match what happens on the real site.

Keep staging private and out of search results

A staging site that search engines find creates duplicate content and can show customers half-finished pages. Protect it in several ways at once:

1. Password protection at server level, so nobody can view it without a login. This is the strongest protection.
2. Discourage search engines in Settings, Reading on the staging copy.
3. Do not link to it from the live site or anywhere public.
4. Check the search engine setting before going live. If you copy staging over the live site, make sure the "discourage" setting is not carried across. This is a common way sites accidentally disappear from Google.

Stop staging from acting like the live site

A copy of your site includes all its automated behaviour. Without care, staging can contact real customers or process real data.

• Email. Disable outgoing mail or route it to a test inbox, so forms and notifications do not reach customers. Some SMTP plugins can block sending for this purpose.
• Payments and integrations. Put payment gateways into test mode and disconnect integrations that sync data, such as CRMs or mailing lists.
• Scheduled tasks. Scheduled posts, reminders and imports may run on both copies. Pause them on staging.
• Personal data. Staging holds copies of form entries and user accounts. Protect it as well as the live site and delete it when you are finished. The UK GDPR and WordPress guide covers your general obligations.

A safe routine for testing and going live

1. Take a fresh backup of the live site. Whatever happens next, you can return to this point. See WordPress backups explained.
2. Refresh staging from live so you test against current content and settings.
3. Make your changes on staging and keep a written list of each change, in order.
4. Test properly. Check the home page, key service pages, forms, menus, mobile layout and any shop or booking pages. Look at the site logged out as well as logged in.
5. Choose how to apply changes live. For updates and plugin changes, repeat the same steps on live from your list. For a full redesign, push the staging copy over live during a quiet period.
6. Test live again straight away, including a test form submission.

The content trap when pushing staging live

The biggest risk with staging is overwriting new content. If the live site received orders, form entries, comments or blog posts while you worked on staging, pushing the whole staging database over live deletes them.

To avoid this:

• Freeze content edits on live while a redesign is in progress, or keep the work short.
• For shops and busy forms, repeat changes on live by hand rather than pushing the database.
• If your tool supports pushing files only, or selected tables, use that where possible.

Is staging always worth it?

For a simple brochure site with a few well maintained plugins, a reliable backup and a quick check after each update is often enough. Staging earns its keep on sites that take orders or bookings, run many plugins, or are being redesigned.

If you prefer to avoid routine updates altogether, WP Web Hosting's WP Managed plan handles WordPress, theme and plugin updates for you, with regular backups included in every plan.

Frequently asked