Better in English?
Better in English? Switch the website language for a better experience.
Strong internal linking can't be fixed after the fact by adding a few links by hand in the rich text. It's decided upstream, when you model your Webflow CMS Collections. That's where 80% of the game is won.
Why? Because Webflow connects content through reference fields and multi-reference fields. Once displayed on the front end, these fields become automatic links between your pages. A blog post that references a category, an author, related articles, and an associated service mechanically generates 4 to 6 contextual internal links, without ever touching the rich text. That's the difference between a linking structure that grows with your content and one that decays the moment you stop maintaining it by hand.
At Mazette.co, when we build a Webflow architecture for a client, we systematically model collections by thinking "link graph" before thinking "form fields." A poorly structured CMS means internal linking that will never happen, no matter how much editorial effort you put in.
Before creating a field, ask yourself the reverse question: which page should point to this collection, and from which other page would someone want to reach it? An isolated "Articles" collection is useless. An "Articles" collection connected to "Categories," "Authors," "Services," and "Case Studies" becomes a node in your semantic network.
Webflow doesn't automatically create a return link. If your Service page references Case Studies, also plan a reverse multi-reference field on the Case Studies collection to link back to the relevant Services. This bidirectionality is what turns a simple link into a true web of internal linking, valued both by Google and by AI engines that assess a site's thematic coherence.
A poorly organized CMS collection can bury content 5 or 6 clicks away from the homepage. Structure your collections so that every item is reachable within 2-3 clicks via at least two different paths: through its category, and through related content (a linked article, an associated service, a city if you manage local content).
| Webflow field type | Internal linking use | Concrete example |
|---|---|---|
| Reference (1-to-1) | Single, reliable contextual link | An article -> its main category |
| Multi-reference | Cluster of thematic links | A service -> several associated case studies |
| Bidirectional cross-reference | Web-like linking, strong signal for SEO and AEO | City <-> Local agency <-> Case studies from that city |
| Simple text field | No link generated automatically | Avoid for any relational content |
The question to ask is never "what info do I need to store" but "which pages need to talk to each other." Take a concrete example we often see with agency clients or multi-location businesses: a "Cities" collection, a "Services" collection, and a "Case Studies" collection.
The result: a Case Study page automatically generates a link to its city and its service. A City page automatically lists all local case studies. A Service page automatically lists all associated case studies. Three collections, one linking triangle that updates itself with every new item added by the editorial team.
This is exactly the logic we apply on our own Webflow agency by city pages: each city links back to local case studies, each case study links back to the city and the relevant expertise. The linking structure never depends on whoever happens to be writing the content remembering to add a link.
A "Testimonials" collection with no reference to "Clients" or "Services" is a dead end. Every collection should have at least one incoming and one outgoing reference, otherwise it adds nothing to your linking structure—just dead data.
A link typed by hand into a Rich Text field works, but it carries no structural consistency: if the target page's URL changes, the link breaks silently. A Reference field, on the other hand, automatically follows slug changes. It's an invisible difference for the visitor, but a crucial one for maintainability.
Even the best collection structure is useless if your Collection List templates don't display these relationships. Systematically plan to include blocks like "Related articles," "Associated services," or "Other case studies in this city" in your dynamic page templates—that's where the data graph finally turns into a real navigation experience for the user.
Well-built internal linking no longer serves Google alone. Answer engines like ChatGPT, Perplexity, or Google's AI Overviews analyze a site's thematic coherence to decide whether they can cite it with confidence. A graph-based CMS architecture, where each page clearly references its sibling and parent pages, sends a very readable editorial trust signal to these systems.
We go into more detail in our article on Webflow AEO Analytics opening up to Claude and Gemini: AI visibility is built on the same foundations as good technical SEO—namely, a clear content structure, rather than any marketing sleight of hand.
You'll also find our full recommendations in Webflow SEO best practices, which detail how to combine CMS structure, semantic markup, and technical performance.
If your Webflow site already exists and you suspect a shaky linking structure, a few tools can help you get a clear picture quickly.
If the audit reveals a CMS structure too rigid to accommodate these new relationships, it's sometimes better to start fresh on solid foundations rather than patch things up. This is often the trigger that leads our clients coming from WordPress or other CMS platforms to migrate to Webflow: relational collection logic is natively built for this kind of architecture, whereas a traditional CMS forces you into plugins and workarounds.
Before even opening Webflow, we map out the client's content as a relational diagram: what entities exist (services, cities, case studies, articles, team), and what logical relationships naturally connect them. This work usually happens upstream in Figma, alongside wireframing, so that the Collection List template design already integrates linked content blocks from the very first mockup.
This approach is an integral part of our design method, and applies just as much to complex redesigns as to simpler sites where internal linking remains a growth lever that's all too often overlooked. If your current CMS looks more like a spreadsheet than a content network, it's probably the right time to discuss it with our team via our contact page.
Code
Over 120 companies have already stepped out of the shadows with us.
Use a multi-reference field on your Articles collection pointing to other items in the same collection, then display that field through a Collection List in your template. Every update to the field updates the linking structure without touching the design or the rich text. It's the most reliable and easiest method to maintain over time.
Reference fields are always preferable because they automatically follow slug changes and guarantee there are no broken links. Manual links in rich text are still useful for occasional editorial context, but they should never carry the main linking structure. Combine both: structure through references, nuance through rich text.
There's no universal ideal number: what matters is that every collection has at least one incoming and one outgoing relationship with another. Three to five well-connected collections often produce better linking than ten isolated ones. Prioritize the quality of relationships over the number of collections created.
