Webflow CMS Reference Fields: Model Relationships Before Importing Content

Reviewed 12 September 2026.

A content model determines what editors can reuse and what the website can display consistently. If every relationship is pasted into rich text, filtering and related content become difficult. If every sentence becomes a field, editing becomes cumbersome.

Start with the content questions

List the information a template needs to answer. A project page may need a client name, service, industry, cover image and narrative. An article may need categories and a related project. Distinguish information that must be queried or repeated from information that only belongs inside the story.

Build a small set of example records before finalising the schema. Include an ordinary record, a complex one and one with optional information missing. These examples reveal whether the model supports the actual content or merely the neatest design mockup.

Use relationships for reusable entities

A category or project referenced by many articles is a reusable entity. A reference connects records instead of duplicating the same information in each article. Decide whether each relationship allows one item or several based on the publishing rule you need.

For example, an article may belong to several categories but point to one primary project. Write that rule in the editorial instructions. Webflow’s CSV import supports references matched by slug and multiple reference values separated by semicolons. Use existing destination records and test the mapping before importing the full file.

Choosing where information belongsInformationLikely locationReasonClient name reused across pagesA project or client recordMaintain one authoritative valueArticle categoryReference relationshipSupport consistent groupingLong explanationRich-text fieldPreserve editorial flexibilityFeatured selectionSwitch with a publishing ruleExpress a clear editorial choice

Keep presentation rules separate from content meaning

A field named Industry describes content. A field named Third purple card describes a temporary layout decision. Prefer names that remain meaningful when the design changes. Use switches for clear binary editorial choices, such as whether an item is featured.

Decide how optional fields affect the template. A missing quote should remove the quote block, not leave an empty heading. A record without a related project should still produce a complete page. Test the empty states while the template is being built, when structural changes are easier to make.

Validate the model through an editing task

Ask an editor to add a realistic record without instructions from the builder. Watch for uncertain field names, repeated typing and unclear relationships. Revise the labels and help text where the editor has to guess.

Before a bulk import, compare a sample record in the CMS and on the rendered page. Check special characters, images, references and optional sections. Keep stable slugs for established records unless a deliberate URL change is required. A clean spreadsheet is only one part of a successful content model: the resulting pages and editing workflow must also work.

Model the relationships your editors need to maintain, then let the template decide how to display them.

A related YAVACADO project

For Trustlayer io, YAVACADO migrated the website and blog from Strapi to Webflow. The project focused on giving the marketing team a visual publishing workflow. It is a practical example of why content structure and the people maintaining it should be considered together.

View project: Trustlayer io

Check your own website

Your review checklistTest three different content recordsDefine one-versus-many relationshipsCheck optional-field statesVerify reference slugs before importUse these checks as you review. Selections are not saved.

Put it into practice

An editor types the same project title and URL into twelve articles. What should you investigate?

Show the suggested approach

Consider a project reference so the title and destination come from one record. Keep article-specific commentary in the article. This separates reusable project identity from the particular reason it is relevant to each story.

Continue reading

Webflow CMS: Build a Content Library Your Marketing Team Can Run

References

• Webflow: importing content and references

Discuss your website

Bring your current website and the task you want to improve. YAVACADO can help define the content, design and implementation work needed for the next step.

Tell us about your project