Last verified: August 31, 2026
What You Can Now Do
Context Memo's Page Builder Chat now accepts relative positioning, so you can tell the assistant where a block goes instead of moving it afterward. Reference an existing block by name and a spatial relationship to it: above, below, before, after, or inside a named section. "Add a FAQ accordion below the pricing table" resolves to a specific insertion point rather than an append operation at the bottom of the page. The task this changes is the one after generation. You used to generate, then drag, then scroll, then drag again because the block dropped into the wrong container. Now the block arrives in position, and the only decision left is whether the structure reads correctly.
Where It Is in Context Memo
It's in the Page Builder Chat panel, the same assistant you already use inside the page builder to generate blocks. There's no separate screen. The change is in what instructions the panel accepts: positional phrasing that names a target block now resolves to an insertion point on the canvas, and the placement is reflected immediately in the block list.
How to Use It
- Open the memo or landing page in the page builder and read down the block list. The names you see there (pricing table, hero, a named section) are the references the assistant can resolve. Rename anything ambiguous before you prompt.
- Type the instruction with the target and the relationship in it. "Insert a definition block above the comparison table." The assistant generates the block and places it at that point, not at the end.
- Check the insertion point on the canvas. If the block landed inside a container you didn't intend, restate the instruction with the parent section named explicitly: "inside the FAQ section, after the second question."
- Chain the next instruction off the block you just placed. Because each reference is relative, you can build a full page structure in sequence without touching the canvas between steps.
- Read the heading sequence from top to bottom before publishing. Order is the thing you're controlling here, so confirm the direct answer sits above the supporting setup rather than at position nine.
- Publish. Schema marking and own-domain publishing run as they already do, with the structure you just set carried through.
Why We Built It
The complaint was consistent and specific: the assistant could write the block, but it couldn't put the block anywhere useful. You'd ask for a three-column feature grid, get a good one, and then spend the next few minutes dragging it up the page and fixing the container it landed in. That cleanup is a tax on every generated block, and it scales with page length, which means it was worst on long pages, landing page variants, and templated resource libraries. Those are exactly the places teams wanted the assistant most. Copilot-assisted page design only pays for itself when the assistant finishes the job.
There's a second reason, and it's the one that matters for AI visibility. Block order is semantic. The sequence of headings, definitions, tables, and FAQs on a page is what tells both a human reader and a machine parser where the hierarchy is. A page where the answer sits above the setup gets read differently from one where the answer is buried below nine blocks of context. Precise placement puts that hierarchy under your control at the moment of creation instead of making it a separate editing pass you may or may not get to.
What It Does Not Do Yet
Relative positioning applies to insertion. It places new blocks against existing ones; it does not reorder blocks already on the page in bulk from chat. Rearranging an existing layout is still manual work in the block list.
Resolution also depends on the reference being unambiguous. If two blocks share a name, or the named block doesn't exist on the page, the assistant has nothing to anchor to. Naming blocks clearly as you build is the practical fix, and it's worth doing anyway for anyone who inherits the page.
One boundary worth restating: the page builder is for publishing citation-grade memos and pages on your domain, not for replacing your CMS or marketing automation stack. Those systems do more, and we don't recommend moving that work here. Use Context Memo for the content layer AI models read, and keep the rest where it lives.
