Recover saved edits or restore an earlier page version

Guides

Identify what you need to recover

Unpublished cloud edits, page backups, and whole-site snapshots are different recovery sources. Choose the smallest one that solves the problem. A draft preserves unfinished editing; a page backup records an earlier saved page; a site snapshot is an administrator-level recovery resource for broader damage.

Confirm the exact website, page identity, and language. Stop editing duplicate tabs and coordinate with anyone else working on the page. Note what is wrong, when the last correct version was seen, and whether newer changes must be preserved. Never restore an entire website to fix one paragraph without assessing the unrelated content it would replace.

Resume unpublished cloud edits

1. Open the normal page while signed in. Pages start with live content rather than silently loading a draft. If a cloud draft exists and recovery is available, choose Resume saved edits to inspect that saved revision. Use Discard only when you intend to abandon those saved edits.
2. Compare the recovered content with the live page and any newer changes. Review the header, body, links, media, and metadata before publishing. Explicit Save publishes the visible recovered version; cloud autosave by itself does not publish it.
3. If an interrupted publish offers Finish publishing, review that recovery state. Retrying completes the original snapshot, not arbitrary later edits. Do not attempt to discard a pending publish while its original write may still succeed.

Review an earlier saved page

4. Open Page Backups from the page administration controls. Select an entry by its timestamp and inspect its preview before restoring anything. Check that the backup represents the intended page and language, especially when several pages have similar titles.
5. Use Edit on a backup when you want to open it as saved edits and review it in the page editor. The backup-opening operation prepares recovery; it does not mean you have published that older page. Resume, review, and save only after reconciling newer content.
6. If a direct restore is appropriate, use Restore and read its confirmation. The interface states that a backup of the current version will be created first. Restoration is still a write that can replace current content, so obtain explicit approval when an assistant or another administrator performs it.

Verify the recovered result

Open the normal page URL outside the editor after publishing or restoring. Check the original problem and nearby content, links, images, access settings, and phone layout. Reopen page administration to confirm the saved state rather than relying on an old browser tab.

If a conflict blocks saving, re-read the current version and reconcile; do not force a stale tab over newer work. Saved to cloud appears only after acknowledgement, so an unconfirmed browser close is not proof of recovery. Local development uses explicit disk saves, and templates and template-bound pages have separate autosave limitations.

For missing history or whole-site damage, ask an authorized administrator to assess snapshots and media recovery. Do not bulk upload local content as an improvised fix. See saving, recovery, and troubleshooting and templates and reusable content.