How to Create a Staging Site on a WordPress VPS in 2026

Every experienced WordPress developer and site owner knows the cardinal rule: never test untested changes on a live production website. A poorly tested plugin update or theme modification can take down your WooCommerce store, break custom post type queries, or corrupt critical database tables in seconds.

The solution is a dedicated staging environment - an identical mirror of your production site running on a private subdomain where you can freely experiment, test updates, and validate changes before deploying them to your live audience.

On a VPS with SSH access, creating a staging site is entirely free and takes under 30 minutes using Nginx virtual host configuration, WP-CLI's powerful command-line tools, and rsync file synchronization.

---

Architecture Overview

---

Step 1: Create the Staging Directory Structure

Create a dedicated web root for the staging environment:

---

Step 2: Clone Production Files with rsync

Copy all WordPress files from your production directory to the new staging directory:

Set correct ownership so PHP-FPM can read and write files:

---

Step 3: Clone the Production Database with WP-CLI

Install WP-CLI globally if not already present:

Export the production database:

Create a dedicated MariaDB database and user for staging:

Import the production database export into the staging database:

---

Step 4: Configure wp-config.php for the Staging Environment

Copy and update the WordPress configuration file for the staging site:

Open /var/www/staging.example.com/public_html/wp-config.php and update the database constants:

Also add a constant to disable automatic plugin updates and email sending on staging to prevent accidental notifications to real customers:

---

Step 5: Search-Replace Production URLs with WP-CLI

The cloned database still contains all references to https://example.com. Replace them with the staging subdomain:

Flush the WordPress cache and object cache:

---

Step 6: Create the Nginx Virtual Host for the Staging Subdomain

Create a new Nginx server block at /etc/nginx/sites-available/staging.example.com:

Enable the configuration:

---

Step 7: Generate HTTP Basic Auth Password File

Create a password-protected access credential for the staging subdomain:

Enter and confirm a strong password. The /etc/nginx/.htpasswd file now contains the hashed credentials required to access staging.example.com.

---

Step 8: Issue Let's Encrypt SSL for the Staging Domain

Certbot will automatically configure HTTPS redirection. Your staging site is now accessible at https://staging.example.com with a valid SSL certificate, protected by HTTP Basic Authentication.

---

Step 9: Disable Search Engine Indexing in WordPress

Log into the staging WordPress admin at https://staging.example.com/wp-admin and navigate to:

Settings > Reading > Search engine visibility

Check ✅ Discourage search engines from indexing this site and click Save Changes.

This sets a X-Robots-Tag: noindex header and inserts into all staging pages as a belt-and-suspenders measure alongside HTTP Auth.

---

Keeping Staging In Sync with Production

After making changes to production content or database, re-sync the staging environment:

You now have a fully isolated, production-identical staging environment that is invisible to search engines, protected from unauthorized access, and ready for safe plugin updates, PHP upgrades, and theme development.