Last verified: September 16, 2026
What You Can Now Do
Context Memo now supports a replace_text operation in Page Builder, so you can rename elements and fix spelling mistakes directly inside your memo layouts. A misspelled product name in an H2, a stale element label left over from a duplicated layout, an old feature name that no longer matches your positioning: all of it is now an edit, not a rebuild. The task this changes is small and frequent. When you catch a wrong string during review, you correct it in place and republish, instead of recreating the block around it or shipping the memo with a known error and queuing a fix for later.
Where It Is in Context Memo
The operation lives in Page Builder and is exposed through the builder's copilot, which now includes replace_text alongside its existing build operations. Open any memo in Page Builder and the copilot can act on the text inside the layout you have on screen. The change spans the copilot and copilot-server modules, so it is available wherever the Page Builder copilot is, with no separate setting to enable.
How to Use It
- Open the memo in Page Builder. The layout loads with its current elements and copy, exactly as they will publish.
- Identify the exact string you want changed. Copy the old spelling or element name so the replacement matches what is actually in the layout rather than what you remember writing.
- Tell the copilot what to replace and what to replace it with. The
replace_textoperation runs against the text in the layout and returns the updated version. - Check the affected elements on the canvas. Confirm the replacement landed in every place you expected and nowhere you didn't, including headings, body copy, and element labels.
- Publish the memo to your domain. The corrected text becomes the version AI crawlers and models read on their next pass.
Two practical notes. Replacements are literal, so include capitalization and punctuation in the string you supply if those matter, for example a product name with an internal capital letter. And if the string appears in structured fields such as an FAQ block, review those alongside the body copy before publishing, since a name that reads correctly in a paragraph should also be correct in schema-marked content.
Why We Built It
Customers told us they were manually recreating or working around text that needed renaming or a spelling correction inside a page layout. That is an expensive way to fix a two-character typo. It cost time in the builder, it discouraged small corrections that were technically worth making, and it left wrong strings sitting in published memos longer than anyone wanted. That last part is the real cost. A memo is written to be read and cited by models, and a misspelled brand or product name is a string those models can pick up and repeat. Corrections should be cheap enough that nobody postpones them.
What It Does Not Do Yet
The operation is scoped to the memo layout you have open in Page Builder. It is not a library-wide find and replace across every published memo, so if the same wrong string appears in five memos, you currently open and correct each one. It acts on text, not structure: renaming an element's text does not change its type, placement, or schema mapping, and layout changes still go through the existing builder operations.
Publishing remains a deliberate step. A replacement inside the builder updates the memo you are editing, and the live page reflects it once you publish, which keeps a review gate between an edit and what models crawl.
More broadly, Page Builder is built for citation-grade memos, not as a replacement for your CMS or marketing automation stack. Those systems carry functionality Page Builder does not, and we would rather you keep them as the system of record for your site while Context Memo handles the memo layer that AI models read.
