How to Create A Staging Environment In xCloud?

Updated November 17, 2026 · 9 min read

Summarize with:
Share:

A staging site in xCloud is a private copy of your WordPress site where you test plugins, themes and other changes, then pull data from the live site or push your changes to it. This guide shows how to create one, how to pull and push, and what each push or pull changes and keeps, so you know what happens to your live site before you click.

See the WordPress staging feature page for what it does, who it is for and which plans include it.

Need a separate, lasting copy of a WordPress site instead, on the same or a different server? Use Clone Site.

Step 1: Open Deploy Staging on your live site

Log in to your xCloud dashboard and open the live (production) site you want to copy. Click ‘Deploy Staging’ at the top of the site page. A window opens asking which domain the staging site should use.

Staging needs a paid plan and isn’t available for WordPress Multisite. If you don’t see ‘Deploy Staging’, check these first.

Click ‘Deploy Staging’ at the top of the production site’s page

Step 2: Choose the domain and deploy

You can put the staging site on an xCloud test domain or on your own domain.

Test Domain

Choose ‘Test Domain’, type a name in ‘Domain Name’ and click ‘Deploy Staging’. This is the quickest option: there is no DNS to set up.

Choose the ‘Test Domain’ card in the Deploy Staging window

Custom Domain

Choose ‘Custom Domain’ and enter the domain you want, for example staging.example.com. Under ‘DNS Setup’, add the A record shown to your DNS provider, click ‘Verify My DNS’, choose whether to enable HTTPS, then click ‘Deploy Staging’.

Choose the ‘Custom Domain’ card, then type the staging domain in ‘Domain Name’

Note: If you have Cloudflare integrated with xCloud, you can check the Cloudflare option to set up DNS and SSL through Cloudflare.

xCloud copies the live site to the new staging site. When it finishes, the staging site appears under the live site in the site menu and in the ‘Staging’ card on the live site’s overview.

Step 3: Pull data from the live site

Open the staging site and click ‘Manage Staging’ in the left menu. The ‘Staging Management’ card has two buttons: ‘Pull Data’ (live site → staging) and ‘Push Data’ (staging → live site).

The Staging Management card with the Pull Data and Push Data buttons

Click ‘Pull Data’. Turn on ‘Files’, ‘Database’ or both:

  • Files: choose ‘Overwrite’ to make staging’s files match the live site exactly, or ‘Incremental’ to copy only new and changed files.
  • Database: choose ‘Full’ for the whole database, or ‘Selected Tables’ to pull only the tables you tick.

Turn on Files and choose Overwrite or Incremental in the Pull Data window

Click ‘Pull Data’ to start. You can follow its status in ‘Deployment Logs’ on the same page.

Step 4: Add hook scripts (optional)

Scroll down to the ‘Hook Scripts’ card to run your own commands after every pull or push.

Script When it runs Where it runs
Post-Pull Hook Script After every pull from the live site On the staging site
Post-Push Hook Script After every push to the live site On the live site

Write your bash script in the box and click ‘Save Post-Pull Script’ or ‘Save Post-Push Script’. Each script runs as the site’s own user inside the site’s folder, so WP-CLI commands such as wp cache flush work without full paths.

The Hook Scripts card with the Post-Pull and Post-Push Hook Script boxes

Step 5: Push your changes to the live site

When your changes are ready, click ‘Push Data’ in ‘Manage Staging’. Turn on ‘Files’, ‘Database’ or both, and pick ‘Overwrite’ or ‘Incremental’ and ‘Full’ or ‘Selected Tables’ the same way as for a pull. Read what a push changes and keeps before you choose.

Turn on Files and choose Overwrite or Incremental in the Push Data window

Keep ‘Take backup of your production site before pushing changes (Recommended)’ ticked. xCloud then backs up the live site first and starts the push only after that backup finishes. If the backup fails, or doesn’t finish within about 20 minutes, the push doesn’t start and your live site is left as it was. Click ‘Push to Production’.

Keep the ‘Take backup of your production site before pushing changes (Recommended)’ box ticked, then click Push to Production

The live site may be briefly unavailable while the push runs. You can follow its status in ‘Deployment Logs’. If something goes wrong, restore the backup taken before the push from the live site’s backups (see Site backups).

Push does not move a domain. Push to Production copies files and database tables into the live site this staging site is linked to, and nothing else. To put a newly built site on a domain that another site already uses, follow When the domain is already used by another site.

NOTE: If you delete a production site then all staging sites attached to it will be removed as they become orphan. To keep the staging site you can clone them and create a new site separately.

What Push and Pull change and keep

A push copies from staging to the live site, and a pull copies from the live site to staging. The site that receives the data is the destination. Here is exactly what happens to it.

Files

Option What happens on the destination
Overwrite Files that differ are replaced, new files are added, and files that exist only on the destination are deleted. For example, images uploaded to the live site since your last pull are deleted by an Overwrite push.
Incremental New and changed files are copied. Nothing is deleted.

In both modes, these files are never copied from the other site:

  • wp-config.php
  • wp-content/object-cache.php (the file that connects your site to Redis)
  • wp-content/.litespeed_conf.dat (LiteSpeed Cache settings file)
  • wp-content/mu-plugins/xcloud-auto-login.php and wp-content/mu-plugins/xcloud-cfe-cache-purge.php (xCloud’s login and cache helper files)
  • the BetterShield plugin folder, when the destination has BetterShield

xCloud also removes the object cache, LiteSpeed settings, login helper and Cloudflare Edge Cache helper files (object-cache.php, .litespeed_conf.dat, xcloud-auto-login.php and xcloud-cloudflare-edge-cache.php) from the destination after a push or pull. Here is what to do next:

  • Redis Object Cache on Nginx: if the site stops using Redis, open ‘WordPress’ → ‘Caching’ and turn Redis Object Cache off and on again. Contact support if that doesn’t help.
  • LiteSpeed Cache on OpenLiteSpeed: its object cache uses the same two files, so check it in the LiteSpeed Cache settings in WordPress.
  • Login helper: you don’t need to do anything. xCloud adds it back the next time you log in to WordPress from xCloud.
  • Cloudflare Edge Cache: open ‘WordPress’ → ‘Caching’ and turn Cloudflare Edge Cache off and on again to put its helper file back.

wp-config.php isn’t copied, but xCloud still edits it on the destination after every push and pull: it sets the site address (WP_HOME, WP_SITEURL) and the cache settings to match the destination. See Redis password below.

Database

Option What happens on the destination
Full Every table copied from the source replaces the destination’s table of the same name. Tables that exist only on the destination are left in place.
Selected Tables Each table you tick is emptied and replaced with the source’s copy. Rows are not merged. The list shows the live site’s tables. A table that exists only on staging isn’t listed, so use Full to push it. Full also replaces every other table on the live site, so read the warning below first. If you tick a table staging doesn’t have, the push fails at the database step.

Because tables are replaced, not merged, leave out tables that keep changing on the live site when you push. On a WooCommerce shop, for example, pushing the orders, customers or users tables replaces every order and account placed on the live site since you pulled with what staging has. Before you tick wp_posts, wp_postmeta or wp_options, check they hold nothing that changed on the live site. On some WooCommerce shops, orders are stored in wp_posts and wp_postmeta. Your tables may start with a different WordPress database table prefix than wp_. Take the backup in Step 5 as well.

After the database is copied, xCloud replaces the source’s address with the destination’s address in the database, and BetterShield keeps each site’s own login protection data.

What a push keeps on the live site

  • Search engine visibility: when a push includes the options table, xCloud keeps the live site’s own Search engine visibility setting, so staging’s “discourage search engines” setting isn’t copied to it. Other indexing settings aren’t protected: SEO plugin settings in the options table and a robots.txt file are copied like any other data.
  • Security keys: a push doesn’t change the live site’s security keys. A push that includes the users tables can still log people out, because their login sessions are replaced with staging’s.
  • The Post-Push Hook Script runs on the live site at the end.

What a pull changes on staging

  • Email and sync plugins are turned off. When a pull includes the database, xCloud turns off FluentSMTP, WP Mail SMTP, Post SMTP and Easy WP SMTP on the staging site and clears their saved settings, so staging can’t send real emails through your live mail account. It also turns off WP Fusion, WP Fusion Lite, WP Fusion Logins and WP Remote Users Sync, and clears their CRM links, so test changes don’t reach your CRM or other sites. These plugins stay as they are on your live site.
  • Search engine visibility: if the staging site is set to discourage search engines, xCloud sets it again after the pull, so the live site’s setting doesn’t make staging visible to search engines. See Search engine visibility.
  • Security keys: xCloud creates new security keys for the staging site, so everyone logged in to staging is logged out.
  • The Post-Pull Hook Script runs on staging at the end.

Redis password in wp-config.php

After every push and pull, xCloud updates the Redis settings in the destination’s wp-config.php:

  • If xCloud’s Redis Object Cache is on for that site and the server uses Redis passwords, xCloud writes the site’s own Redis login on Nginx, and leaves the WP_REDIS_PASSWORD line alone on OpenLiteSpeed.
  • In every other case, xCloud removes any WP_REDIS_PASSWORD line you added by hand.

If you connect to Redis with your own password and the server uses Redis passwords, turn on Redis Object Cache in xCloud for the site. On any other server, add the line again after each push or pull. See How to find the Redis credentials.

Troubleshooting

A custom Nginx config is turned off on the staging site

When xCloud creates a staging site, it tests the live site’s custom Nginx configs on the staging server before copying them. A config that NGINX rejects there is copied turned off, so it can’t stop NGINX from reloading for the other sites on that server. Staging on the same server as the live site is the usual case: a server-wide setting such as a log_format name can only be set once per server, and the live site already sets it.

Open the staging site and go to ‘Tools’ → ‘Nginx Customization’. A notice above the Custom Nginx Config table names each config that was copied as inactive and why. Edit the config so it no longer clashes, then switch its Active toggle on. The Clone Site guide shows the notice. On an OpenLiteSpeed server this test is skipped, and configs are copied as they are on the live site.

Staging creation stopped with an NGINX message

xCloud stops creating the staging site, instead of reporting a site NGINX never loaded, when:

  • NGINX on the staging server is already failing. The message reads “NGINX on the destination server is already failing, so nothing can be checked or copied until it’s fixed.” Fix that server’s NGINX first, see fix NGINX configuration regeneration failures, then deploy staging again.
  • xCloud couldn’t run the check on the server. The message reads “We couldn’t check NGINX on the destination server. Try again in a moment.”
  • NGINX rejected the staging site’s own config. The message reads “NGINX rejected the cloned site’s config, so it was not loaded.” and is followed by the error from NGINX. Read that error, fix or turn off the config it names on the live site, then deploy staging again. If you can’t tell what the error means, contact support.

Frequently asked questions

Does an Overwrite push delete files on my live site?

Yes. Overwrite makes the live site’s files match the staging site, so files that exist only on the live site are deleted. Incremental only adds new files and updates changed ones, and deletes nothing. wp-config.php and the files listed under Files above are never copied in either mode.

Will pushing selected tables merge my new orders into the live site?

No. Each selected table on the live site is emptied and replaced with the staging copy. Leave out tables that change on the live site, such as orders, customers, form entries and content changes, or they go back to what staging had. On some WooCommerce shops, orders are stored in wp_posts and wp_postmeta.

Why did my SMTP plugin stop working on staging after a pull?

When a pull includes the database, xCloud turns off FluentSMTP, WP Mail SMTP, Post SMTP and Easy WP SMTP on the staging site and clears their saved settings, so staging can’t send real emails through your live mail account. Set up a test mail account on staging if you need to test email.

Why was my Redis password removed from wp-config.php after a push or pull?

After every push and pull, xCloud updates the site address and cache settings in wp-config.php. A WP_REDIS_PASSWORD line you added by hand is removed unless Redis Object Cache is on for that site and the server uses Redis passwords. On a server that uses Redis passwords, turn on Redis Object Cache in xCloud for the site. On any other server, add the line again after each push or pull.

Does xCloud control indexing on production sites?

xCloud doesn’t add its own indexing rules to live sites. During a push it only keeps the live site’s Search engine visibility setting. All other indexing settings are controlled by WordPress, themes, plugins or custom configurations, and a push can copy them from staging.

Does xCloud set environment flags such as WP_ENV or WP_STAGING?

No. xCloud doesn’t add these settings, so they can’t hide your live site from search engines.

Does xCloud add noindex via MU-plugins or server-level rules?

No. xCloud adds a login helper and cache helpers to mu-plugins, but none of them, and no server rule from xCloud, sets noindex on a live site.

Why is indexing disabled on staging sites?

Indexing is disabled by default on staging sites to prevent staging URLs from being indexed by search engines. This is intentional and expected behavior, designed to protect SEO and avoid duplicate content issues.

Does pulling or pushing data affect production indexing?

It can. A push keeps the live site’s Search engine visibility setting. It doesn’t protect other indexing settings: SEO plugin settings in the options table and a robots.txt file are copied like any other data. Check them after a push. A pull only changes the staging site.

Can staging noindex settings be applied to production?

Some can. A push keeps the live site’s Search engine visibility setting, but SEO plugin settings in the options table and a robots.txt file are copied like any other data. Check them after a push.

Does xCloud ever treat a production site as staging?

No. xCloud keeps live sites and staging sites apart, and a live site doesn’t get the staging site’s Search engine visibility setting. A push does copy the files and database tables you choose from staging to the live site, so any settings stored in them come along.

If a production site shows noindex, where does it come from?

Noindex on a live site can come from:

  • WordPress database options
  • SEO plugin settings (such as Rank Math or similar)
  • Theme logic or custom code that detects environment conditions

xCloud doesn’t add noindex itself, but a push can copy these settings from staging.

What should I check if production indexing issues occur after staging operations?

If indexing issues appear on production, review the following:

  • SEO-related database options after staging pushes
  • SEO plugin settings, especially environment-based or advanced configurations
  • Any custom deployment scripts, environment checks, or conditional logic in themes or plugins

If you run into any issues with staging, feel free to reach out to our support team.