Rolling back a website change
If a website change doesn't turn out the way you wanted, you can put your site back the way it was before — no rebuilding required.
Where to do it
Go to Settings → Site. You'll see a table of your site's recent versions, each with the date it was published and a Rollback button. Press it on the version you want, and that version becomes the one being served — no rebuild needed. Your own browser can still show the old page for a few minutes afterward (it caches pages briefly), so if you check right away and it looks unchanged, give it a few minutes or reload.
There's no confirmation step, so double-check you've picked the right row before pressing it. It isn't destructive — you can roll straight back again — but the switch itself happens as soon as you press it.
I'll remind you it's there
Right after I publish a change to your live site, I'll mention in chat that you can roll it back anytime if it doesn't look right, and ask you to tell me what was wrong so I can fix it going forward — you don't have to remember this article to find the switch. You'll also see a reminder in Settings → Site itself, right above your version history, whenever there's actually an earlier version to go back to.
What rolling back does
Rolling back changes which version of your website is live, and it resets the starting point I work from for your next website change (see below). It doesn't touch your business details, your payments account, your email, or anything I'm working on in the background — just the site.
How far back you can go
Your ten most recent published versions are kept and available to roll back to. Older ones age out to keep storage tidy — an aged-out version still shows in the table, dimmed and marked as expired, but with no Rollback button, because the files behind it are gone.
The version that's currently live is never aged out from under you, no matter how old it is. So if you roll back to an older version and stay there, it stays available.
The next change starts from what's live
Rolling back moves your starting point too, not just what visitors see. If you roll back and then ask me for a website change, I build on the version you rolled back to — so publishing that change won't quietly bring back whatever you rolled away from.
It's still worth telling me what was wrong with the change. Rolling back stops the bleeding; knowing what you didn't like is what keeps me from doing the same thing again next time. And if you'd rather go the other way — you rolled back, then decided you wanted the newer version after all — you can roll forward to it from the same table, as long as it's still in your version history.
Rolling back isn't the same as asking me to undo something
This is a manual switch you make yourself in Settings → Site, not something you ask me for in chat today — there's no "undo my last website change" I can act on directly. If you'd rather just describe what you don't like and have me fix it, that works too, and per the section above it's usually the better option.