How We Structure Webflow CMS So SaaS Sites Scale to Thousands of Pages

Liana Pogonyi
Liana Pogonyi
Head of Operations
Webflow
Published
November 13, 2026
Last updated
November 13, 2026
Read time
7
​
No attention span?

Summarize this article with AI.

​
AI summary
A Webflow site can scale to thousands of pages if the CMS is planned before the design. Use connected collections with reference fields so shared content like customer logos is updated in one place, one CMS template per page type for programmatic SEO, and reusable components for campaign pages. Plan around Webflow's display limits, such as 100 items per Collection list.
On this page

A Webflow site can have thousands of pages without becoming difficult to manage. But that depends on how the CMS is structured.

We use a combination of connected CMS collections, reusable templates and components. This means adding page 300 doesn't require the same amount of work as building page 30 from scratch.

Most SaaS websites don't run into problems at launch. They run into them later.

Someone duplicates a static page to create a new landing page. A customer logo gets uploaded in four different places. The blog ends up with two category fields because nobody remembers the first one. A year later, changing your pricing means editing eleven pages, and nobody knows which version is correct.

We take over websites like this regularly, where the problem is usually not the design but the structure underneath it.

Here's how we approach Webflow CMS for SaaS websites that need to grow.

Where do you start: the design or the CMS?

The CMS. Before opening Figma, we map out what types of pages the website will need, both at launch and as the company grows.

For a SaaS company, we usually ask:

  • Which questions do buyers ask before booking a demo?
  • Which pages will the marketing team want to create themselves? Campaign pages, integrations, comparisons, locations?
  • What content appears in multiple places? Customer logos, testimonials, pricing, team members?
  • Which page types will need dozens of variations?

The answers help us plan the collections and how they connect. Then we design the website around that structure.

It's much easier to get this right before development than to rebuild the CMS once the website has grown.

Which collections does a SaaS website need?

Most of our SaaS projects start with a similar set of collections. Some have their own pages, while others store content that's reused across the website.

CollectionOwn page?What it holdsUsed in
Blog postsYesArticles, guides, comparisonsBlog, resource hubs
CategoriesOptionalTopics for grouping postsBlog filters, category pages
AuthorsOptionalName, role, photo, bioBlog posts
Case studiesYesClient stories and resultsCase studies, industry pages
CustomersNoLogo, name, industryLogo strips, case studies
TestimonialsNoQuote, person, rolePages that need social proof
IntegrationsYesOne page per connected toolIntegrations directory
Industries / use casesYesPages for different audiencesNavigation, landing pages
LocationsYesPages for regions or citiesLocation pages
TeamNoName, role, photoAbout page

Not every website needs all of these. A startup might only need four collections at launch.

The important thing is to understand how they fit together. Adding a new collection later shouldn't mean rebuilding the pages around it.

Why use reference fields instead of typing things twice?

Because the same information shouldn't have to be updated in several places.

Webflow reference fields let you connect one CMS item to another. Multi-reference fields let you connect it to several items.

For example:

  • A case study can reference a customer and an industry.
  • An industry page can display all case studies connected to that industry.
  • A blog post can reference its author and categories.

This means you don't have to manually add the same information everywhere.

Update a customer's logo in the Customers collection, and the change can appear across all the pages that reference it.

It also makes adding content easier. Publish a new case study for a fintech client, and it can automatically appear on the fintech industry page.

How do you build hundreds of SEO pages without hundreds of designs?

Use one CMS template for each page type.

For example, all your location pages can share one template. You design the layout once and populate it with different content for each location.

The important part is making sure the template works for different types of content.

A page targeting Berlin might need different information from one targeting a smaller region. You can use optional sections and different content fields to account for these differences.

Simply changing the city name on an otherwise identical page isn't enough. Each page needs useful information of its own.

We've used this approach with two of our clients.

cleverlohn (payroll SaaS)

We created a CMS template for location pages targeting different German regions. Adding a new region is now a CMS entry rather than a separate design and development project.

The website has 90+ CMS pages and 30+ programmatic SEO pages. Their content team can publish new pages without needing a developer.

Between April and October 2026:

  • 341% organic growth.
  • 40% more indexed pages.
  • 300+ AI responses.

Integral (fintech)

We built a structured CMS to support more than 450 programmatic SEO landing pages targeting high-intent keywords.

The website has more than 500 CMS pages, and the marketing team can create new landing pages independently.

Between June 2025 and June 2026:

  • 208% organic growth.
  • 70% more indexed pages.

In both cases, the goal was to make publishing new pages a content task rather than a development project.

How do marketers build new pages without breaking the site?

Not every page needs to be a CMS template. Campaign landing pages, for example, often need more flexibility.

For these, we use reusable components.

We build on the MAST Framework and create a library of sections such as:

  • Hero sections
  • Logo strips
  • Feature grids
  • Testimonials
  • Pricing tables
  • FAQs
  • CTAs

Each component has a few controlled options, such as background colour, layout or whether a button is visible.

The marketing team can combine these sections, add the content and publish the page. Typography, spacing and responsive behaviour are already set up, so they don't have to worry about breaking the design.

It also means they don't need to duplicate an old static page every time they want to launch something new.

Every GeekyGrowth website project also includes our GeekyGrowth component library, worth €2,350. It gives your team ready-made sections and elements like sliders, popups and promotional banners that they can add to the website without involving a developer.

See what's included in our projects.

Which Webflow CMS limits should you plan around?

Webflow has expanded its CMS capabilities with its next-gen CMS architecture. Here are the current limits for displaying CMS content on a page:

LimitMaximum
Collection lists per page40
Nested Collection lists per page10
Nesting depth3 levels
Items displayed per Collection list100

These are display limits, not the total number of items you can store in your CMS. Your Site plan has separate limits for CMS items and collections.

A few things to keep in mind:

  • You can use pagination to display more than 100 items across multiple pages.
  • Nested Collection lists cannot be placed inside Webflow components.

For most SaaS websites, the bigger challenge isn't reaching the CMS item limit. It's creating a structure that's easy to manage.

We try to keep relationships simple. For example, a case study can reference a customer directly instead of creating several layers of collections that are difficult to maintain.

What do we fix when we take over a messy Webflow site?

We tend to find the same problems:

  1. Landing pages built as duplicated static pages. We replace them with reusable components or CMS templates.
  2. Plain text where a reference should be. Customer names and author details are entered manually in several places. We connect them through reference fields.
  3. Too many unnecessary fields. Three category fields, five different type options and plenty of unused settings. We clean up the structure.
  4. Rich text used for entire page layouts. We split the content into proper fields and components so the layout stays consistent.
  5. No naming conventions. Collections, fields and classes are named differently across the site. We introduce a consistent structure.
  6. SEO fields left empty. We connect meta titles, descriptions and Open Graph images to CMS fields so each new page gets the right settings.

These are usually not difficult problems to fix individually. But when several of them exist together, even simple website updates become unnecessarily complicated.

Is your Webflow CMS ready for 300 pages?

We'll check for free.

Send us your website URL. Within 24 hours, someone from our team will review your CMS structure, page templates and SEO setup, then send you a short list of what needs attention as your website grows.

Get your free website audit

Frequently asked questions

How many pages can a Webflow site have?

It depends on your Site plan. Webflow has separate limits for CMS items, collections and static pages. Check the current Webflow pricing for the latest allowances.

Is Webflow CMS good for programmatic SEO?

Yes. You can use one CMS template to create hundreds of location, integration or use-case pages. Each page should still contain useful, relevant content.

What is a reference field in Webflow?

It connects one CMS item to another. For example, a case study can reference a customer, so you only need to update that customer's information in one place.

Can marketers add pages to Webflow without a developer?

Yes, if the website is built with reusable components and CMS templates. At cleverlohn, the content team can publish new pages without developer support.

Should I fix my CMS structure or redesign the website?

Usually, start with the structure. If the design works but adding and updating content is difficult, a full redesign might not be necessary.

Liana Pogonyi
Written by
Liana Pogonyi
Head of Operations

Keep reading

​
All resources
Webflow
November 18, 2026

Webflow for B2B SaaS: Is It the Right Platform for Your Website?

Webflow suits B2B SaaS teams whose marketing ships pages without engineering. Where it works, where it falls short and what to use instead.
Webflow for B2B SaaS: Is It the Right Platform for Your Website?
Dev Diaries
November 17, 2026

The Optimizely hack explained like you're five

Malware hit Zoom, CNN and 170+ other big websites through an A/B testing tool. Here's what happened in plain English, and how to keep your Webflow site safe.
The Optimizely hack explained like you're five
Dev Diaries
November 16, 2026

Why I Founded GeekyGrowth After Four Years of Freelancing

After four years as an independent Webflow developer, I founded GeekyGrowth to bring branding, design and development together.
Why I Founded GeekyGrowth After Four Years of Freelancing
Migrations
November 12, 2026

WordPress to Webflow: Migrate Without Losing SEO Rankings

How we move SaaS websites from WordPress to Webflow in 6 to 12 weeks while protecting rankings, traffic and backlinks.
WordPress to Webflow: Migrate Without Losing SEO Rankings
talk to a Developer

Skip the sales pitch.

Nicolas Rak, Founder & Lead Dev at GeekyGrowth
Nicolas

Founder & Lead Dev

Book a call with Nicolas
​
Schedule a call

Or send us an e-mail