Last verified: August 23, 2026
What You Can Now Do
Context Memo now keeps a version history for every landing page, so each saved and published state is retained and can be previewed and restored. A page is no longer a single-state object where the last save erases the one before it. What changes for you is the response to a bad edit: instead of rebuilding a section from memory or asking around the team, you open the page timeline, identify the save that preceded the problem, and put that state back. If conversions slip on a URL taking both AI-referred and paid traffic, the history tells you which edit landed immediately before the drop.
Where It Is in Context Memo
Version history sits with the landing page itself, in the page-level panel alongside page settings in the builder. That panel now lists retained states in reverse chronological order. Each entry carries a timestamp, the editor who made the change, and a marker for whether the state was published or held as a draft. Selecting an entry previews the page as it stood at that point.
How to Use It
- Open the landing page in the builder and open the history panel from the page-level menu. You get the full list of retained states, newest first.
- Scan the entries by timestamp and editor. Published states are labeled separately from drafts, so you can separate what buyers actually saw from what someone was still drafting.
- Select a state to preview it. The preview renders the page as it existed at that save, including layout and assets, not a text-only comparison.
- Preview the state immediately before it and confirm which edit introduced the change you're chasing.
- Restore the state you want. It becomes the current working state of the page.
- Publish the restored state. The live URL returns to that version, and the restore itself is recorded as a new entry in the history.
Why We Built It
The question we heard most from page owners was blun: "who changed this?" Campaign pages collect late-cycle edits from stakeholders who don't own the page, and before this shipped, the page owner's only recovery path was memory and a screenshot if someone happened to take one. The cost showed up twice: hours rebuilding a page the night before a launch, and copy changes that quietly suppressed conversions for days because nobody could point to the edit that caused them.
What It Does Not Do Yet
- Only states saved in Context Memo are captured. If a page is edited in an external CMS or template system, that change isn't in the log. Context Memo isn't a CMS replacement, and pages you maintain elsewhere still need their own revision trail.
- Comparison is visual, not field-level. You compare two states by previewing each one. There's no side-by-side diff of individual fields or blocks yet, so on long pages, use the timestamp and editor to narrow down candidates before previewing.
- Restore acts on the whole page state. Bringing back one section from an older version means restoring that version and re-applying the newer edits you want to keep.
- Restores aren't live until you publish. Restoring sets the working state. The public URL doesn't change until the publish step, which is deliberate, but it does mean a restore alone won't fix a live page.
Version history is most useful when it's part of how you audit, not just how you recover. When a memo or landing page is pulling citations and then stops, the timeline gives you a factual starting point instead of a guess. Check the history before you change the page again.