Most Webflow blogs are set up to fail. When you only have 5 or 10 articles, a messy database structure is easy to ignore. You can manually style author names, paste category labels as plain text, and hard code links to related posts. But once your blog grows past 50 posts, this ad hoc approach falls apart, leading to broken layouts, duplicate work, and poor organic search performance.
To structure a Webflow CMS blog correctly, you must build separate, interlinked collections for Blog Posts, Categories, and Authors from day one. By using single reference and multi-reference fields instead of plain text fields, you ensure that every author profile, category archive, and related post section updates automatically across your entire site.
After 450+ builds, I have migrated dozens of sites away from messy, flat databases to structured architectures. Getting this right before you write your first post saves hundreds of hours of manual migration work. Let's walk through the exact schema you need to build.
The core three-collection architecture
A scalable blog relies on a relational database design. Instead of cramming all your data into a single blog post collection, you should divide your content into three distinct collections.
1. The Authors Collection
This collection stores the human entities writing your content. Setting this up as its own collection is crucial for building credibility and satisfies Google's E-E-A-T guidelines.
- Name: Plain text
- Profile Picture: Image field
- Bio: Rich text or plain text
- Title / Role: Plain text
- Social Links: Link fields for LinkedIn or Twitter
- Slug: Automatically generated
2. The Categories Collection
This collection groups your articles into broad, high-level topics. Keep this list focused, aiming for 4 to 8 categories maximum.
- Name: Plain text
- Icon / Cover Image: Image field
- Description: Plain text
- Color: Color field (useful for dynamic UI labeling)
- Slug: Automatically generated
3. The Blog Posts Collection
This is your primary collection where the actual content lives. It binds to the other two collections using reference fields.
- Title: Plain text
- Post Body: Rich text field
- Excerpt: Plain text (140 to 160 characters for search listings)
- Main Image: Image field
- Author: Single reference field (pointing to the Authors Collection)
- Category: Single reference field (pointing to the Categories Collection)
- Tags: Multi-reference field (optional, pointing to a separate Tags Collection)
- Publish Date: Date field
By separating these collections, you only write an author's bio or design a category icon once. If an author changes their profile picture, you update it in the Authors Collection, and it instantly changes on every blog post they have ever written.
Leveraging reference page templates for automatic archives
One of the biggest advantages of this structure is that Webflow automatically generates a page template for every single item in your collections. These are called Collection Pages.
When you create a Categories Collection, Webflow generates a Category Template page. You can design this page once as a dynamic archive. By placing a Collection List on this template and filtering it to only show items where the Post Category equals the Current Category, Webflow will automatically generate a custom archive page for every category you create.
The same rule applies to the Authors Collection. The Author Template page can display the author's bio, social links, and a grid of all the posts they have authored. This setup requires zero manual building when you hire a new writer. You simply add them to the Authors Collection, and Webflow automatically builds their author profile page and links their articles.
Want a website that turns visitors into customers, not just compliments?
Book a 15-min introSlug planning and avoiding the redirect trap
A major pitfall when setting up a Webflow blog is rushing the URL slug structure. URL structures are difficult to change later because modifying a slug changes the live link, breaking external backlinks and forcing you to create manual 301 redirects to avoid 404 errors.
Before you publish, map out your URL structure. Webflow enforces a folder structure for collection pages based on the collection name. By default, your URLs will look like this:
- Blog Posts:
yourdomain.com/post/how-to-scale - Categories:
yourdomain.com/category/webflow - Authors:
yourdomain.com/author/talha-shahzad
I recommend keeping the folder names simple and descriptive. If you want your blog posts to live under /blog/ instead of /post/, name your Blog Posts collection "Blog" when you create it. You cannot easily change the parent folder name once the collection is created without deleting and recreating it, so check this setting in the collection configuration before you build your page templates.
Structuring for related posts and internal linking
A healthy blog needs to pass link equity between articles to help search engine crawlers discover new pages. To do this, you need a related posts module at the bottom of your blog post template.
There are two ways to structure this in Webflow:
- The Automatic Method: Add a Collection List to your Blog Post Template. Set a filter where the category of the post matches the category of the current post. To prevent the page from displaying the post the user is already reading, add a second filter where the Post Name is not equal to the Current Post. Limit this list to 3 items.
- The Curated Method: Add a multi-reference field called "Related Articles" to your Blog Posts collection, pointing back to the Blog Posts collection itself. This allows you to hand-pick which articles appear at the bottom of each post, giving you total control over user pathways.
The automatic method is easier to maintain because it requires zero effort when publishing. The curated method offers better control but requires your editor to manually select related posts every time they draft a new article.
Structuring your CMS properly is about thinking five steps ahead. By building a clean, relational database schema with separate collections, planning your URL folder paths, and designing dynamic archive templates from the beginning, you create a system that runs smoothly whether you have 10 articles or 10,000.