What is a Staging Site?
A staging site is a separate copy of your WordPress site where you can test changes without touching your live site. This article explains the idea and what Hera Backup's staging includes on Free and on Pro.
The problem staging solves
Changing your live site directly is risky: a plugin update can break your layout, a theme switch can cause errors, a bulk edit can delete content. A staging site gives you a place to test updates, try design changes, debug issues and build new pages before they go live.
How it works
When you create a staging site, Hera Backup copies your site's files into a new folder inside your WordPress folder (by default staging-{slug}), and copies your database tables into new tables with their own table prefix. The copied tables sit in the same database as your live site, under that prefix. The copy gets its own address and its own WordPress admin.
The staging site and the live site then change independently. Nothing you do on the staging site reaches the live site unless you push it there, and pushing is a Pro feature.
What is included on Free and on Pro
| Capability | Free | Pro |
|---|---|---|
Staging site in a subfolder (yoursite.com/staging-{slug}/) |
Yes | Yes |
| Staging sandbox (email, scheduled tasks, outbound requests and search indexing blocked) | Yes | Yes |
| Staging site on a subdomain | - | Yes |
| Push staging changes to the live site | - | Yes |
A staging site in a separate database is not available: every staging site is created in your site's own database, under its own table prefix.
The staging badge
While you are signed in on a staging site, the WordPress admin bar shows an orange STAGING badge, in the admin and on the front of the site, so you can tell it apart from your live site.
The sandbox
Every staging site runs in a sandbox, on Free and on Pro, so the copy cannot act as if it were your live site:
- Email: mail sent through WordPress (
wp_mail) is not delivered, so customers and users receive nothing from the staging site. - Scheduled tasks: WP-Cron events and Action Scheduler jobs copied from the live site (scheduled posts, order processing, subscription renewals) do not run, and WooCommerce webhooks are not delivered.
- Outbound requests: requests made through WordPress's HTTP API go nowhere except to the staging site itself, because the copy holds your live site's API keys.
- Search engines: pages carry
noindex, nofollow, robots.txt disallows everything, and WordPress reports the site as not public.
Working on Your Staging Site describes each of these in more detail.
When to use staging
Use staging for changes with real risk: WordPress core updates, major plugin or theme updates, theme switches, WooCommerce configuration changes, or new features. For a small content edit it is usually more than you need.
A staging site holds a copy of your site's files (Hera Backup's own backup folder is not copied) and a copy of the tables you choose, so it needs disk and database space of the same order as your live site. You can create more than one, and each stays until you delete it.