Skip to main content

Staging Environments

Staging gives you a safe copy of your website for testing before production changes.

Why staging matters​

Use staging to reduce risk when changing:

  • plugins and themes,
  • checkout or form behavior,
  • template/layout structure,
  • performance and caching settings.

Typical staging workflow​

  1. Open Websites and select Add new.
  2. Choose Clone a website, select the production website, and enable Make this a staging site.
  3. Select Add and wait for provisioning to complete.
  4. Apply planned changes on staging only.
  5. Test key user paths (forms, login, checkout, account pages).
  6. Confirm no major visual or functional regressions.
  7. Use Push live only after reviewing which production data may be replaced.

Staging and cloning must be enabled for the hosting package. A staging website does not provide domain mapping or email accounts and is marked noindex by default.

Validation checklist​

  • Homepage and key landing pages render correctly.
  • Navigation, forms, and integrations still work.
  • Mobile behavior is acceptable.
  • Error logs do not show new critical issues.

Good practice​

Refresh staging from production before major work so tests reflect current live content and configuration.

For stores and membership sites, remember that pushing an older staging database can overwrite new production orders, accounts, or form submissions. Ask support when you are unsure which data will be replaced.