Heading
Contact UsThe CMS problem almost never shows up where people are looking for it. It shows up months after launch. For example, when a company already has numerous blog posts and several people are publishing them. Suddenly during this website phase, someone from the marketing team tries to filter case studies by industry and product both and discovers the CMS does not support it.
These problems mostly start during the initial website planning stage, when content structure is built with insufficient attention.
One primary reason behind this is that the CMS tutorials on a basic level only inform how to create collections and publish content. Such limited services are not enough for growing business as they have increased requirements such as:
- need to manage multiple content types
- establish relationships between them
- ensure their website can scale as the business grows
Growing businesses should also consider how different content types will connect, how teams will manage them, and whether the structure can support these future requirements.
Summary
- Plan your CMS before building: Decide what content your website needs, how it should be organised, and how different content types connect to avoid expensive changes later.
- Choose collections based on your website's needs: A simple website may need only a few collections, while a growing B2B website may need more to manage different types of content.
- Understand Webflow's limits: CMS plans allow up to five reference fields per collection, while Business plans allow ten. Plan how your content connects to avoid reaching these limits.
- Keep shared information in one place: Use separate collections for industries, categories or tags that appear across different content types. This keeps information consistent and makes filtering easier.
- Prepare for future growth: Plan your website URLs, content filters and publishing responsibilities early. If your requirements exceed Webflow's capabilities, consider connecting it to an external content system.
What Is a Content Model, and Why Does it Matter?
A content model defines the types of content a website contains. It also decides how each type of such content is structured, and how they relate to one another.
For example, a B2B website may have separate content types for case studies, blog posts and industries. Each type has specific fields. A case study might include a client name, industry, business challenge, solution and results. Planning these structures before designing CMS templates helps ensure the website can manage and display content consistently.

A well-planned content model makes content management easier. Editors can publish updates, organize information and maintain consistent page layouts. They do it without repeatedly involving developers. Poorly structured models make future changes more complicated. Even a simple request, such as adding a new content filter, may require changes to existing collections and page templates.
Begin by identifying your website's content requirements in two steps:
- Identify recurring content types. List the categories of content your website will regularly publish, such as blog posts, case studies, services and team profiles.
- Define content fields and relationships. Identify the information each content type requires and where different types share the same information. For example, if case studies, testimonials and team profiles all need to reference an industry, consider creating a shared Industry collection.
This allows editors to select an existing industry, such as Financial Services, instead of entering it manually in multiple places.

Our Webflow project work shows how different content models hold up at different sizes.
How Many Webflow CMS Collections Does Your Website Need?
There is no fixed number of Webflow CMS collections a website needs. A simple marketing website may require only a few collections, while a growing B2B website may need more. The right number depends on the types of content, their usage and the relationships between them.
For example, a B2B software company may need collections for products, industries, partners, certifications, testimonials and case studies. However, not every content type requires a separate collection.

Content relationships also matter more than volume alone. A website with hundreds of blog posts may have a simple structure. In contrast, fewer case studies may require more complex relationships across products, industries, services and customer outcomes.

To plan your CMS structure:
- List all content types.
- Identify which ones need dedicated pages.
- Determine shared information and content relationships.
- Define the required collections and fields before development.
Reference vs Multi-Reference Fields: How they Work and What to Consider
A reference field links a CMS item to a single item in another collection, such as a case study to its primary industry. A multi-reference field links it to multiple items, such as a case study to several related services.

Choose one reference field when an item needs one related value, and a multi-reference field when it needs several.
The type of reference field determines how content is connected, displayed and filtered. For example, visitors may filter case studies by one or multiple industries. Filtering by multiple industries may require extra configuration or custom functionality, depending on how it needs to work.

These requirements should be defined before building CMS templates. Our web design scope work usually settles this during planning, not mid-build.
Understanding Webflow's Reference-Field Limits
Webflow limits how many reference and multi-reference fields a CMS collection can have. The answer is five on CMS plans and ten on Business plans.
These limits can become restrictive for complex B2B websites. For example, a product collection might need to connect to use cases, industries, team members, certifications, partners, resources, testimonials, case studies and related services. That's already nine reference fields, leaving room for only one more on a Business plan.

Websites with many interconnected content types can quickly reach these limits, even on higher-tier plans. Enterprise plans offer greater flexibility, including support for up to 1,000 items per multi-reference field.
When you hit the limit, there are three real options:
- Merge two relationships into one collection where they're conceptually close. industries and sectors are often the same field pretending to be two.
- Use appropriate field types. Consider option fields for fixed values that do not need separate CMS records or relationships.
- Evaluate external data management. If requirements exceed the CMS's capabilities, consider whether a separate data source or a different architecture is appropriate.
When Should Categories and Tags Have Separate CMS Collections?
Treat categories, tags and industries as collections, not text fields, the moment more than one content type needs to share them. For example, if blog posts, case studies and team profiles all reference Healthcare, a shared Industry collection ensure editors to use the same category name across the website.
Without standardised values, editors may enter variations such as "Healthcare," "healthcare" and "Health Care." These inconsistencies can complicate filtering and content management.

Inconsistent category names are easier to prevent than to correct after a website has accumulated substantial content. They can lead to incomplete filtering results, duplicated categories and additional editorial work. Correcting these issues may require standardising existing values and updating how content is organised.
The Trade-Off: Better Content Organisation vs More Editorial Work
Separate taxonomy collections can improve consistency and support relationships between content types. However, they also make the CMS more complex. Editors may need to select values from several reference fields whenever they create a new item.
The goal is to introduce only the collections and relationships needed for the website's content, filtering and publishing requirements.
How to Plan CMS Collection Names, URLs and SEO Settings
Use consistent collection names to simplify content management. For example, name a collection “Case Studies” and its singular item “Case Study.” Clear naming helps developers and editors identify content types.
Define CMS URL structures before development. For example, use /case-studies/ for case study pages. Changing collection URLs after publication may require updating internal links, reviewing references, and implementing 301 redirects to preserve SEO value.
Configure CMS templates with dynamic SEO fields for page titles, meta descriptions, and Open Graph information. Connect these settings to CMS fields so each blog post or case study can have unique metadata. For more on how this sits alongside the rest of the build, our web design and development work covers it in context.
How Nested Collections and Content Volume Affect Website Architecture
Nested collections determine how related content appears on a website. Content volume however affects how easily it can be managed. Both influence website structure as content grows.
For example, a case study page may display related resources using Webflow's Nested Collection Lists. Even then, not every content relationship requires nesting.

Large collections can also become harder to manage. As item counts grow, editors may experience a slower CMS interface. Published pages in such a case still perform well.
For larger collections, plan pagination and filtering early. This makes content easier to browse and reduces the need to redesign the browsing experience later. Webflow's CMS documentation explains the available collection list settings.
What a Mid-project Restructure Costs
The cost of restructuring a Webflow CMS depends on the amount of existing content, content relationships and website templates that need changes. Larger restructures generally require more development work, content migration and testing.
For example, converting text-based industry categories into a shared CMS collection may involve:
- Reviewing and standardising existing industry names.
- Creating a new Industry collection.
- Connecting relevant content through reference fields.
- Updating CMS templates and filtering logic.
- Testing the changes before publication.

If existing page URLs change, the migration plan should include 301 redirects. These help preserve access to the affected pages.
Before approving a CMS restructure, assess the development effort and content migration needs. Also consider the impact on existing URLs. Use this assessment to agree on the project's scope, budget and timeline.
The Four Architectures Compared
|
Approach |
Suited to |
Reference fields used |
Content reuse and filtering |
Cost / limit |
|
Flat, single-collection |
Small teams, simple content, one editor |
Minimal, mostly none |
Basic, no cross-type filtering |
Cheap to build, breaks as content diversifies |
|
Relational, multi-reference |
Growth-stage B2B with shared taxonomies |
Heavy, approaches the per-collection limit |
Strong, supports layered filtering |
Hits the ten-reference ceiling fastest |
|
Hybrid-decoupled |
150+ person companies with one large catalogue |
Moderate, split across Webflow and external data |
Strong within Webflow, full control externally |
Needs two systems kept in sync |
|
External headless CMS with Webflow front end |
Enterprise, multi-team, compliance-heavy |
Managed outside Webflow entirely |
Highest reuse across channels |
Most setup time and ongoing governance |
When Should Businesses Consider an External CMS or Hybrid Architecture?
Businesses should consider an external CMS or hybrid architecture when their content, data relationships or publishing requirements become difficult to manage within Webflow CMS.
For example, a business with a large product catalog may need to manage the following:
- regional pricing
- technical specifications
- certifications
- partner information and more

An external product database may be better suited to handling this information. Businesses with strict approval or compliance processes may also need more advanced publishing controls.
Complex content relationships can also influence the decision. A website may need to connect organizations, departments, teams and projects. Businesses should assess whether Webflow's CMS Collections can support these relationships.

A hybrid approach does not mean replacing Webflow entirely. Suitable content like marketing pages can remain in Webflow CMS. Complex product data or specialised information can be managed externally and displayed through Webflow's Collection Pages,
Before choosing an architecture, involve the teams responsible for managing the content and data. This ensures the website supports current requirements and future growth.
Deciding who Decides
The least technical part of this is often the part that goes wrong: nobody is named as the owner of the content model. The requirement examples include but are not limited to:
- marketing wants a new attribute for filtering
- product wants specifications kept in sync with an internal database
- legal wants an approval gate
Whoever's paying for the build wants to know it won't need rebuilding after several months. Each has a legitimate stake in the same structural decision, and none individually has the authority to decide it.
Before signing off the site-map, considering these points :
- Assign a person responsible for the content model before development begins.
- This person should coordinate decisions about new CMS collections, content fields and relationships.
- Maintain a brief record explaining the purpose of each collection, the information it contains and how it connects to other content types.
- This documentation will help future developers and content editors understand the existing structure.

Final Verdict
- If you're a small team with one editor and a straightforward site, three to six flat collections will serve you for years.
- For companies with shared taxonomies across products, case studies and team content, plan the relational model and the reference-field budget before build starts. The reason is that Webflow CMS architecture decisions get expensive to undo later.
- If you're managing large catalogues or genuine compliance requirements, Webflow CMS alone probably isn't the full answer, and a hybrid approach is the honest one.
- Settling this before design starts is cheaper than any restructure later.
See more of our thinking on the Spoke blog, shaped by actual Webflow build work rather than theory. A webflow development agency UK can usually tell within an hour which of these situations you're in. If you'd rather talk it through than guess, get in touch directly.
FAQs
Q: How many collections should a typical marketing site have?
A: Most marketing sites with one editor need three to six collections blog, case studies, team, and perhaps locations or services. That number rises quickly once content types share taxonomies or relate to each other in several ways. Count relationships, not just content types, before settling on a figure.
Q: Should I create a separate collection for categories or use a plain text field?
A: Use a collection the moment more than one content type shares the same category, tag or industry value. A text field invites inconsistent spelling across editors, which quietly breaks filtering. The cost of a dedicated collection is one more dropdown for editors, which is cheaper than fixing filtering later.
Q: What happens if I exceed the reference field limit per collection?
A: You can't add an eleventh reference field on a Business plan, or a sixth on CMS. Teams usually merge two conceptually similar relationships, move one relationship to a plain option field, or conclude the content needs an external data source. Decide which approach before you're mid-build, not during it.
Q: Can I restructure my collections after content is already published?
A: Yes, but it means rebuilding the collection, remapping every reference and setting a 301 redirect for every URL that changes. It's rarely a quick fix once hundreds of items exist. Cost it honestly before agreeing to a timeline with whoever requested the change.
Q: How many items can a collection hold before performance suffers?
A: Collections past roughly a thousand items start to slow down inside the Designer's CMS interface, though the published site typically performs fine with proper pagination. Plan filtering and pagination before a collection approaches that size, not after editors start noticing the lag.
Q: Can I filter by multi-reference fields on the front end?
A: Yes, but the filter logic needs to account for whether an item should match any of the selected values or all of them, and that decision changes how the filter is built. Decide this during template planning rather than after editors start tagging content inconsistently.
Q: What's the right number of fields per collection for a scalable site?
A: There's no fixed number, but the reference field count matters more than the total field count, since it's capped at ten on Business plans and five on CMS plans. Build only the relationships your filtering and reporting genuinely need, and leave room under that ceiling for growth.
Let’s Connect.
Have a project in mind or want to explore how we can help your business grow?
Heading
Contact UsHeading
Contact UsHeading
Contact UsGet a callback from Saransh





