Page revision history and restoring content

Documentation / Saving, recovery, and troubleshooting

Page history preserves earlier content separately from unpublished cloud edits. Use it when a saved change needs reversal or when you want to recover selected text, layout, or custom source. Confirm the website, page ID, and language before choosing a revision.

Review in the CMS

Open the page's Backups tab or View page backups action. The list can include saved drafts as well as backups, so check the entry type and timestamp. Use Preview to inspect a backup before Restore.

The restore confirmation says that a backup of the current version will be created first. A full restore is a content mutation, not a read-only comparison. Avoid making concurrent edits while the restore is in progress, then reopen the page and verify its rendered result.

Do not use Delete merely to leave the preview. Deleting a backup removes a recovery record and has a separate irreversible confirmation.

Inspect history through an assistant

list_page_revisions lists revision metadata for the selected page and language. get_page_revision retrieves a complete snapshot. These are inspection tools, not automatic restore commands.

After reviewing the snapshot, approve the fields to recover. An assistant can apply them through a normal page update using the latest expectedPageModifiedAt. Preserve current identity, path, root, and translation identity unless changing those is part of the approved recovery. Direct updates affect saved content immediately.

Know the limits

A page revision does not restore root ordering, every template dependency, site settings, or the active shell. Use the matching recovery mechanism for those resources. History is subject to the workspace's retention and actual stored records; do not assume permanent availability.

If the desired entry is missing, stop destructive cleanup and ask an administrator about snapshots or other retained backups. See saving and recovery.