Knowledge base
Testing changes on staging first
A full copy of your site on its own URL, so an update that breaks something breaks a copy.
Staging is your site — files, database, plugins, content — copied to a separate address that search engines are told to ignore.
Creating one
Sites → your site → WordPress → Staging copy. It takes a few minutes and does not affect the live site.
What it is for
Plugin and theme updates, PHP version changes, code changes, and anything you would rather not discover in front of customers. Update on staging, look at the site, then update live.
Pushing changes back
You can push files, the database, or both. ⚠️ Pushing the database overwrites live content — orders and comments taken since you copied are lost. For a normal plugin update, push files only.
Keeping it fresh
A staging copy made three months ago tells you very little about today's site. Refresh it from live before you test something important.
What is different from live
Staging is noindex so it cannot compete with your real site in search results, and outbound email is held rather than sent, so a test order does not email a real customer.
⭐ Delete a staging site you have finished with. It counts against your plan's storage, and an out-of-date copy of your site sitting on a URL somebody might find is not doing you any favours.
Still stuck?
Support is included on every plan and answers in your own language.
Contact support → All articles →