Last verified: September 15, 2026
What You Can Now Do
Context Memo now lets you set an image per memo, so the header, the public index card, and the link preview can each carry a picture that belongs to that specific memo instead of one banner repeated across your whole library. When you set an image, Context Memo writes it into the page's Open Graph tags, Twitter Card tags, and the schema.org image property, so the asset travels with the link when someone pastes it into Slack, LinkedIn, or an email. The decision this changes: you no longer have to accept a generic house banner on a library of memos about unrelated topics, and you no longer have to hand-edit markup to make a shared link render correctly.
Where It Is in Context Memo
Image settings live with each individual memo rather than in site-wide theming, so you'll find them in the memo's own publishing and settings area alongside the other per-memo attributes that control how the page renders publicly. Each memo carries its own image assignment, its own alt text, and its own preview.
How to Use It
- Open the memo you want to change and go to its settings. Upload or select the header image. The header on the published page updates to that asset.
- Enter alt text for the image. Alt text is stored with the file and is what a screen reader and a text-only parser read in place of the picture, so write the substance of the image, not "header photo".
- Confirm which image maps to which surface: the in-page header, the card that appears in your public memo index, and the preview image used when the link is shared. Setting one image populates the shared metadata; check the index card to see how it crops.
- Check the file weight before you publish. A heavy hero image slows first render on the page an AI crawler is fetching, and nothing about the image earns you a citation. Export at the smallest size that still looks correct at full width.
- Publish, then paste the live URL into whatever channel your buyers actually use. The preview should show your image, title, and description. If a channel caches an older preview, re-fetch the URL in that platform's debugger so it picks up the new tags.
- Repeat per memo, not per site. Fifty memos can carry fifty distinct cards, which is the point of the per-memo model.
Why We Built It
Customers kept telling us the same thing: "our memo index looks like fifty copies of the same page." A library built for AI consumption still gets shared by humans, and when every card and every link preview used one brand banner, the memos on pricing, security, and integrations were visually indistinguishable at the moment a buyer decided whether to click. Before this, the workaround was either accepting a global banner or editing page markup by hand to get Open Graph and schema image values right, which is slow and easy to get wrong in ways nobody notices until a link renders blank in a sales thread.
What It Does Not Do Yet
- We don't compress, resize, or generate crops for you. Optimizing the asset for weight and aspect ratio is still your step, and it matters more than the image choice itself for page performance.
- Assignment is per memo. There's no bulk apply across a set of memos, so a library-wide visual refresh is still a memo-by-memo pass.
- Alt text isn't written for you. If you leave it blank, the file publishes without it, and the text parsers reading your page get nothing in its place.
- Context Memo is not an asset library. We store what you attach to a memo, and we don't replace a CMS or a digital asset manager for versioning, rights, or reuse across channels. Keep your canonical assets where your team already manages them and attach from there.
One expectation to set plainly: images change click-through and how a shared link renders. They do not change whether a model cites you. Citation still comes from the structured substance of the memo, the schema around it, and the authority of the domain it sits on. Treat the photo as the thing that gets a human to open the page your buyers were already going to be shown by a model.
