The Problem
You want to update a plugin, install a new theme, or push code to your site, but you can’t risk taking the live version down. The fix is a staging site — a private copy of your live WordPress install where you can test changes first. Most managed hosts include one-click staging. If yours does not, the WP Staging plugin builds one inside your existing hosting account. This tutorial walks through both methods, the testing workflow, and how to push validated changes back to the live site.
What You’ll Need
- WordPress version: 6.0 or higher on the live site
- Permissions needed: Administrator role on WordPress plus access to your hosting control panel
- Time to complete: 5-10 minutes with host-based staging, 20-30 minutes with the plugin method
- Difficulty level: Intermediate
- Prerequisites: A recent full-site backup, hosting plan that supports subdirectories or subdomains, and at least 2 GB free disk space
Step 1: Check Your Host for Built-in Staging
Log in to your hosting control panel. Look for a Staging tab or button. Kinsta, WP Engine, SiteGround, Cloudways, Bluehost, and Pressable all include this feature in current plans. If you see the option, click it and skip to Step 2. If your panel has no staging button, your host does not support it natively — jump to Step 4 for the plugin path. Confirm your hosting tier includes staging; some hosts gate it behind higher plans only.
[SCREENSHOT: host-staging-button]
Step 2: Create a Staging Copy in Your Host Dashboard
Click the Create Staging button in your host’s panel. The host clones the live site’s files and database to a separate environment within 1-3 minutes. Most hosts give you a temporary URL like staging.yoursite.com or yoursite.staging.host.com. Note the URL and the temporary admin login if the host generated new credentials. Open the staging URL in your browser. Confirm the front end matches the live site, then log in to the staging WordPress dashboard.
[SCREENSHOT: kinsta-staging-created]
Step 3: Use WP Staging Plugin for Manual Hosts
Install WP Staging from Plugins → Add New on your live site. Activate it and go to WP Staging → Sites. Click Create New Staging Site. Pick the database tables and theme/plugin files to copy. Leave the defaults selected for a full clone. Click Start Cloning. The plugin creates the staging site at yoursite.com/staging-XYZ/:
What this does: sets a base URL and a database table prefix that the staging site uses, so it never overwrites the live database.
define( 'WPSTG_STAGING_URL', 'https://yoursite.com/staging-test/' );
$table_prefix = 'wpstg1_';Log in to the new staging URL with your live admin credentials. The staging copy works independently from the live site.
[SCREENSHOT: wp-staging-create-clone]
Step 4: Test Plugin Updates and Theme Changes
On the staging site, run every change you plan to apply to live. Update plugins one at a time. Switch themes. Add custom code. Browse every page type — home, post, category, search, and any custom post types. Confirm forms, checkout, and login still work. Take screenshots of any error messages. Most issues that surface here would have caused outages on the live site. Document the fixes before moving to the push step.
[SCREENSHOT: staging-test-checklist]
Step 5: Push Changes Back to Live
Run a full backup of the live site first. Our backup workflow guide covers the safe sequence for backups before deploys. With host-based staging, click Push to Live in the host panel. Pick whether to push files, database, or both. Most updates need files only. With WP Staging, install the WP Staging Pro add-on to enable the push feature. Or copy the validated files manually via SFTP and re-test on live. Always re-check the live site after pushing.
[SCREENSHOT: push-staging-to-live]
Step 6: Tear Down or Keep the Staging Site
If you only needed staging for one change, delete the staging environment to free disk space. Click Delete Staging in your host panel or remove the WP Staging clone from the plugin dashboard. If you plan to test changes regularly, keep the staging site running and refresh it from live every two weeks. Stale staging copies drift from production and produce false-positive test results. Schedule a recurring sync so staging always reflects the live database within the last 14 days.
[SCREENSHOT: delete-staging-site]
Troubleshooting
Error: Staging site shows the live URL in links and images.
Fix: The clone process did not run search-and-replace on the database. Use the WP Staging plugin’s Search and Replace tool, or run wp search-replace 'yoursite.com' 'staging.yoursite.com' via WP-CLI.
Error: Search engines indexed the staging site by accident.
Fix: Add a noindex robots header in the staging WordPress dashboard under Settings → Reading → Search Engine Visibility. Many host staging environments enable this by default.
Error: Push to live overwrote pages added on the live site after the clone.
Fix: Restore the live database from the pre-push backup. Always pause new content creation on live during a staging-to-live deploy.
Error: WP Staging fails to clone with “memory limit exceeded”.
Fix: Raise the PHP memory limit in wp-config.php to 512M, or run the clone in chunks via the plugin’s advanced settings.
Quick Recap
- Managed hosts (Kinsta, WP Engine, SiteGround) include one-click staging in most plans
- WP Staging plugin builds a staging clone inside any standard hosting account
- Test every change on staging before applying it to the live site
- Always back up live before pushing staging changes back
- For host-by-host comparisons, our managed host review notes which plans include staging. Reference: the WP Staging plugin page on WordPress.org
