Get A Quote
Get A Quote
Get A Quote

How to Stage a WordPress Site Before Going Live

Recent Posts

Imagine testing a plugin update, clicking save, and watching your live site break — with real customers seeing the error in real time.

This is exactly the scenario a WordPress staging site prevents. A staging environment is a private copy of your WordPress site where you can safely test changes — plugin updates, theme changes, major redesigns, custom code — before they affect your actual visitors.

It's one of the most important WordPress best practices, and one of the most consistently ignored by small business site owners. This guide explains what staging is, why it matters, and how to set one up — with free and paid methods for every situation.

What Is a WordPress Staging Site?

A staging site (also called a test site, development site, or pre-production environment) is a copy of your WordPress site that:

  • Runs on a private URL (e.g., staging.yourdomain.com or yourdomain.com/staging/)
  • Contains an identical copy of your live site's files and database
  • Is protected from public access (password-protected or IP-restricted)
  • Can be modified freely without affecting the live site

The workflow is:

Development
Testing
Deployment

This workflow eliminates the risk of breaking your live site with untested changes.

Why Staging Matters (Real Scenarios)

Scenario 1: Plugin Update Breaks Checkout
Without Staging

You update WooCommerce on your live site. The new version conflicts with your payment gateway plugin. Checkout breaks. Customers can't purchase. 3 hours diagnosing — while losing sales.

With Staging

The update is applied on staging first. The conflict is detected immediately. You delay the live update until the plugin developer releases a fix — no customer impact.

Scenario 2: Theme Redesign Breaks Mobile Display
Without Staging

Your redesign looks great on desktop but the mobile navigation is broken. Google indexes the broken mobile version (mobile-first indexing) before you notice.

With Staging

The mobile issue is caught during testing on staging. Fixed before it ever goes live. Google never sees the broken version.

Scenario 3: Custom Code Error Causes White Screen
Without Staging

A developer adds custom code to functions.php on the live site. A typo causes a PHP fatal error. White screen. Live site down.

With Staging

The same error occurs on staging. Fixed there. Live site never affected. Zero downtime.

1
Hosting Provider's Staging Feature
Easiest — No Technical Knowledge Required
Recommended

Most managed WordPress hosts include one-click staging environment creation. This is the easiest method — no technical knowledge required.

SiteGround
Site Tools → WordPress → Staging → Create Staging Website → set URL → Push to Live when ready
WP Engine
User Portal → Installs → Add Environment → Staging → Push to Production with selective options
Kinsta
MyKinsta → Sites → Environments → Add Staging → Push to Live when verified
Cloudways
Applications → Staging Management → Clone → requires manual database/file sync
Tip: If your hosting provider offers one-click staging, use it. It's the simplest, most reliable method and includes push-to-live functionality built in.
Easiest method. If your host includes staging, there's no reason to use anything else.
2
WP Staging Plugin
Free, Works on Any Host
Free

If your host doesn't include staging, the WP Staging plugin creates a staging copy within your existing hosting environment.

Setup

Install WP Staging (free) from wordpress.org
Go to WP Staging → Create Staging Site
Click Start Cloning
WP Staging creates a copy at yourdomain.com/wpstg0/ (or similar path)
Log in to the staging site (uses a different login if configured)

Using the Staging Site

Work on the staging site exactly as you would the live site — apply plugin updates, test theme changes, install new plugins, test custom code.

Pushing Changes to Live

Important: The free version of WP Staging does not include push to live. You can make changes on staging, but deploying to live requires manually exporting and re-importing the database and copying changed files via FTP.

WP Staging Pro ($139/year) adds one-click push to live functionality. For frequent staging needs, this is worth the investment.

Good free option for basic hosting. Pro version recommended if you need push-to-live functionality.
3
Local Development with Local
Beginner-Friendly Desktop Environment
Free

Local by Flywheel is a free desktop application that runs a complete WordPress development environment on your computer.

Setup

Download Local from localwp.com — available for Mac, Windows, and Linux
Install and open Local
Click Create a new site — enter name, configure PHP version and environment
Local creates a local WordPress installation accessible at http://yoursite.local

Pull from Live Site

Instead of starting from scratch, pull your live site to Local:

Use the Connect feature or Flywheel/WP Engine integration
Or: Export your live site with Duplicator and import to Local
Your local site is now an identical copy of your live site

The Professional Development Workflow

Local
Active development on your computer
Staging Server
Final testing, accessible to team/clients
Live
Production — real visitors
Best for developers who want a fast local environment. Combine with hosting staging for the full professional workflow.
4
Subdomain Staging (Manual Setup)
For Basic Hosting Without Built-in Staging

For those on basic hosting without built-in staging, create a staging environment manually using a subdomain.

Create the Subdomain

Log in to cPanel
Go to Domains → Subdomains
Create staging.yourdomain.com pointing to /public_html/staging/

Copy Your Live Site to Staging

Option A: Use Duplicator to create a package of your live site and install it at the staging subdomain (adjust the install URL to staging.yourdomain.com).

Option B: Manual FTP copy + phpMyAdmin database export/import + wp-config.php update.

Password-Protect the Staging Site

Always password-protect your staging environment to prevent accidental Google indexing (duplicate content), public access to unfinished work, and security exposure from potentially outdated staging files.

Via cPanel:

Go to Security → Password Protect Directories
Navigate to your staging directory
Enable password protection and set credentials

Via .htaccess:

Apache
AuthType Basic
AuthName "Staging Site"
AuthUserFile /path/to/.htpasswd
Require valid-user

Or add to WordPress wp-config.php:

PHP
define( 'DISALLOW_INDEXING', true );
Most manual method. Works on any hosting but requires technical comfort. Always password-protect.

Best Practices for Staging Sites

  • Always work staging → live, never live → staging. Once your live site has new orders, comments, or content that staging doesn't have, you can't safely sync staging data back to live (you'd overwrite the new content). Changes always flow one direction.
  • Keep staging reasonably current. If staging is 6 months old, testing a plugin update on staging doesn't accurately reflect what will happen on live. Refresh staging monthly on active sites.
  • Use staging for all significant changes. "Significant" means: any plugin update affecting checkout, forms, or core functionality; any theme changes beyond minor text edits; any custom code additions; any major WordPress core version upgrade.
  • Test the complete user journey on staging. Don't just check that the site loads — test the full visitor flow: browse a product, add to cart, complete checkout, receive confirmation email. Test on mobile. Test in multiple browsers.
  • Never run staging on the same performance infrastructure as live. Staging on shared hosting with your live site creates performance interference. Ideally, staging is on a separate server or hosting account.

Frequently Asked Questions

Q: Will Google index my staging site?
A: Only if it's publicly accessible. Always password-protect staging or add noindex directives. In WordPress: Settings → Reading → check "Discourage search engines from indexing this site." On your staging .htaccess, add the password protection shown above.
Q: How often should I update the staging site to match live?
A: For active sites, refresh staging monthly. For sites with infrequent changes, refreshing before each major testing session is sufficient.
Q: Can I use staging to show clients work before going live?
A: Yes — this is one of the best uses of a staging site for agencies. Build the site on staging, share the password-protected URL with the client for review and approval, then push to live when sign-off is given.
Q: Is a staging site necessary for simple content updates (adding blog posts, changing images)?
A: No. Staging is for changes that could break functionality — plugin updates, theme changes, custom code. Simple content creation (new posts, editing text, adding images) is low-risk and fine to do directly on the live site.

Final Thoughts

A staging environment is the difference between confident website management and anxious guesswork. It costs nothing on managed hosts that include it, and a small investment on other setups — and it prevents the kind of live-site disasters that erode customer trust and cost real money to fix.

If you're updating plugins directly on your live site today, this is the highest-leverage improvement you can make to your WordPress workflow.

Contact us to discuss professional WordPress development workflows
Views: 89