In short. Framer generates CMS pages from a shared detail layout and loads each collection item's fields into it.
Definition: A Framer CMS detail page is one reusable page layout connected to a collection. Framer uses the layout for each collection item, loading that item's fields into the page and generating content that can appear on the published website.
Key facts
- Framer recommends its built-in CMS for blogs, articles, and documentation, and says it automatically generates pages for search engines to crawl and analyze in its SEO features guide.
- Framer describes CMS Pages as dynamic pages generated from CMS collections with a shared template. Its example uses blog posts, news articles, product pages, and case studies in Using pages.
- The documented creation path is Pages, New CMS Page, a collection, then Detail Page, according to Framer Academy's CMS detail page lesson.
- Each collection item has field data, a unique slug, and a draft status. Framer's CollectionItem reference says drafts are excluded from publishing.
How does one layout serve many pages?
The collection stores repeated records such as articles. The detail page supplies the presentation shared by those records. Framer's page documentation says that a single page template displays each item in a collection, including individual blog posts or articles. Content placed inside a page is visible on the published website, while the surrounding Canvas is not published.
The detail page lesson describes the binding step: CMS variables connect each layer or component property to the current item. A text layer can use a title field, an image can use an image field, and a link control can use a link field. Selecting another item from the canvas dropdown previews different values while the layout stays the same. An edit to that layout applies across the collection.
Pages > New CMS Page > [collection] > Detail Page
This creates the shared detail-page structure. The collection item supplies the values that make one rendered page different from another.
What makes an item a published page?
Framer's CollectionItem reference identifies an item as a row in a CMS Collection. It documents field data, a unique slug, and draft status as properties of that item. The slug is therefore the item-level value to inspect when checking a published address, while the detail page remains the shared layout. The reference states that slugs should be unique within a Collection and that drafts are excluded from publishing.
Framer's page documentation describes CMS Pages as automatically generated from collection content. The SEO guide applies this model to blogs, articles, and documentation and says that the generated pages are for search engines to crawl and analyze. A published item URL therefore represents a collection record rendered through the detail page, subject to that item's publishing state.
How can each page get its own search metadata?
Framer's SEO documentation allows metadata for CMS pages. Its current metadata guide explains that CMS fields can dynamically populate both meta titles and descriptions, so each CMS page reflects its individual content in search results. The setup uses plain text fields in the collection, then references those fields from the CMS page's Page Settings.
Title field: {{Title}}
Page description field: {{Description}}
The same guide says to enter {{Title}} in the Title field and {{Description}} in the Page description field. This keeps the page template shared while allowing the title and description to come from each item. Framer also documents CMS cover images for social previews, with an image field selected from Page Settings.
What should you check before publishing?
Preview more than one item from the canvas dropdown. The detail page lesson says that the values change for each item while the shared layout remains the same. Check bindings for titles, images, body content, and links, then check items with missing values. Framer documents visibility conditions for cases such as hiding a button when the current item has no URL.
Check the item's slug and draft status in the CMS. A unique slug identifies the item within its collection, and a draft is excluded from publishing. Finally, inspect the CMS page's Page Settings for dynamic metadata and publish the site so the configured content is available on the live website.
Related terms
- Can search engines read Framer overlays?
- How are semantic HTML tags assigned to Framer layers?
- XML sitemap
- Canonical URL
FAQ
Does Framer create a separate canvas layout for every CMS item?
No. Framer's CMS detail page lesson describes one reusable layout for individual items. The item fields change while the shared layout stays the same, and a layout edit applies across the collection.
Where does the content for one detail page come from?
The current collection item supplies the values through CMS variables connected to layers and component properties. Framer's CMS detail page lesson gives text, images, and links as examples of fields that can be bound to the layout.
Can a CMS item be published without being ready?
Framer's CollectionItem reference documents a draft status and says drafts are excluded from publishing. Check the item status and its fields before publishing the site.
Sources
- Framer, "Guide to Framer SEO optimization features", 15 September 2026
- Framer, "Using pages", 15 September 2026
- Framer Academy, "Create one reusable page for every CMS item", 15 September 2026
- Framer, "How to update page titles, descriptions, and social images", 15 September 2026
- Framer, "CollectionItem", 16 October 2026
Check how a page reads to answer engines. Open the GEO score analyzer