Why drafts and publication are separate
Editing content does not yet mean the public website changed. The workspace may contain a new draft and an earlier published text simultaneously. When checking results, open the public URL rather than the draft preview. This is particularly useful when an editor and agent collaborate: one prepares a new description, another checks facts, and visitors still read the previous version. Revision history identifies which version was published at the time of an observation or referral without attributing future changes to data already collected.
Version conflicts protect other people's work
Publication and modification operations check expectedRevision. For example, the agent read revision 7, but the owner has already saved revision 8. The correct next step is to reread the page, compare changes and prepare an agreed action. Retrying an old write with an invented new number can lose an editor's change and is not acceptable. Retries of the same operation use the same clientRequestId; a new intentional action uses a new identifier. These mechanisms distinguish a safe retry after a connection failure from a new publication with different content.
Organizing a restoration
First identify what must be restored: text, metadata, a published revision or page availability. Read the current history and choose a suitable existing version. After restoring it, check the public address and save the result in the log. If policy requires approval, rollback goes through that control. Not every action has a universal undo: availability depends on its type and retained information. Edits to the original website outside the managed section need their own versioning mechanism, such as Git or CMS history accessible to your external agent.
What rollback cannot reverse
A search engine may already have read old content, a visitor may have saved it, and an IndexNow notification may already have reached an external service. Restoring text does not erase these events. After a substantial correction, check the published page again and notify search when the change justifies it. A repeat AI answer is also collected separately: it does not arise from a ‘version restored’ record. The practical result is controlled public text and a clear correction history, not a promise to instantly restore former rankings, citations or referral counts.
Conditions and limitations
- Does not roll back search results
- Not all external actions are reversible
- Original-website versions are managed separately