Publishing and domains
Version history and staging
Every publish is kept; bring one back. Stage a version privately for a client to approve.
- 3 minute read
- 3 interactive walkthroughs
- For everyone publishing a website
Version history#
Every time a website is published, the version it replaces is kept. Version history lists them with the date, the person who published, any note written in the Publish dialog, and their state: the one that is live, and any that sit on a staging address.
Preview opens any version exactly as visitors saw it, which is the honest way to answer "what did it look like before?" and the quickest way to copy a sentence from the old wording.
Step 1 of 3
A shelf of versions
Every publish keeps the version it replaced, with the date and the person who published.
Reduced motion is on, so the walkthrough waits for you. Use the arrows or pick a step.
- 1Open Version history from the website menu.
- 2Preview a few older versions.
- 3Note the one to restore, if any.
Bringing a version back#
Each older version has Make live and Restore. Make live puts that version in front of visitors straight away: its pages, design and settings. The products stay as they are now, because products are published on their own, and anything changed in the editor since stays in the draft for later. The version it replaces is kept, so it can be undone the same way.
Restore copies the version into the editor instead, products included, replacing the current draft. Nothing changes for visitors until you publish, which makes it the careful choice when the old version is a starting point rather than the answer.
Step 1 of 3
Preview first
See the version exactly as it went out before committing to it.
Reduced motion is on, so the walkthrough waits for you. Use the arrows or pick a step.
Before you continue: Make live returns every page as it was in that version, including pages removed since and without pages added since. Anything published after it is kept in its own history entry, but visitors will see the older version.
Staging for approval#
With Pro, a website can also have staging addresses: private copies, each with a name and a password, for showing the next version to a client before it is public. Send to staging puts the current draft there, behind the password, and the client sees the real site rather than screenshots.
When the client says yes, Make it live promotes exactly the version they approved, products included, which removes the last gap between what they saw and what goes public.
Step 1 of 2
Private copies
Staging addresses carry a password, for showing the next version without it being public.
Reduced motion is on, so the walkthrough waits for you. Use the arrows or pick a step.
- The staging password shared only with the people giving feedback
- Feedback on the staged version, not the live one
- The approved version the one that gets promoted
Common questions
How long are versions kept?
They are kept as long as the website exists, so a restore is possible months later. Deleting the website deletes its history.
Does an old version bring back old products?
Make live keeps the products visitors see now. Restore puts the old version's products back into the draft, to publish when you choose.
Does staging cost extra?
Staging is part of Pro. It does not need its own licence: it belongs to the website and its licence.
Related guides
- Publish and unpublishChoose what goes live in the Publish dialog, publish products on their own, see what is waiting, and take a site offline without deleting it.Publishing and domains
- Fix an earlier versionUse version history to find, preview and restore what the site looked like before.Troubleshooting
Something here out of date, or a step that did not match what you see? Tell us and we will correct the guide. Never send a password or an API token.