Memo Metadata in 📝MythOS gives creators control over how their public memos appear in search results and social cards. Three optional fields — SEO Title, Meta Description, and Canonical URL — can be set per memo to override the auto-generated values derived from the memo title and body snippet.

Fields

• SEO Title (max 70 characters) — overrides the memo title in <title>, Open Graph, Twitter Cards, and JSON-LD structured data
• Meta Description (max 160 characters) — overrides the auto-generated snippet in meta description tags and social previews
• Canonical URL (HTTPS only) — points search engines to the original source when a memo is cross-posted from another platform (e.g., a WordPress blog migration)

Override Chain

When a field is populated, it takes precedence over the auto-generated value:

• seoTitle → header.title → platform default
• seoDescription → header.snippet → platform default
• canonicalUrl → auto-generated permalink

For private memos, these fields are editable but meta output always uses platform defaults — no custom SEO data leaks into HTML.

Where It Lives

The fields appear in the right sidebar under the Metadata section (formerly "Hero Image"), below the hero image upload. They save automatically on blur via PATCH /api/me/{username}/{id}/seo. Sending an empty string clears an individual field.

Tier Gating

• The Metadata section is visible to all creators (hero image has no tier gate)
• The SEO fields within the section are restricted to Scholar and Oracle members
• The API enforces the same tier check server-side, with an isTestPersona bypass for development

API

• PATCH /api/me/{username}/{id}/seo — set or clear individual fields. Accepts { seoTitle?, seoDescription?, canonicalUrl? }. Null or empty string clears the field
• DELETE /api/me/{username}/{id}/seo — bulk clear all three fields
• Both endpoints require Bearer token auth and Scholar/Oracle tier

Contexts

• 🏷️#mythos-api
• 🏷️#mythos-feature
• 🏷️#search-engine-optimization