FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

Webflow CMS: what it can do and how to plan collections

What the Webflow CMS can do: field types, references, limits and template pages, plus a simple way to plan collections so your site stays easy to grow.

By Abdul QuadirUpdated 2026-11-1411 min read
TL;DR
  • The Webflow CMS stores repeatable content in collections, and each collection gets one template page that every item uses.
  • Fields cover text, rich text, images, video links, dates, numbers, switches, options and references to other collections.
  • Reference and multi-reference fields let you connect content, like case studies to industries or posts to authors.
  • Plan collections on paper first: content types, fields, links between them and who edits what.
  • Plan limits on items and collections depend on your Webflow site plan, so check them before you build a big content library.

What the Webflow CMS is, in short

The Webflow CMS is the part of Webflow that stores repeatable content, like blog posts, case studies, jobs or team members, in structured collections. You design one template page for each collection, and every item you add gets its own page using that layout. Editors add and change items without touching the design.

It is visual, so designers can bind fields to elements directly on the canvas. And because it lives inside the same tool as your site, there is no separate theme or plugin to keep updated.

Planning it well is the difference between a site your team loves to update and one they avoid. The rest of this guide shows how we plan collections on real projects.

You do not need to be technical to plan a CMS. You need to know your content: what you publish, how often, who writes it and how readers find it. A developer turns that into collections and fields. The thinking is yours.

Collections, items and template pages

Three words cover most of the CMS:

  • Collection. A content type, like "Blog posts". You define its fields once.
  • Item. One entry in a collection, like a single blog post.
  • Template page. The layout every item in the collection uses. Change it once and every item updates.

You can also show items anywhere on the site with a collection list. A home page might show the three latest posts. A service page might show case studies for that service only. Collection lists can be filtered, sorted and limited, and they support pagination when you have many items.

Field types you can use

FieldGood for
Plain textTitles, short labels, SEO titles
Rich textArticle bodies with headings, lists, links and images
Image and multi-imageThumbnails, hero images, galleries
Video linkEmbedded videos from common hosts
Link, email, phoneButtons, contact details
NumberPrices, results, sort order
Date and timePublish dates, event dates
SwitchFeatured on or off, show or hide
OptionA fixed list, like "Guide" or "News"
ColorA brand colour per item, like a client accent
FilePDFs and downloads
Reference and multi-referenceLinks to items in other collections

Every field can have help text. Use it. A one line hint like "Max 60 characters, shows on Google" saves editors from guessing.

Pick the narrowest field that fits. If a value can only be one of four things, use an option field, not plain text. If something should link to another item, use a reference, not a pasted URL. Narrow fields keep data clean, and clean data makes filters and lists work.

References: how collections talk to each other

Reference fields are where the Webflow CMS gets powerful. A reference links one item to one item in another collection. A multi-reference links one item to many.

On the template page, you can pull fields from a referenced item straight into the layout. A blog post can show its author's name, photo and bio, all stored once in the authors collection. Update the bio once and every post shows the new version.

Some examples from real sites we have built:

  • A blog post references one author. The author page then lists every post they wrote.
  • A case study multi-references several services and one industry. Each service page shows only its own case studies.
  • A job references a team and a location, so the careers page can filter by both.

The rule of thumb: if you type the same thing into many items, such as an author name or an industry, it probably wants to be its own collection with a reference. That keeps spelling consistent and gives you a page for it for free.

How to plan collections, step by step

  1. List your content types. Write down everything that repeats: posts, case studies, testimonials, FAQs, team, jobs, logos, events.
  2. Decide which need their own page. Posts and case studies do. Logos and testimonials usually do not, but they can still be collections shown in lists.
  3. List the fields for each. Title, slug, summary, main image, body, SEO title, SEO description, Open Graph image, plus anything specific.
  4. Draw the links. Which collection references which? Keep it simple. Two or three levels is plenty.
  5. Mark required fields. A post without a summary breaks the card grid. Make it required.
  6. Write help text for every field an editor will touch.
  7. Add real sample items with long and short content, then check every template and list.

We do this in a simple sheet with the client before we touch Webflow. It takes an hour and it shapes the whole build.

Leave room to grow, but do not build for a future you are not sure about. It is easy to add a field later. It is harder to explain to editors why there are twelve empty fields on every post that nobody uses.

Example: a typical B2B marketing site

Here is a setup we use often for SaaS and service businesses:

CollectionOwn page?Key references
Blog postsYesAuthor, category
AuthorsYesNone
CategoriesYesNone
Case studiesYesIndustry, services
IndustriesYesNone
TestimonialsNoCase study
FAQsNoOption field for topic
JobsYesTeam

From eight collections, the site gets dozens of pages that update themselves: category archives, author pages, industry pages with their case studies and service pages with matching proof.

Notice that testimonials and FAQs do not get their own pages. They live in the CMS so they can be reused across the site, but nobody needs a page for a single quote. That is a simple test for every collection: does one item deserve its own URL? If not, turn off the template page or keep it out of the sitemap.

Limits to know before you build

The Webflow CMS is a great fit for most marketing sites. It is good to know where its edges are before you commit:

  • Item and collection limits depend on your site plan. Check Webflow's current plan page if you expect thousands of items.
  • Collection lists show a limited number of items at once, with pagination for the rest. Very long lists need some planning.
  • Nested lists have limits on how deep and how many items they show.
  • Rich text is flexible but not a page builder. For complex layouts inside posts, use custom elements or components with care.
  • Large imports work through CSV or the API, but relationships between collections need to be mapped carefully.

When a site needs very large content libraries or content shared across many channels, a headless CMS like Sanity with Astro can be a better fit. We compare the two in Webflow vs Astro and cover the setup on our Astro and Sanity page.

SEO inside the CMS

Every collection with its own page should have SEO fields. We add these by default:

  • SEO title, bound to the page title setting on the template.
  • Meta description, bound to the description setting.
  • Open Graph image, bound to an image field.
  • Schema markup in the template custom code, with fields inserted so each item gets its own JSON-LD.

Fall back to the item name and summary when SEO fields are empty, so nothing ships blank. More checks like this are in our Webflow SEO checklist.

Mistakes we see in inherited projects

  • Static pages for content that repeats. Ten case studies built by hand instead of one template.
  • Free text where an option or reference belongs. "SaaS", "Saas" and "SAAS" all become separate filters.
  • One giant collection with a "type" field trying to hold posts, news, events and jobs.
  • No help text, so editors guess what goes in each field.
  • Images with no size guidance, so a 6MB photo ends up on the blog grid.

Most of these can be fixed without a rebuild. It usually means adding the right collections, moving content across and updating the templates.

The fix order matters. Create the new collections first, move content across, update templates and lists, then remove the old static pages and add redirects from their URLs. Doing it in that order means nothing breaks for visitors while the work happens.

How editors use the CMS day to day

A CMS is only as good as the editing experience. Most of your team will never open the Designer. They will use the Editor or the CMS panel to add a post, fix a typo or swap an image.

  • Adding an item is a form. Fill in the fields, upload an image, save as draft or publish.
  • Editing on the page works in the Editor. Click the text on the live layout and change it.
  • Scheduling lets you set a publish time, so a post can go live on launch day without anyone at a desk.
  • Roles let you decide who can publish and who can only draft, depending on your plan.

Good field names, help text and required fields make this feel easy. Bad ones make editors nervous, and nervous editors stop updating the site. That is why we spend real time on the editing side, not just the design side.

Moving content into the Webflow CMS

If you are coming from another platform, your content needs to move too. The usual steps:

  1. Export content from the old system, often as CSV or through its API.
  2. Clean it up: fix broken formatting, remove old shortcodes and decide which posts are worth keeping.
  3. Create the collections and fields in Webflow first, matching the plan.
  4. Import the main collections, then the ones that reference them, so links connect properly.
  5. Check images, slugs and rich text on a sample of items.
  6. Set up 301 redirects from old URLs to new ones.

Small libraries can be moved by hand. Hundreds of posts usually need a script and a careful check. We handle this as part of our WordPress to Webflow and Wix to Webflow migrations.

Getting help with your CMS

If you are planning a new site, our Webflow CMS service covers planning, building and importing content. If you have a site that has outgrown its first setup, we can restructure it as part of our Webflow development work, or step by step on the care plan.

Either way, start with the plan. A sheet of collections, fields and references is the most useful hour you will spend on a Webflow site.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Webflow CMS

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

A collection is a content type, like blog posts or case studies. You set its fields once, then add items. Each item can get its own page from a shared template.

It depends on the site plan. Webflow publishes the current limits on its pricing page, so check there before you plan a large library.

A field that links one item to several items in another collection, like a case study linked to three services.

Yes. You can import CSV files into a collection, or use the Webflow API for larger or repeated imports.

Yes. Editors can add and change items without touching the design, especially when fields have help text and required settings.

When you need very large content libraries, content shared across apps and channels, or complex editorial workflows. A headless CMS like Sanity can suit those cases better.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.