Framer CMS SEO setup: Field by field

Framer CMS is fast to set up and easy to extend. The trade off is that the default fields skip the SEO and AEO essentials. Add these fields once and your editors can ship optimised content without thinking about it.

Required fields

Use the list below as a working reference. Each item is something specific you can check or action directly.

• metaTitle (text, 60 char counter).
• metaDescription (text, 160 char counter).
• slug (text, lowercase enforced).
• ogImage (image, 1200x630).
• publishedAt (date).
• updatedAt (date).
• author (reference to Author collection).
• category (reference).
• summary (text, 240 chars, used for cards and AEO extraction).

Schema integration

Inject Article schema in the page head using the CMS fields. Use a single shared schema component so every post is consistent. Add FAQPage schema only when the post has a real FAQ section.

Editorial fields worth adding

Beyond the SEO essentials, a few extra fields make it much easier for a non technical editor to ship AEO ready content without extra training.

• faqItems (repeatable question and answer pairs, optional per post).
• keyTakeaway (short text, surfaced as a callout near the top of the post).
• sources (repeatable link field for citations at the bottom of long form posts).
• readMinutes (number, calculated or manually set for the reading time badge).

Governance: keeping the CMS consistent over time

Field schemas drift as teams grow. Without a light process, editors start leaving fields blank or duplicating content across the wrong ones.

1. Document each field's purpose in a short internal style guide.
2. Make metaTitle, metaDescription and summary required before publish.
3. Review a sample of live posts quarterly for missing or duplicated fields.
4. Update the shared schema component in one place when requirements change.