A staging site is a private, fully functional copy of your live WordPress website. Same theme, same plugins, same content, same database — but isolated from the version visitors see. You experiment freely on staging: swap themes, update plugins, redesign pages, test WooCommerce checkout flows. If something breaks, your public site is untouched. On smartxhosting.uk, the Plesk WordPress Toolkit creates a staging environment in a few clicks. This guide walks through why staging matters, how to create and work on a staging copy, how to protect it from accidental public exposure, and how to sync changes back to production safely.
What a staging site is · Why staging matters · Creating a staging site via WordPress Toolkit · Working on your staging copy · Password-protecting the staging site · Testing on staging · Syncing staging changes to live · Deleting the staging site · Common staging use cases · Frequently asked questions
A staging site is a complete duplicate of your production WordPress site running on a separate URL (typically staging.yourdomain.co.uk). Same code, same database at the moment of cloning. Changes on staging stay on staging until you push them to production.
Think of it as a rehearsal space: try something risky, see how it goes, commit only if you are happy with the result. The live site never sees the changes until you are ready.
Making changes directly on a live site is one of the most common causes of unexpected downtime and broken layouts.
Especially valuable before WordPress major version updates, WooCommerce upgrades, theme switches and any change that touches database structure.
Plesk WordPress Toolkit handles the entire cloning process automatically — copies files and database, creates a new subdomain, updates URLs so the staging copy works independently.
Plesk > WordPress. You see a card for each installation.
Find the card for the live website you want to stage. Confirm the URL.
Click the Clone button on the installation card. Cloning configuration screen opens.
Most common approach: a new subdomain like staging.yourdomain.co.uk. Optionally customise database name and installation path.
Other options: clone to an existing subdomain, or to a different domain on your hosting account.
Click Start. WordPress Toolkit copies every file, duplicates the database, updates internal URLs. Typically 1–3 minutes depending on site size.
Once complete, a new installation card appears in WordPress Toolkit labelled with the staging subdomain. Live site unchanged.
The staging site is a fully independent WordPress installation. Its own URL, database, wp-admin dashboard, files.
Log in via Plesk SSO from the staging installation card — no password needed.
Nothing touches production until you explicitly sync.
By default, staging is publicly accessible. Anyone who knows the URL can visit. Search engines may discover and index it — creating duplicate content issues and accidentally exposing work in progress.
Visitors and search engine crawlers must enter credentials before viewing any staging page.
From the staging site card, an option to add noindex, nofollow meta tags. Extra layer against accidental indexing. Recommended in addition to password protection.
The WordPress Toolkit can generate a staging-specific robots.txt blocking all crawlers. Another belt-and-braces layer.
Before syncing changes to live, test thoroughly.
Open staging in Chrome, Firefox, Safari, Edge. Different rendering engines occasionally expose layout bugs.
Check for new PHP warnings or errors caused by your changes. Tools > Site Health in WordPress; Plesk > Logs for PHP error log.
When staging works correctly, two ways to get the changes to production.
WordPress Toolkit can push selected changes from the staging installation to the live installation.
wp-content/themes/, wp-content/plugins/, wp-content/uploads/).If your staging changes are few and well-documented, applying the same changes manually on production can be safer:
Slower but gives finer control.
Once staging has served its purpose, remove it:
Toolkit deletes files and the database. Frees up space in your plan quota. The subdomain itself may persist — delete it via Plesk > Websites & Domains if no longer needed.
Some teams keep a staging environment permanently available. The advantage: always ready for the next change, no re-cloning required. Disadvantage: it drifts out of sync with production over time. If you keep staging permanent, periodically re-clone from production to keep them aligned.
Clone, upgrade on staging, test thoroughly, then upgrade production once confident.
WooCommerce updates occasionally require customer data migrations. Run on staging first.
Try the new theme on staging, check every page type, adjust until everything works, then switch production.
Switch PHP on staging, test every plugin for compatibility, then switch production (or revert staging if plugins need updating first).
Reorganise categories, rewrite pages, restructure navigation on staging. Let a client review before going live.
Install and try a new plugin on staging to confirm it does what you need before adding to production.
Agencies developing for clients typically work on staging and push to production on milestone reviews.
Does staging count against my plan's domain or WordPress instance quota?
Yes. The staging site is a full WordPress installation on a subdomain; it counts toward your plan's WordPress instance limit and storage allowance. WP Standart (3 instances) allows production + staging + one more site. Plan accordingly.
Is the staging site a backup?
No, not a backup. Staging is a live, changeable copy — not a frozen snapshot. For proper backups, use Plesk Backup Manager or UpdraftPlus.
Can I give a client access to staging without Plesk credentials?
Yes. Create a WordPress user on the staging site for them, set password protection with credentials they can share, or use the Plesk WordPress Toolkit's password protection.
How long does cloning take?
1–3 minutes for most sites. Larger WooCommerce sites with big media libraries can take 10–20 minutes. The Toolkit shows a progress indicator.
Will search engines find and index my staging site?
Possible if unprotected. Enable password protection immediately after cloning. Also tick the "discourage search engines from indexing" option in staging's WordPress Settings > Reading.
Can I run multiple staging sites at once?
Yes, subject to your plan's WordPress instance quota. Useful for testing multiple independent changes in parallel.
What happens to content created on staging?
Stays on staging until you sync. If you create 10 new posts on staging and never sync, they only ever exist on staging.
Can I migrate changes the other way — production to staging?
Yes. Re-clone staging from production via the Toolkit — pulls the current production state over. Useful if staging has drifted out of sync or you want to test something new.
Does staging affect live site performance?
Minimal. Staging uses the same server resources but the process of cloning is brief. Ongoing use of staging adds some load depending on traffic; usually negligible.
What is the difference between Clone and Copy Data?
Clone creates a brand-new installation from scratch. Copy Data copies files and/or database from one existing installation to another. Use Clone to create a new staging site; use Copy Data to push staging → production.
Launch your WordPress site on smartxhosting.uk
UK hosting with the Plesk WordPress Toolkit, LiteSpeed Cache, Redis object caching, free Let’s Encrypt SSL, free CDN and daily backups — from £2/month.
View WordPress hosting plans →