Framer CMS: The Complete Guide for Blogs & Portfolios
The Framer CMS is the content database built into Framer: collections hold items, fields define each item, and one detail page renders every item. Framer CMS: The Complete Guide for Blogs & Portfolios is Pavlo Zhydkykh's walk-through of content modelling, plan limits and CMS SEO, drawn from real client builds.
Pavlo ZhydkykhUpdated · 6 min read
Short answer
The Framer CMS is the quiet workhorse behind every serious blog and portfolio on the platform. In this Framer CMS guide I break down how collections, fields and dynamic pages actually work, what the plan limits mean for your content, and the habits that keep a CMS-driven site fast and easy to rank. Everything here comes from shipping real client projects - not from the marketing page.
Key takeaways
- The Framer CMS separates content from page design: collections contain items, and fields define the information stored in every item.[2]
- A CMS detail page reuses one layout for every item, so a new blog post or case study is a content task, not a design session.[2]
- Framer CMS pages can carry unique JSON-LD structured data per page through custom code that references CMS fields.[3]
- Titles and descriptions can be set as site defaults and overridden per page or per CMS item, so every post ships with correct metadata.[4]
- Pavlo Zhydkykh runs client blogs and portfolios on the Framer CMS; adding a case study to a well-modelled collection takes about fifteen minutes.
What is Framer CMS?
The Framer CMS is a structured content layer inside a Framer project: a collection groups one type of content, fields set what every item contains, and a CMS detail page reuses one layout for every item at a URL such as /blog/post-slug. Editors change content; the design stays untouched.
Wikipedia: Content management system
“I model every collection around the content, not the current design: one fact per field, so a redesign never means rewriting posts.”
Last checked · 6 min read
What Is the Framer CMS?
The Framer CMS is a content database that lives inside your Framer project. Instead of designing every blog post or case study as a separate page, you create a collection - Blog, Projects, Testimonials - and Framer generates a page for every item in the collection from a single dynamic template. Change the template once and every article updates instantly.
In practice, this is the feature that turns Framer from a landing-page tool into a platform you can run a real content operation on. My own site runs its blog and portfolio from two collections, and on client projects the CMS is usually where the site quietly earns its keep for years after launch.
Design the template once, then let the CMS do the shipping - that is the entire trick to publishing consistently.
Collections, Fields and Dynamic Pages Explained
Three concepts do all the work, and understanding the three properly will save you a rebuild later. Collections are content types - one for blog posts, one for portfolio projects. Fields define what every item contains. Dynamic pages are templates connected to a collection, and each item gets its own URL such as /blog/your-slug.
The field types you will actually use:
- Plain text - headlines, meta descriptions, author names.
- Rich text - the article body: headings, lists, quotes, images and embeds.
- Image - thumbnails and heroes, each with its own alt text.
- Date, link, number and toggle - publish dates, project URLs, ratings and flags.
- Reference - connect items across collections, for example a post to an author or a category.
A habit worth stealing: model your collection around the content, not the current design. If you bake facts like read time into sentences, you will regret it the day you redesign. Keep every fact in its own field and let the template decide how to present each fact.
Framer CMS Limits by Plan (2026)
CMS capacity is decided by your site's plan, and the plan is the first thing I check when scoping a content-heavy build. These are the limits on Framer's pricing page as of 23 October 2026, with the price per month on yearly billing and the month-to-month price in brackets:
| Plan | Price per month | CMS collections | CMS items | Best for |
|---|---|---|---|---|
| Free | $0 | 10 | Limited | Trying Framer - no custom domain |
| Basic | $10 ($15) | 2 | 1,000 | Personal sites with a single blog |
| Pro | $30 ($45) | 10 (40 with add-ons) | 2,500 (40,000 with add-ons) | Marketing sites and content teams |
| Enterprise | Custom | Custom | Custom | Large organisations |
Two things worth knowing from real projects. First, the Basic plan's two collections sound tight, but a blog plus a portfolio fits exactly - which is what most freelancers need. Second, if you are planning thousands of items or programmatic landing pages, price the Pro add-ons in from the start. I break the full cost picture down in my guide to how much a Framer website costs in 2026.
How to Set Up a Blog with the Framer CMS
Here is the exact sequence I use on client builds:
- Create a Blog collection and add fields: headline, meta description, slug, date, author, thumbnail, intro text and a rich text field for the body.
- Add a separate FAQ rich text field if you plan to use accordion FAQs - keeping FAQs out of the body makes the template cleaner.
- Create the dynamic detail page, connect the page to the collection, and design the article layout once.
- Map the page title and meta description to CMS fields, so every post ships with correct metadata automatically.
- Build the listing page with a CMS-connected grid, sorted by date.
- Write two or three real posts before you finalise the design - real content exposes layout problems that placeholder text hides.
- Publish, then submit your sitemap in Google Search Console.
If you prefer to watch the setup done on screen, Framer University's crash course is the best walkthrough I have found: https://www.youtube.com/watch?v=cHJPudv5dbY - Learn the Framer CMS in 26 minutes.
Building a Portfolio on the Framer CMS
Portfolios benefit from the CMS even more than blogs, because case studies share a rigid structure. One Projects collection with fields for client, sector, services, year, cover image, gallery and a results paragraph will carry you for years. Adding a new case study becomes a fifteen-minute content task rather than a design session - which is exactly why my own works page is CMS-driven.
The detail that separates a premium portfolio from a template-looking one is the write-up. A rich text field lets every case study tell a story - brief, approach, outcome - instead of dumping screenshots and hoping screenshots speak for themselves.
Framer CMS SEO: Making Dynamic Pages Rank
CMS pages rank the same way any page does - the CMS simply makes doing it consistently much easier. Map titles and meta descriptions to fields, keep slugs short and keyword-led, and give every image real alt text. Because Framer renders CMS pages as static HTML on a CDN, Core Web Vitals stay strong as the blog grows.
Two mistakes I fix constantly on audits: duplicate or default slugs, and article bodies that are one wall of text with no headings. Both are content problems, not platform problems. My Framer SEO guide covers the full checklist, from structured data to sitemap submission.
Where the Framer CMS Falls Short
Honesty matters more than cheerleading, so here is where the CMS will frustrate you:
- Editorial workflow is simple - there are no approval chains, so larger content teams need process discipline outside the tool.
- Item limits are real: heavy programmatic SEO needs Pro with add-ons, and truly huge content libraries still belong on a headless CMS.
- Writers coming from Notion or Google Docs will miss comments and suggestion mode in the editor.
- Complex many-to-many content relationships take careful planning compared with a proper database.
None of these has ever stopped a marketing site or portfolio I have built. But if your project is closer to a publication with a five-person editorial team, weigh your options in my Framer vs Webflow comparison before committing.
Want an SEO-First Framer Website?
Pavlo Zhydkykh builds fast, SEO-first Framer websites with clean CMS architecture - blogs, portfolios and marketing sites that stay easy to update long after launch. If you are planning a CMS-driven Framer project, get in touch and tell him what you are building.
If you need this built
A Framer landing page from Pavlo starts at $1,200 (1 to 2 weeks), a multi-page site at $3,000 (2 to 4 weeks). SEO and GEO basics are included.
See Framer developmentFrequently asked questions
How many CMS items does a typical blog need?
Far fewer than people budget for. A weekly publishing schedule is roughly 52 items a year, so the Basic plan's 1,000 items covers years of content. You will usually outgrow the two-collection limit before the item limit.
Can I import existing content into the Framer CMS?
Yes - Framer supports CSV import into a collection, and it maps columns to fields during the import. For rich text bodies, expect to do some manual clean-up afterwards, especially around images and embeds.
Does the Framer CMS support categories and tags?
Yes, through option fields for simple cases and reference fields for proper taxonomies. A Categories collection referenced from your Blog collection gives you filterable category pages without any code.
Is the Framer CMS good for SEO?
Very. CMS pages are rendered as static HTML and served from a CDN, titles and meta descriptions map to fields, and slugs are fully controllable. The platform will not hold you back - thin content will.
Can a client edit CMS content without breaking the design?
Yes - that is one of the strongest reasons to use the CMS. Framer lists content editor seats at $10 per editor per month, and editors can update items and use on-page editing without touching the layout or design.
Free tool Does ChatGPT recommend you? Free report in 48 hours · 5 AI engines
Checklist
7 Framer CMS mistakes Pavlo fixes on audits
Most CMS problems are structural, not platform problems. These are the ones Pavlo Zhydkykh finds most often on client sites.
1. Default or duplicate slugs
URLs like /blog/article-14 tell neither readers nor Google what the page is. Pavlo sets slugs short, keyword-led and by hand.
2. Facts baked into sentences
A read time or client name typed into the body cannot be restyled later. Every fact belongs in a separate field.
3. A collection shaped like the layout
Fields named after today's design break at the next redesign. Fields named after the content survive.
4. Blank meta fields
Titles and descriptions not mapped to CMS fields leave every item with the site default.
5. Images without alt text
Every image field carries a description, for search engines and screen readers alike.
6. One wall of text
Article bodies without headings are hard to scan for readers and for search engines. The rich text field supports proper headings.
7. FAQ inside the body
A separate FAQ field keeps accordion questions out of the article text and the template cleaner.
Fit check
Is the Framer CMS
right for you?
A good fit if
- A blog, a portfolio or a case study library on a marketing site.
- A small team whose editors update content without touching the layout, in the CMS or with on-page editing.
- A content library that fits the item limits of a Framer plan, which covers years of weekly posts.
- You want Pavlo to model the collections once so the site stays easy to update for years.
Not the right fit if
- A publication with a five-person editorial team that needs approval chains, comments and suggestion mode.
- Heavy programmatic SEO with huge item counts: that needs Pro add-ons, and the largest libraries belong in a headless CMS.
- Complex many-to-many content relationships that need a proper database.
Compared
Pages built one by one vs a CMS collection
Why Pavlo Zhydkykh moves repeating content into collections on every Framer build.
| Criterion | Pages designed one by one | Framer CMS collection |
|---|---|---|
| New post or case study | A design session per page | A content task: fill in the fields |
| Redesign | Every page edited by hand | One template change updates every item |
| SEO fields | Set page by page, often forgotten | Mapped to CMS fields once |
| Structured data | Written by hand for each page | Generated per item from CMS variables |
| Who edits | A designer on the canvas | Editors in the CMS or on the live page |
| Consistency | Drifts with every new page | Every item follows one layout |
How it works
A portfolio on the Framer CMS, step by step
How Pavlo Zhydkykh sets up a case study collection that carries a portfolio for years.
| # | Step | When | What happens | You get |
|---|---|---|---|---|
| 01 | Create a Projects collection | First | One collection for case studies, separate from the blog. | A home for every project |
| 02 | Add the fields | Then | Client, sector, services, year, cover image, gallery and a results paragraph. | A content model that lasts |
| 03 | Design the detail page | Then | One case study layout with a rich text story: brief, approach, outcome. | Every case study in one layout |
| 04 | Build the works page | Then | A CMS-connected grid of project cards. | An index that updates on publish |
| 05 | Map titles and alt text | Before launch | Meta title and description bound to fields, alt text on every image. | Unique metadata per project |
| 06 | Add the next project | After launch | A new case study goes in as content, in about fifteen minutes. | A portfolio that keeps growing |
In their words
The Framer CMS, by the docs
and by Pavlo's clients
Word for word, with the source linked: research, official documentation and the people Pavlo Zhydkykh has worked for.
“The Framer CMS separates your content from the page design.”
“The CMS contains collections, each collection contains items, and fields define the information stored in every item.”
“Traditional (or coupled) CMSs integrate content authoring, storage, and presentation into a single application, with content typically published directly to a website managed by the CMS.”
“It was an absolute pleasure working with Pavlo. He's very professional and responds immediately to all questions and/or feedback. The quality of work he delivered was AMAZING.”
“One of the best contractors I have worked with. Really thoughtful about communication. Went above and beyond in delivering the results that our team needs. Would 100% hire again for our projects.”
“The collaboration went smoothly and the work was delivered as agreed. Communication was timely, and the final result aligned with the initial expectations. Overall, a very positive and rewarding experience!”
About the author
Pavlo Zhydkykh
Pavlo Zhydkykh is a web designer and developer in Eastern Europe who has built websites for AI, fintech and B2B startups since 2016, designing and building each project himself on Framer or Astro + Sanity. Clients include MStudio Asia, Silicon Data, Inturai, Accolade Pro, NimbleStax and Sancts.
- Top Rated on Upwork
- 100% Job Success
- 10 years since 2016
- 50+ sites shipped
- 90+ PageSpeed at launch
About Pavlo LinkedInUpworkContra Privacy policy
Page reviewed by Pavlo Zhydkykh · Updated
In this topic
Framer guides
9 articles
- 01 Framer SEO Guide 2026: Rank Your Framer Site 7 min
- 02 Core Web Vitals on Framer: How to Hit 90+ in 2026 5 min
- 03 Framer CMS: The Complete Guide for Blogs & Portfolios You are here
- 04 How to Add a Blog to Your Framer Website (2026 Guide) Next
- 05 Framer Animations: A Practical Guide for Real Sites 5 min
- 06 Can Framer Handle Custom Code and WebGL? (Yes! Here's How) 5 min
- 07 Is Framer Ready for E-commerce in 2026? 5 min
- 08 10 Framer Mistakes That Quietly Kill Your Conversions 5 min
- 09 Framer Website Redesign: Rebuild or Patch? (2026 Guide) 5 min