Skip to content

Using the Staging Site

A staging site is a private copy of cadence-group.com where you can try changes (new pages, white papers, blog posts, SEO edits, layout changes) without touching the live website. When a change looks right on staging, it can be pushed to the live site.

The Cadence Group website is hosted on SiteGround. Staging copies are created and managed in SiteGround Site Tools → WordPress → Staging, not from inside WordPress. There’s no staging plugin to install.

Staging address staging2.cadence-group.com
Staging login staging2.cadence-group.com/wp-admin
Username and password The same WordPress login you use on the live site. It was copied over when the staging site was created.
Created November 19, 2026, by Jim (Visionquest Development)

SiteGround Site Tools Staging Copies page showing staging2, with SiteGround’s assistant explaining the missing DNS record

In SiteGround Site Tools, under WordPress and then Staging, the staging2 copy appears. On the right, SiteGround’s assistant explains that the domain’s DNS is at GoDaddy, so the record has to be added there.

Every website address needs an entry in an “address book” called DNS. DNS tells browsers which server a name like staging2.cadence-group.com lives on.

  • The domain cadence-group.com is registered at GoDaddy.
  • Its nameservers (the setting that decides who runs the address book) still point to GoDaddy (ns51.domaincontrol.com and ns52.domaincontrol.com), not SiteGround.
  • The website itself now lives on SiteGround’s servers.

When you create a staging copy, SiteGround builds the copy on its server, but it can’t add the matching address to GoDaddy’s address book. So nobody’s browser can find the new staging site. SiteGround’s own staging guide says the same thing: if your nameservers aren’t pointed to SiteGround, you have to add the staging address yourself at your current DNS provider.

For staging2, Jim added that record by hand at GoDaddy on November 19, 2026:

Type Host Points to
A staging2 35.212.118.55 (the SiteGround server)

Step-by-step: your browser asks GoDaddy DNS where staging2 lives, GoDaddy answers with the A record Jim added (35.212.118.55), your browser connects to the SiteGround server, and the staging site loads.

When there’s no record (any new staging name)

Section titled “When there’s no record (any new staging name)”

Step-by-step: you type a new staging name, your browser asks GoDaddy DNS, GoDaddy has no record for that name, so the lookup fails and the site can’t be reached.

Flowchart: If staging2 is still listed in SiteGround, use staging2.cadence-group.com. If not, or you want a new name, create the copy in SiteGround, contact Jim with the new name, Jim adds the DNS record at GoDaddy, and after DNS updates the new staging site loads.

In short:

  1. Check SiteGround first. In Site Tools → WordPress → Staging, look under Manage Staging Copies. If staging2 is there, use it.
  2. If you need a new one, create it in SiteGround (see Creating, deploying and protecting staging copies).
  3. Contact Jim with the exact staging name SiteGround gave it (for example staging3).
  4. Jim adds the DNS record at GoDaddy. DNS changes can take a little while to show up everywhere.
  5. Then the new staging site loads.

Yes. If the domain’s nameservers were moved from GoDaddy to SiteGround (ns1.siteground.net and ns2.siteground.net), SiteGround could create staging addresses on its own, and your team could create and deploy staging copies without waiting on Jim.

The catch is that moving the nameservers moves all of the DNS for cadence-group.com to SiteGround, including the email records. Every existing record has to be copied over correctly first, or email and other services could stop working. That’s a decision for Jim to plan and make with you, so for now the nameservers stay at GoDaddy and Jim handles staging DNS.

  • Make your changes on staging and check them carefully.
  • Pushing to live is done from SiteGround with Full Deploy or Custom Deploy. Read what each one does before you click. A Full Deploy replaces the whole live site, including its database.
  • If you’re not sure, ask Jim before deploying.