Webflow CMS: how to structure it

The Webflow CMS stores your repeating content, such as blog posts, case studies, events, people and FAQs, as collections: each one a set of items with the same fields, shown through one template page and as many lists as you like. Structure it around what your team adds each month, not around pages. Give each type of content one collection, store anything shared once and link to it, and keep categories few. When we rebuilt Smokeball’s US site, 11 exports of the old site became 1,182 items in 13 collections, and 30 blog categories became 11.

What belongs in the CMS, and what doesn’t

The CMS is for content that repeats and grows. One-off pages are better built as static pages from your components, where the team can arrange sections freely.

Content	Where it goes	Why
Blog posts, news, resources	A collection	Added every month, all on one template
Case studies, testimonials	A collection	Shown on many pages, filtered by industry or size
Events, webinars, speakers	Collections, linked to each other	A speaker can appear at many events
FAQs	A collection	One answer can appear on every page it belongs to
Authors, team members	A collection	A bio written once appears on every post
Home, pricing, campaign pages	Static pages	Each one is different, built from components

How we structure a marketing site’s CMS

1. Start from what the team adds

List what your marketing team publishes in a normal month, and who does it. That list, not the sitemap, decides your collections. A collection nobody adds to is extra upkeep, and content added every week that lives on static pages becomes a design job every time.

2. One collection per type of thing

Merge collections that overlap. Smokeball’s old site had three webinar collections; on the new site they became one, so every webinar has the same fields and appears in the same lists. Fewer collections also make a site easier for a new team member to learn.

3. Store shared things once, and reference them

Reference fields link an item to another collection, and multi-reference fields link it to several. Use them for anything that would otherwise be typed twice:

• People. On Altus’s site, authors are a collection of their own, and each post links to its author, so a bio is written once. Smokeball’s webinar presenters became a reusable set of 59 speaker profiles.
• FAQs. Fresh Clinics stores more than 90 FAQs once in the CMS and shows each on the pages it belongs to. Endeavour Lotteries moved its FAQs into the CMS in 2026, so one answer can appear on many pages.
• Testimonials. Smokeball’s Wall of Love runs from its own collection, so adding a review is a CMS entry, not a design job.

4. Keep categories few

Every category is a page, a filter and a decision for whoever writes the next post. Smokeball’s 30 blog categories became 11. If two categories always appear together, merge them; if one has three posts, retire it.

5. Plan the URLs before launch

Each collection has its own address, such as /blog, and each item’s slug follows it. Choose both before you import anything, and keep them close to your old site’s addresses if you’re moving. A URL that changes later needs a redirect, so it’s cheaper to decide once. We cover the move itself in WordPress to Webflow migration.

6. Give every item its search fields

Add fields for an SEO title, a meta description and a social image, then bind them in the template’s page settings, so each post sets its own. Our Webflow SEO guide covers the rest of the search setup.

7. Add fields that save the team work

A few small fields make a CMS much easier to run. On Smokeball’s Spark conference site, each session has a date and time, so the agenda sorts itself as sessions are added, and FAQs have a field that sets their order. Its testimonials have a switch to choose which are featured. Ask what the team would otherwise have to ask a developer for, and make it a field.

Smokeball’s US case studies. Each is a CMS item, and the filters come from its fields, so a new case study appears in the right places as soon as it’s published.

8. Plan for markets and languages

If you sell in more than one country or language, decide early whether each market shares a collection or has its own. With Webflow Localization, CMS items can be translated within one site; see Webflow Localization for how we set up Altus’s German version.

The limits worth knowing

Webflow’s Premium site plan, the one most marketing sites need, includes 20,000 CMS items and up to 40 collections, after Webflow’s May 2026 plan update (Webflow). A collection can have up to 60 fields (Webflow). On a page, Webflow shows up to 40 collection lists, nested lists included, and each list shows up to 100 items by default (Webflow). These figures were read on 26 October 2026.

For most marketing sites that’s plenty of room: Smokeball’s US site, with years of posts, case studies and resources, uses 1,182 items in 13 collections. Our Webflow pricing guide compares the plans.

Once the structure is right, your team can publish without waiting on anyone; see publishing pages without a developer. Bulk changes to CMS content can also be made with an AI assistant connected through Webflow’s MCP server.

Questions we get asked

Is Webflow a CMS?

Yes. Webflow is a visual website builder with a CMS built in: you design templates and lists visually, and your team adds posts, case studies, events and other content as CMS items through the Webflow editor. Hosting is included, so there’s nothing separate to install or update.

Is Webflow the best CMS?

For a marketing team that builds and publishes pages itself, it’s the one we recommend: the CMS, visual builder and hosting work together. If your site is changed mostly as code, by developers or an AI assistant, a headless CMS with Astro can suit better (Astro web development).

What are the limitations of Webflow as a CMS?

Each plan sets how many items and collections you can have: Premium includes 20,000 items in up to 40 collections. Each collection has up to 60 fields, and a list shows 100 items by default. Planning collections around your content keeps most marketing sites well inside those limits.

Can we move our existing content into the Webflow CMS?

Yes. Collections can be filled by importing a CSV file, or through Webflow’s API for larger moves. Plan the structure first, then map each old field to a new one. Smokeball’s US site came across from 11 exports, checked in four passes against the originals.

If you’re planning a Webflow site, or your CMS has grown messy, see our Webflow and custom development service, or tell us about your site.

This guide is part of Webflow for marketing teams, which brings together everything we’ve written on choosing, building and running a Webflow site.

Sources

• Webflow, Updated pricing and simplified plans for May 2026
• Webflow, Dynamic content limits
• Webflow, Managing CMS collections and items
• Webflow, Plans and pricing