How Do You Build a Related Posts Section in Webflow Using CMS Reference Fields in 2026?

Why does your related posts section keep showing the wrong articles?

Most likely it is sorted by date, so it just shows your newest posts every time instead of posts that match the topic. The fix is to use a Reference field or a Multi-Reference field in Webflow CMS so the section pulls posts that truly relate to what the reader is on right now.

I had a client with 120 posts whose old related section did exactly this. It showed the newest posts on every page, no matter the topic. A reader finishing a post about forms might see three posts about pricing. Not helpful. We switched it to a category-filtered Collection List, and the section finally became relevant. Readers started clicking through to a second article instead of leaving.

That single change told me a lot. The old block was not broken in code. It was broken in logic. It linked posts at random, so readers learned to ignore it. Once the links matched the topic, the same block that people used to skip became a path they actually followed. Relevance is the whole game with related posts.

What is a related posts section really for?

It is internal linking that runs on autopilot. A related posts block at the end of an article points the reader to your other work on the same theme. That keeps them on your site and helps search engines connect your pages. Done right, it is one of the highest-value blocks on a blog, and it builds itself once set up.

Google Search Central guidance states that internal links help Google find pages and understand how they relate to each other. So a good related posts block does double duty. It serves the reader, and it helps Google map your blog. I do not treat it as decoration. I treat it as a working part of the page that earns its place at the bottom of every post.

What is a CMS Reference field, and how is it different from a Multi-Reference field?

A Reference field links one CMS item to one other item, like tying a post to a single Category. A Multi-Reference field links one item to many items, like tying a post to several related posts at once. Both live in Webflow CMS, and both let a Collection List pull connected content onto the page on its own.

These two field types are the engine behind everything in this guide. The single Reference field powers the automatic approach, because most blogs already point each post at one Category. The Multi-Reference field powers the hand-picked approach, because it lets one post point at a small set of chosen posts. Knowing which field does what makes the rest of the setup simple in the Webflow Designer.

Does keeping readers on a second page actually help?

Yes, and it is the cheapest traffic you will ever get. Here is my own observation after years of building blogs. A rich, relevant related posts block keeps readers moving to a second page. You already paid to earn that visitor. A second pageview from the same person costs you nothing extra, so it is pure upside.

The numbers around engagement back up why this matters. The 2025 engagement benchmarks, via Optimizely, put average session duration across industries near 2 minutes and 17 seconds. Those same benchmarks treat a 60% to 80% scroll depth as strong for long-form content. So readers who reach the bottom of your post are your warmest audience. A good related posts block catches them right at that moment, before they bounce.

What is the automatic approach to related posts?

The automatic approach uses your Category reference field to pull matching posts on its own. Most Blogs collections already have a Category Reference field. So you can build a related section that filters by that field with no manual picking. It updates itself as you publish more posts, which is why it scales so well.

Here is how I set it up in the Webflow Designer. On the Collection Page template, I add a Collection List bound to the Blogs collection. Then I set a filter so Category equals the current item's Category. Last, I limit it to three items. Now each post shows three other posts from the same category in the Categories collection. As your blog grows, the section stays fresh without any editing from you.

How do you stop the current post from showing in its own list?

This is the tricky part of the automatic approach. The filter pulls every post in the category, including the one the reader is already on. So the current post can show up in its own related list, which looks broken. You need a way to hide it so the reader never sees a link back to the page they are reading.

Finsweet Attributes can hide the current item from a Collection List using a CMS Filter setup. It reads the slug of the current page and drops that matching item from the list. This keeps your related posts clean and avoids the awkward link that points back to the same page. I reach for it on almost every automatic related section I build, since native filters cannot reference the current slug on their own. You can also try Conditional Visibility to hide the wrapper when no other posts exist.

What is the hand-picked approach instead?

The hand-picked approach gives you full editorial control with a Multi-Reference field. Instead of filtering by category, you choose the exact posts you want to show under each article. It takes more effort per post, but you decide every link by hand, which is powerful for your most important pages.

To set it up, add a Multi-Reference field called Related Posts to the Blogs collection. For each article, choose two or three posts you want to feature. Then bind a Collection List to that Multi-Reference field on the Collection Page template. Now the section shows only the posts you picked. This is great for guiding readers along a path you planned out yourself, step by step.

When should you use automatic versus hand-picked?

Use automatic for big blogs and hand-picked for cornerstone posts. If you have a large library that grows fast, the category-filtered Collection List keeps every page current without manual work. You set it once and it scales with you, even as you add dozens of new posts.

For your most important pages, the cornerstone articles you want to rank and convert, the hand-picked Multi-Reference field is worth the time. You can point readers to the exact next step you want them to take. Many sites I build use both. Automatic everywhere, then hand-picked links on the few posts that carry the most weight. There is no rule that says you must choose only one.

How does this fit into a bigger linking plan?

Related posts are one piece of a wider internal linking plan. On their own they help, but they shine when they fit a real structure. That structure is how you guide both readers and search engines through your whole blog, not just one page to the next. The slug and Category of each post already tell Webflow how things connect.

If you want the full picture, read my guide to internal link architecture. To plan which posts should relate to each other in the first place, my piece on topic clusters shows how to group content by theme. And if you want readers to filter posts themselves, my tutorial on CMS tag filtering walks through that without extra tools.

What should you do this week?

Build one related posts section and make it relevant. First, open your Collection Page template in the Webflow Designer. Next, add a Collection List bound to the Blogs collection and set a filter so Category equals the current item's Category. Then limit it to three items. After that, add a Finsweet Attributes CMS Filter to hide the current item using its slug. Last, for two or three cornerstone posts, add a Multi-Reference field and hand-pick the links instead.

My honest take is this. Related posts are not decoration. They are internal linking that runs on autopilot, and they keep your warmest readers moving deeper into your site. Pair this with a real internal link architecture, plan your themes with topic clusters, and let readers explore with CMS tag filtering.

If you want a hand wiring this up in your own project, reach out. I work with founders on this kind of thing from my small practice in Bengaluru. Let's chat.