Skip to content

Creating, Deploying and Protecting Staging Copies

This page summarizes SiteGround’s own instructions. For the full, current version, see SiteGround’s guide: How to create a Staging copy of your site and the rest of their Staging Tool tutorial.

  1. Log in to SiteGround and open Site Tools for cadence-group.com.
  2. Go to WordPress → Staging.
  3. Choose the WordPress installation (cadence-group.com) from the drop-down.
  4. Type a Staging Name and click Create.
  5. If SiteGround finds files or folders that aren’t part of a normal WordPress install, it asks whether to copy them too. Tick the ones the site needs and click Confirm.
  6. The new copy appears under Manage Staging Copies.

SiteGround copies the site’s files and database for you. A few things to know from SiteGround’s guide:

  • Staging copies use subdomains like stagingX.cadence-group.com. Because our nameservers aren’t at SiteGround, SiteGround’s guide says the address (and the www. version) must be added as an A record at the current DNS provider, GoDaddy. That’s the step Jim does.
  • WordPress’s automatic scheduled tasks (cron) are turned off on staging copies, so staging won’t send duplicate emails or run automated jobs.
  • Limits: up to 10 staging copies per account and 15 staging actions per day. The database must be under 5 GB, and the account needs enough free space.
  • Open the staging site’s dashboard from Manage Staging Copies (the log-in icon), or go straight to /wp-admin on the staging address.
  • Log in with your normal WordPress username and password. They’re copied from the live site.
  • From the copy’s menu you can also Replicate it (clone it), Rename it, or Destroy (delete) it. Renaming or recreating a copy changes its address, so tell Jim if you do either.

When you’re happy with your changes, SiteGround offers two ways to push them live:

Option What it does When to use it
Full Deploy Replaces the live site’s files and database with the staging copy’s, in one click. Only when staging has everything the live site should have. Anything added to the live site after staging was created (new form entries, comments, posts) could be overwritten.
Custom Deploy Compares staging with the live site and lets you pick which files and database tables to add, update, or delete. Most of the time. You can push your page changes without overwriting things like form entries.

Before deploying, make sure the staging copy’s WordPress version isn’t older than the live site’s. SiteGround won’t push a staging copy with an older WordPress version. SiteGround also has a restore option if a deploy goes wrong.

Staging sites are public by default, and search engines can find and index them. That’s what happened with Cadence’s old dev site, so protecting staging matters.

In SiteGround Site Tools (SiteGround’s instructions):

  1. Go to Security → Protected URLs.
  2. On the Users tab, create a user with a username and password (save them somewhere safe).
  3. On the URLs tab, choose the staging subdomain (for example staging2.cadence-group.com), enter / as the path to protect the whole site, pick the user, and click Protect.

Visitors and search engines then get a username and password prompt before they can see the staging site. You can change the password or remove the protection later from the same screen.