Version history is the undo button your website never had

Most small business websites have exactly one version: whatever is live right now. If a change goes wrong, or someone deletes the wrong section, getting back to how things were means hoping somebody made a backup — and that it actually works.

Flagstage keeps a history instead.

How it works

Every time you approve a change, we save a complete snapshot of your site as it was at that moment. Not just the page that changed — the whole site, exactly as visitors saw it.

Those snapshots stack up into a history: the day your site moved in, the day you added the new service page, the day the holiday hours came down.

Why snapshots instead of backups

A traditional backup is a copy of a database and some files that have to be restored and reassembled before you know whether they work. A snapshot is the finished website. Putting a previous version back is a matter of pointing your domain at a snapshot that already exists, so it happens in one step.

When rollback helps

• You approved a new homepage design and, after a week, decide you liked the old one better.
• A seasonal promotion went up, and you want the previous version back exactly as it was.
• You need to show someone what your site looked like on a particular date.

What rollback doesn't touch

Rolling back changes what visitors see on your website. It doesn't delete form submissions you've received, and it doesn't change your domain or email settings.

How to ask for it

Just say what you want: "Can we go back to the homepage from before the summer update?" We'll show you a preview of that version first — the same rule as any other change — and put it live when you say so.