Last verified: September 22, 2026
What You Can Now Do
Context Memo now lets you define and reuse a shared header across multiple landing pages within a brand, instead of configuring a header individually on every page. Set your logo, navigation links, and call-to-action once at the brand level, and every landing page you build under that brand renders the same header. The practical change: when your nav changes, you edit it in one place. No page-by-page sweep, no orphaned pages still pointing at a retired product name or a dead pricing link. For teams publishing memos and landing pages across multiple campaigns, this moves header management from a per-page task to a brand-level setting.
Where It Is in Context Memo
The shared header lives in the landing pages builder, configured at the brand level rather than inside an individual page. Open the builder for any brand and you'll find the site header configuration alongside your other brand-level page settings. Individual landing pages now reference that shared header rather than carrying their own copy of it, so the header section on a page shows what it inherits.
How to Use It
- Open the landing pages builder for the brand you're publishing under. You'll see the site header configuration at the brand level, separate from the individual page canvas.
- Configure the header once: logo, navigation links, and your primary call-to-action. Save it. The saved header becomes the default for pages in that brand.
- Open an existing landing page in the builder. The header section now reflects the shared brand header instead of the per-page configuration you previously set up.
- Publish or republish the page. The live page renders the shared header, and the version your buyers and AI crawlers see matches every other page in that brand.
- When your navigation or CTA changes, edit the shared header at the brand level. Every page that references it picks up the change on its next publish, so you're not auditing pages one at a time to confirm consistency.
Why We Built It
Customers told us they were recreating the same header configuration on every landing page they built. Ten pages meant ten headers, each one a separate opportunity to mistype a URL, skip a nav item, or leave last quarter's CTA in place. The cost showed up twice: setup time on every new page, and inconsistency on the pages nobody remembered to update. That second one matters more than it looks. Landing pages are part of your citable surface area. When AI models crawl your domain and find pages with conflicting navigation, mismatched brand names, or links to products you no longer sell, that inconsistency becomes part of how models describe you. A single source of truth for the header removes a class of drift that used to require manual discipline to prevent.
There's a compliance angle for larger teams as well. If your legal or brand team approves header copy, links, and disclosure placement, approving it once at the brand level is auditable in a way that approving it fifteen times across fifteen pages is not. One configuration, one review, one record of what changed and when.
What It Does Not Do Yet
A few limits worth knowing before you restructure your page library around this:
- Scope is per brand. The shared header applies across landing pages within a single brand. If you manage several brands in Context Memo, each one carries its own header configuration. There's no cross-brand header inheritance.
- Publishing is still per page. Editing the shared header does not silently rewrite pages that are already live. Pages pick up the updated header when you publish them. If you change the nav and want it reflected everywhere immediately, republish the affected pages.
- This is a header, not a template system. Footers, page-level sections, and body layout are still configured where they were. The shared configuration covers the site header only.
- Not a CMS replacement. Context Memo's landing pages builder is built for publishing citation-grade memos and supporting pages on your own domain. If you need full content management, complex page hierarchies, or a marketing automation layer, keep that in your CMS and use Context Memo for the AI-visibility layer. The two are meant to sit alongside each other.
One workflow note: if you have existing landing pages with per-page headers you spent time tuning, check them after you configure the shared header. Decide which version you want as the brand standard, set that once, then republish. It's a one-time reconciliation rather than something you'll revisit.