How to roll back a website to a previous version

Stop and work out what changed

Before restoring anything, spend two minutes on what went wrong. Is the problem on the live site or only in the editor? Did it start with one edit you remember, or after an AI assistant, a coding agent or a colleague changed things? Is it the page's content, or something around it, such as a domain, a form connection or a payment link? The answer decides whether a rollback is the right tool at all, and how to roll back a website to a previous version without losing good work. A wrong phone number is quicker to fix by hand; a page whose layout fell apart after a batch of changes is what rollbacks are for.

The general method, on any platform

Find the version list. Builders call it history, revisions or versions; with code, it's your Git log; with a host, it may be a list of deployments.
Identify the last good version by time and by who made it. If you're unsure, note the time you last saw the site working.
Preview it without saving, if the tool allows. Check the part that broke and anything you changed on purpose since.
Restore it. Good tools save the old version again as a new one, so the broken version stays in history and you can go back if you picked wrong.
Republish or redeploy. In many tools, restoring changes the project but not the live site until you publish.
Re-apply the good changes made after that version, one at a time, checking after each.
Check the live site in a private window on a phone and a laptop, and send a test through each form.

Rolling back an Anticode site

Anticode keeps a project's saves as versions: the most recent ones, up to a number set by your plan and shown in the panel. Saves made by you, by the CLI or a coding agent, and by an AI assistant through MCP are all recorded and labelled by source.

Open the project in the builder and choose History from the project menu in the chat header.
The list shows versions newest first, each labelled with who made it, such as Your edit, CLI or coding agent or AI assistant (MCP), and when.
Select a version to preview it on the canvas. Nothing is saved while you look; Back to current returns to where you were.
Press Restore this version. Anticode saves it as a new version, so every earlier version, including the one you're leaving, stays in History.
The publish button now offers to Update live site, because the project no longer matches what's published. Press it to put the restored version live. Publishing runs the security checks again.

Separately, Anticode backs up the last ten published versions of each site and checks published files against hashes recorded at publish, about once a day per site. That's a safety net for the live files rather than something you browse; version history is the tool for undoing your own changes. If a change came from the CLI, an assistant or an agent while the builder was open, the canvas shows it with an undo straight away, which is quicker than History for a change you've just seen.

What a rollback does and doesn't undo

What restoring a version covers on a typical site builder
Thing	Restored?	Notes
Page text, sections, order and design settings	Yes	This is what a version stores.
Form submissions received since	No	They're data, not design, and they stay where they are.
Uploaded photos and files	Usually not	The version refers to them; deleted files may not come back.
Content in collections or a CMS	Often not	Many builders store entries separately from page versions; check before relying on it.
Domains, connectors, payment links	No	These are account or site settings, not part of a page version.
What visitors and search engines already saw	No	Caches and shared previews update over time.

Mistakes that make rollbacks harder

Restoring without previewing, then discovering the old version also lacks a week of good edits.
Forgetting to republish, so the editor looks fixed while the live site is still broken.
Rolling back twice in a panic. Each restore is a new version; make a note of the version numbers you tried.
Letting several people or agents edit at once. It muddies the history. Make big changes in one sitting and check them before the next round; the safe big-changes workflow shows an order of work.

Limits

History only goes back as far as your plan keeps versions, so for a site you care about, keep your own copy too: Anticode can export a single HTML file or a Next.js project, which backing up a website covers. A rollback can't recall emails already sent from a form, payments taken through a link, or changes made at your domain registrar.

Questions people ask

Does restoring a version change my live site straight away?

In Anticode, no. Restoring changes the project; the live site changes when you press Update live site. Many other builders work the same way.

Can I undo a rollback?

Yes. The version you replaced is still in History. Restore it the same way.

How do I undo a change an AI assistant made?

Look in History for the version labelled AI assistant (MCP) and restore the one before it, then publish. If the builder was open when it happened, use the undo it showed.