Skip to content
Security

Protected from first publish

Undo should be a decision you make, not a request you submit.

The most common way a website breaks is not an attack — it is a change. A page edited quickly before a holiday, a navigation tidy-up that buried the maintenance contracts page, a form that quietly stopped routing to the right person. In Siteleon every publish creates a restore point covering pages, structure, settings and the business facts behind them, labelled with what changed and who published it. Restoring is something you do yourself: pick the point, see exactly what would change, confirm. Copies are held apart from the live site, so a bad edit or a compromise there does not take the history with it.

Restore point per releaseSelf-serve restoreChange preview before confirmIsolated off-site copies

Restore points read as changes you recognise

The list is not timestamps and version hashes. It reads as a change you remember making — new commercial maintenance page, pricing block updated, published by your office manager on 23 August — so finding the right moment takes seconds rather than a call.

You see what a restore will change

Nothing is reverted silently. The preview shows which pages, settings and content would move back and which would stay, and you confirm — the same approval step that applies to any high-impact change Siteleon proposes.

Copies are kept away from the live site

Backups sit on separate managed infrastructure rather than on the machine running your site, so losing one does not mean losing both. Retention schedules and the recovery detail are set out in the Trust Centre.

Your business online. Built to adapt.

Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.

No technical setup · Keep your existing site if you want to · [email protected]