A WordPress staging environment is a copy of your website where you safely test updates, plugins, and code changes before they go live. You create it via a subdomain, a copied database, and customized WordPress settings. Below you’ll read how to set this up in Plesk, how to clone your site to staging, and what to pay attention to when restoring to your live environment.
Why use a staging environment
Before installing a WordPress update, new theme, or plugin on your live website, it’s best to test it first in an isolated environment. A staging environment prevents visitors from seeing a broken website or error messages. Typical uses include:
- Testing WordPress core and plugin updates for compatibility
- Trying out new themes and designs
- Making code and CSS changes without risk
- Practicing recovery procedures before applying them to the live site
Creating a staging environment in Plesk
In Plesk, you set up a staging environment with a subdomain, a separate folder, and a copied database. You’ll find these options via your hosting account; with Tandata’s webhosting, Plesk is available by default.
Log in to Plesk
Open your Plesk panel and go to Websites & Domains, where your WordPress site is registered.
Create a subdomain
Click on Subdomains and create, for example, staging.yoursite.com, with its own document root so that live and staging remain separate.
Copy the database
Use phpMyAdmin to make a copy of your live database and give it a clear name, such as database_staging.
Copy the files
Transfer all WordPress files via SFTP or the File Manager to the staging folder and check the file permissions.
Request an SSL certificate
Enable free SSL for the subdomain via Plesk, so that your staging environment is also accessible via https.
Cloning WordPress to staging
Once the structure is in place, adjust the WordPress configuration so the staging site actually works on the new subdomain:
- wp-config.php: change DB_NAME, DB_USER, and DB_PASSWORD to the credentials of your staging database.
- Site URLs: update the site and home URL in the staging database from your live domain to the staging subdomain via an SQL query.
- Blocking search engines: enable the option under Settings > Reading to discourage search engines from indexing, so staging doesn’t appear in Google.
- Securing access: protect the subdomain with a password via .htaccess, so that only you or your client can access it.
Because Tandata servers run on LiteSpeed with NVMe storage, your staging environment also remains fast, even though it runs alongside your live site on the same account.
Restoring changes to live
After testing, only push the approved changes to your live site. Always work with a fresh backup of the live environment so you can roll back if something goes wrong. For synchronization, you can choose from:
- Manually copying specific files and database changes
- A migration plugin that automates the entire process
- A partial sync, where you only transfer theme or plugin files
Note that email settings and domain configuration are separate from your WordPress staging; you manage those separately via business email and domain names. If you get stuck during setup, consult the knowledge base for more background information.
Frequently Asked Questions
Does a staging environment cost extra on my hosting plan?
No, you can create additional subdomains and databases within your existing hosting plan at no extra cost.
Can I show my staging site to a client?
Yes, secure the staging site with a password via .htaccess, so only the client with the correct login details has access.
Which plugins help manage staging?
Plugins such as WP Staging, Duplicator, and All-in-One WP Migration automate the cloning and synchronization of your site.
How do I prevent Google from indexing my staging site?
Under Settings > Reading in WordPress, enable the option to discourage search engines, and consider additional password protection.
Can I switch to Tandata with an existing staging setup?
Yes, when transferring your site, you can bring along both the live and staging environments; see more information about switching to Tandata.
Conclusion
With a staging environment, you safely test WordPress updates, themes, and plugins before they go live, without risk to your visitors. Via Plesk, you can quickly set up a subdomain with its own database, and thanks to LiteSpeed and NVMe storage, that environment remains just as fast as your live site. This way, you manage your website professionally and avoid unpleasant surprises.