Sharing & hosting
Every full-site deploy is reversible: how versioning works
1 September 2026 · 2 min read
Uploading a new version of a full site is a little nerve-wracking the first time: what if the new files break something, or you meant to keep the old homepage a while longer? MakeMySiteLive retains recent full-site deployments so you can step back. Free full sites keep the latest 3 versions and Pro full sites keep the latest 10; microsites update in place instead.
Uploads don't overwrite, they add
Every time you deploy a new full-site ZIP, MakeMySiteLive creates an immutable version and makes it active. The previously active deployment stays in version history until it falls outside the retention cap: the latest 3 versions on Free full sites or the latest 10 on Pro full sites.
Rolling back is one click
If a new upload breaks something, missing images, a typo that matters, a layout that didn't survive the export, you don't need to rebuild the fix under pressure. Pick the previous version from the list and roll back, and the site goes back to exactly how it looked before, live again in seconds.
What this actually protects you from
A bad ZIP export. A last-minute edit that introduced a typo. An AI tool's regenerated output that lost something the previous version had. The recent working deployment remains available within the site's retained history, so the newest mistake doesn't have to become an emergency.
It works the same for AI-published sites
A full-site deployment through the CLI, REST API, or Claude over MCP creates a version the same way a dashboard ZIP upload does. Rolling back doesn't care which path published it. Microsite publishing is different: it updates the current content in place and doesn't retain rollback history.
Key takeaways
- ✓Every full-site upload creates an immutable version instead of overwriting the previous one.
- ✓Rolling back to an earlier version takes one click and is live again in seconds.
- ✓Free full sites retain the latest 3 versions and Pro full sites retain the latest 10; older versions are pruned.
- ✓Dashboard, CLI, REST API, and MCP full-site deployments share the same version history.
- ✓Microsites update in place and don't have rollback history.
Frequently asked questions
Do old versions of my site get deleted?
Yes, once they fall outside the retention cap. Free full sites keep the latest 3 versions and Pro full sites keep the latest 10; older versions are pruned automatically.
How do I undo a bad upload?
Open the site's version history in the dashboard and roll back to the version before the one that broke something. It goes live again in seconds.
Does rolling back lose the broken version entirely?
No, rolling back just changes which version is live. The version you rolled back from is still there if you ever need to look at it again.
Does this work if I deployed through the CLI or Claude instead of the dashboard?
Yes for full-site deployments through the CLI or Claude's full-site tools. Microsite publishing updates in place and doesn't create rollback history.