Built for modern Webflow creators

How to Plan a Complex Webflow Project: Page Structure, CMS, and Sections Before You Design

Plan a complex Webflow project before you design: sitemap, page sections, CMS collections and SEO fields, with a real example.
2026-11-18
10
min read
How to Plan a Complex Webflow Project: Page Structure, CMS, and Sections Before You Design

Key Takeaways

  • Plan the content, the structure of every page and the sections before the design starts.
  • Keep the sitemap in Figma and all URLs in a table, with the main keyword in each slug.
  • Make a list of sections for every page. Sections used on more than 2 pages become Components.
  • Use a CMS collection for a lot of information with a repeating structure.
  • Make a CMS scheme table, and remember the limit of 60 fields per collection.
  • Add SEO fields and FAQ fields from the start. Move FAQ to a separate collection to save fields.
  • Prepare Variables and Client-First base classes before you build.
  • Give the designer the sections list, the CMS scheme and the text length limits.

Why plan before you design

A complex Webflow project is hard to fix after the design is ready. If the designer forgets a CMS field, or the same section looks different on every page, the developer has to change the design again. This case shows the plan I make before the design starts: content, page structure, sections, CMS and SEO fields.

As an example, I use my latest template, Consilis. It has 11 static pages, 5 system pages, 6 CMS collections and more than 30 different sections.

I also show how the same ideas work on a real client site, Benson Law.

What makes a Webflow project complex

A project is complex when many things depend on each other. Usually it has:

  • many pages, and not only a few static ones;
  • several CMS collections that are connected to each other;
  • sections that repeat on different pages;
  • dynamic pages with many fields, such as author, dates and related items;
  • a team that will edit the content after launch.

In Consilis, the blog, the case studies, the team and the pricing all come from the CMS. On the Benson Law site, one list of 27 practice areas is shown in three groups on the Practice Areas page, and the same items appear again on the home page. If this is not planned before the design, every new field or section means another design change.

Benson Law practice areas page with 27 services grouped in 3 categories
Benson Law practice areas page: 27 services in 3 groups share one structure.

Step 1: Collect the content and study the business

I start with the information. I ask the client for the content, a list of pages, the Figma file if there is one, and all details about the business. I also analyze the competitors in detail.

From this information I build the structure of every page. Then I make prototypes with the real content, then the design, and only then the development in Webflow. When I open Webflow, I already have the designs of all pages, with a clear structure and all the sections the site needs.

Step 2: Build the sitemap and the URL list

I keep the structure of the site in Figma, and all URLs in a table. For Benson Law, the planning started from the client's list: 27 different legal services, which became 27 practice area pages.

The URL (slug) should contain the main keyword that the page or the collection item is about. If I need to change a URL later, I set a 301 redirect, so the old link keeps working.

Consilis sitemap in Figma with a table of page URLs
Consilis sitemap in Figma with the URL list for every page.

Step 3: Split every page into sections

I split a page into sections according to the content it needs. The order is logical, from the first section to the last. For every page I make a list of sections.

Then I check which sections repeat. A section that is used on more than two pages becomes a Component. For example, the same call-to-action block, "Get your 100% free consultation", is on both the home page and the Practice Areas page of Benson Law. It makes sense to build such a block once and reuse it. You can read more about reusable Components with Properties in my other case.

List of Consilis page sections with reusable sections marked as Components
Section list for Consilis: sections used on more than 2 pages become Components.

Step 4: Plan the CMS collections

I use a CMS collection when there is a lot of information, the page structure repeats and the items belong to one category. In Consilis there are six collections:

  • Pricings
  • Blog Categories
  • Blog Posts
  • Team Members
  • Case Categories
  • Case Studies

The collections are connected with each other. For example, Case Studies has an Author field that uses a multi-reference to the Team Members collection. This is very convenient: the author's data is edited in one place, and it changes in all the cases at once. You can see how Consilis is built in a separate case.

Case Studies collection settings with the Author multi-reference field linked to Team Members
The Author field in Case Studies pulls data from the Team Members collection.

Make a CMS scheme before you build

The fields depend on all the information that the page must show. Before building, I make a table with the CMS scheme. It shows how many fields each collection has, which fields repeat, and which collections can be linked. Where it helps, I use Reference and Multi-reference fields. This is also how I keep the number of fields small.

Remember the limit of 60 fields

A Webflow collection can have only 60 fields. You cannot add more, unless you buy extra limits in your plan. So the number of fields is a planning question, not a detail you solve at the end. A good way to save fields is to move FAQ into a separate collection, and to connect it to the page with a reference. For more about this topic, see my Webflow CMS guides.

Step 5: Plan SEO fields and FAQ from the start

I add SEO fields to every collection right away, and separate FAQ fields where they are needed. It is much easier than adding them to 30 or 40 items later. On Benson Law, every practice area page has its own FAQ, and the client wrote about it in the review: "added a 5-question FAQ section for each item."

Step 6: Prepare the Client-First base before the build

Before I build any page, I prepare the base of the project. I follow Client-First and the class naming rules I use in every template.

  • Variables for fonts, colors, spacing and gaps.
  • Base classes for text: all headings from H1 to H6 and the rich text.
  • Base classes for structure: body, page-wrapper, main-wrapper, section, padding-global and container-large.
  • Section spacing: padding-section-large, padding-section-medium and padding-section-small.
With this base, every new section looks like the rest of the site, and the page structure is the same on all pages.
Webflow Variables panel and Client-First base classes in the Consilis project
Consilis base: Variables for fonts, colors and spacing, plus Client-First base classes.

Step 7: Give the designer a clear plan

I can design the site in Figma myself, or build from a design made by someone else. In both cases the designer gets a clear plan before the work starts:

  • the list of sections for each page;
  • the CMS scheme, with the fields that every dynamic page must show;
  • the length limits for headings and texts where they matter;
  • the image sizes, and how a page looks when an optional field is empty.

Then the designer does not have to guess what the CMS can show, and I do not have to change the design after it is ready.

‍

Example: how I planned the Consilis template

For Consilis I followed these steps: information about the business, the structure of every page, prototypes with real content, the design, and then the Webflow build. The plan had 11 static pages, 5 system pages, 6 CMS collections and more than 30 different sections. Because the sections and fields were planned first, the structure was clear from the start, and every section is easy to reuse.

Common mistakes when planning a complex project

These are the mistakes I see most often:

  • The designer forgets the fields of dynamic pages. For example, the creation date, the update date, the author, the author photo and the text about the author.
  • There is no section with related items. A case page can end without a block of similar cases.
  • The CTA section is different on every page. It should be one section, so it can be one Component.
  • H2 and H3 sizes are different on different pages. The fix is a base class for every heading level.
If the design was made without a CMS plan, it can still be fixed. I add the missing fields and change the design so that everything looks logical and is easy to use. In some places it is hard, but it is possible.

What the client gets from a good plan

When the plan is ready before the design, the client gets fewer design changes, a faster project and a site that is easier to edit. The structure is clear from the start, so it is easy to add new sections that show the content in full. After the launch, the same plan makes the handover of the site to the client much easier.

Conclusion

A good plan for a complex Webflow project has seven parts: content, a sitemap, a list of sections, CMS collections, SEO fields, a Client-First base and a clear brief for the designer. If you need a site built like this, see my custom Webflow development service.

Complex Webflow project planning checklist

Complex Webflow project planning checklist
Step Done when
1. Content I have the content, the list of pages, the Figma file (if any) and details about the business
2. Competitors The competitors are analyzed and the structure of every page is clear
3. Sitemap and URLs The structure is in Figma and all URLs are in a table, with keywords in the slugs
4. Sections Every page has a list of sections in a logical order
5. Components Sections used on more than 2 pages are marked as Components
6. CMS scheme Collections, fields and references are planned in a table, within the 60-field limit
7. SEO and FAQ fields SEO fields and FAQ fields are planned in every collection that needs them
8. Client-First base Variables and base classes for headings, text, sections and spacing are ready
9. Designer brief The designer has the sections list, the CMS scheme and the text length limits
About the Author:
I design and build Webflow templates for the Webflow Marketplace and work with the Client-First system, CMS structure and Variables. I write these guides from the templates and client projects I work on.
Last Updated:
2026-11-18
Best For:
Freelancers, Webflow Agencies, Webflow Developers, Website Owners

Webflow project planning FAQ

Quick answers about sitemaps, sections, CMS collections and planning before the design.

Why plan a Webflow project before the design?

Without a plan, the designer can forget CMS fields or make the same section different on every page. Then the design has to be changed after it is ready. A plan with a sections list and a CMS scheme prevents this, so there are fewer design changes and the project is faster.

What makes a Webflow project complex?

A project is complex when it has many pages, several connected CMS collections, sections that repeat on different pages, dynamic pages with many fields and a team that will edit the content. Consilis, for example, has 11 static pages, 5 system pages, 6 CMS collections and more than 30 sections.

Which sections should become Components?

I make a Component from a section that is used on more than two pages. A call-to-action block that appears on many pages is a good example. Build it once and reuse it, so it stays the same everywhere.

When should I use a CMS collection?

Use a collection when there is a lot of information, the page structure repeats and the items belong to one category. Blog posts, case studies and team members are typical examples.

How many fields can a Webflow CMS collection have?

A collection can have up to 60 fields. More is possible only with extra limits in a plan. To save fields, use Reference and Multi-reference fields, and move FAQ into a separate collection.

Where should I keep the sitemap and the URL list?

I keep the structure of the site in Figma and the URLs in a table. The table has all the addresses before the build starts.

What if I need to change a URL (slug) later?

Set a 301 redirect from the old URL to the new one, so the old link keeps working. It is better to choose a slug with the main keyword from the start.

What should the designer know before the design?

The designer needs the list of sections for each page, the CMS scheme with the fields of every dynamic page, and the length limits for headings and texts. It also helps to know the image sizes and how a page looks when an optional field is empty.

Can I fix a design that was made without a CMS plan?

Yes. I add the missing fields and change the design so that everything looks logical and is easy to use. In some places it is hard, but it is possible.

What do I need from the client before I plan a Webflow project?

I ask for the content, the list of pages, the Figma file (if there is one) and detailed information about the business. I also analyze the competitors. With this I plan the structure of every page, make prototypes with the real content, and only then start the design and the build in Webflow.

About Kedd Design
I design and build Webflow templates and websites with a clear structure.
I focus on clean structure and functional design.
100%
Built on Client-First methodology
Need a Webflow template or a custom website?
I build clean, well-structured Webflow websites. Tell me about your project, and I'll suggest the best next step.
tehnosupp@gmail.com
Prefer a quick chat? Reach me on:
Yevhen - Founder of Kedd Design
Yevhen - Founder of Kedd Design
Webflow Designer & Developer
Let's build something clear and well-structured together.