How to create a WordPress staging site and push it to live

For hosting customers · Updated 2026-10-29

On this page
  1. Before you start
  2. Create the staging copy
  3. Push the staging copy to live
  4. Undo a push
  5. Good to know
  6. Common questions

A staging site is a private copy of your WordPress site on a subdomain such as staging.example.com. You test updates, a new theme or plugins there, then push the result to the live site. The live site is not touched until you push.

Before you start

  • The copy uses one subdomain and one database from your plan.
  • The site must be listed on the WordPress page and ready (not installing).

Create the staging copy

  1. Log in to the control panel (https://<server>:2083).
  2. Open WordPress (section Files).
  3. On the live site's card, enter the subdomain name next to Create staging copy. The default is staging.
  4. Click Create staging copy and confirm.

You see Creating the staging copy (a minute or two). A new card appears for the copy, marked Staging copy of example.com. Its files are in ~/sites/staging.example.com.

What the copy gets:

  • all files and a copy of the database (its own database and user);
  • addresses rewritten to the staging address;
  • hidden from search engines;
  • automatic updates turned off.

Push the staging copy to live

  1. On the staging card, decide whether the database goes too. Tick also the database (posts, pages, settings, orders — changes made on the live site since the copy are lost) only if you changed content or settings on staging.
  2. Click Push to live and confirm.

Without the database, only files are pushed (themes, plugins, uploads, code). The live site's wp-config.php and .htaccess stay as they are, and its search engine setting is kept.

Undo a push

The live site is saved before every push. On the live site's card, click Undo the push and confirm to put it back exactly as it was before the last push.

Good to know

  • Push files only for a shop or a site with comments or orders: pushing the database replaces everything visitors added on the live site since the copy was made.
  • The saved live site is kept until the next push or an undo.
  • The staging subdomain gets its own certificate automatically once it resolves to the server.
  • Delete the staging site when you are done with Delete site on its card (leave also delete its database ticked).

Common questions

Why do I get an error about the limit of subdomains or databases?

Your plan has no subdomain or database left for the copy. Delete an unused one, or ask for a larger plan.

Can I create several staging copies?

Yes, with different subdomain names, as long as your plan has subdomains and databases left.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.