How to Undo Changes in the GoDaddy Builder (and Restore Old Versions)

Ten minutes into a redesign, a section you liked is gone and the layout is fighting you — that's usually the moment people learn how to undo changes in the GoDaddy website builder properly. There are two mechanisms, and they solve different problems: the Undo and Redo buttons for the mistake you made a minute ago, and Site History for restoring the state your site was in last Tuesday. This procedure covers both, plus the rollback traps that catch people.

When do you need this? A theme experiment that soured. A section deleted in haste. A well-meaning helper who "improved" the homepage over the weekend. Or the quiet kind of damage — a dozen small edits over an hour that added up to something worse than what you started with. The builder saves your changes as you work, which is convenient right up until the change it saved was wrong. Recovery, then, is not one tool but a choice between two, and picking the right one first saves real time.

Prerequisites

• Access to the site's editor — both tools live inside it, not on the dashboard.
• A rough idea of when the site was last right. Restores are chosen by backup timestamp, so "sometime before Tuesday's theme change" is genuinely useful information.
• A grasp of draft versus live: the editor is a working copy, and nothing reaches visitors until you press Publish. This distinction matters twice below.

How the two tools divide the work

Undo and Redo are for the current working session: a deleted paragraph, a color you regret, a section dropped in the wrong slot. They step through recent edits one at a time, in order. Site History is the heavier machine: a version archive of the whole site that lets you jump back to a named moment — before the theme change, before the helper got creative. Rule of thumb from the bench: if the damage is measured in clicks, use Undo; if it's measured in hours or days, go straight to Site History and stop guessing.

Quick fix: the Undo and Redo buttons

1. In the editor, find the Undo and Redo buttons in the top navigation bar.
2. Select Undo to step backward through your recent edits, one at a time.
3. Select Redo to step forward again if you overshoot.

That's the whole tool, and its scale is the point: Undo is for the current session, not for archaeology. If the damage happened yesterday — or you can't remember everything that changed — stop clicking Undo and move to Site History instead.

Procedure: restore an old version with Site History

Site History is the builder's version archive. It records automatic backups at major events — a theme change, a publish, a section delete — and lets you save manual backups on top of those. Restoring one returns the site build to that moment.

1. From My Products, expand Websites + Marketing, select Manage, then Edit Website.
2. Go to Settings → Site History.
3. Review the backup list and identify the one from when the site was last right.
4. Before restoring anything, save a manual backup of the current state — this is your escape hatch if the restore turns out to be the wrong call.
5. Hover over the backup you want to return to.
6. Select Restore.
7. Inspect the editor carefully, then Publish to push the restored version live.

CAUTION: Restore rolls back every change made after that backup's timestamp — the entire site, not a page or a section. There is no partial restore. Anything you built after that point vanishes from the editor the moment you restore, and if you skipped the manual backup in step 4, there is no way back to it.

What restore does — and doesn't — roll back

A restore rewinds the site build: pages, sections, text, layout, theme. It does not delete your uploaded images, your products, or your appointments — those live in the dashboard, outside the page history, and they survive every restore untouched.

The practical upshot: your image library is safe, but a page restored from an old backup may no longer display pictures you placed after that date. The files still exist — re-place them on the page and republish. Same logic for products: the catalog is intact even if the page showing it went backward in time.

The publish-state trap

Remember that the editor is a draft. Restoring a backup changes the working copy only — your live site keeps showing whatever was last published until you press Publish. That cuts both ways: it protects visitors from a half-finished restore, and it explains the classic confusion of "I restored but the site didn't change." Equally, once you do publish, the rollback is what the world sees — inspect the whole site in the editor first, not just the page that prompted the restore.

Variations and edge cases

• Comparing themes: because a theme change triggers an automatic backup, you can switch, look around, and restore if you hate it. Just do it before making content edits — see the trap below.
• Multiple sites on one account: Site History is per site. Open the editor for the site you actually mean to rewind before touching anything.
• Account-level items: Site History is documented as rolling back site changes — the build. Treat things that live outside the editor, like domain connections and subscriptions, as beyond its reach.
• Editing from a phone: the editor runs on mobile devices too, and the same top-bar controls apply — though for a careful restore-and-inspect job, a full-size screen is the better bench.

Versioning habits that save future-you

• Save a manual backup before anything structural — a theme switch, deleting sections, rebuilding the homepage. It costs seconds and buys you a named restore point.
• Publish at milestones. Every publish creates an automatic backup, so shipping known-good states builds your archive for free.
• Mind the theme-change trap: the backup taken at a theme switch stores content as well as design, so restoring it also discards every edit you made after switching. Back up again once the new theme has settled in.
• Deleted a section by accident? The editor takes an automatic backup at section deletion — that's often the cleanest restore point available.

Session-scale undo plus whole-site restores — with nothing in between — is part of this builder's character. Our GoDaddy Website Builder review weighs that quirk against what the platform does well. Every other procedure in this manual is filed in the GoDaddy tutorials index.