How do I use CMS fields in Webflow schema markup?

Definition: CMS fields supply item-specific values to schema markup, the structured data that describes a page. A Webflow Collection page is a shared template for individual content items; binding its schema values to Collection fields gives each item's page its own data.

As of October 2026, Webflow documents automatic field inclusion for AI-generated schema and manual binding for schema added by hand.

Key facts

• Webflow's schema markup documentation says generated schema includes relevant dynamic Collection fields, while manually added schema requires field binding.
• Webflow's Collection page documentation explains that Collection page settings support dynamic values that produce unique information for each item page.
• Google's structured data guidelines require marked-up content to be visible to readers, including when the markup uses JSON-LD, a JSON format for structured data.

Where does the schema belong?

Webflow's Collection page guide gives this template location:

Pages panel > CMS Collection pages > [Collection Name] template

The settings icon appears when hovering over the template in the Pages panel. Webflow's schema instructions then direct the editor to the Schema markup section, where schema can be generated or added manually. Saving and publishing makes the markup live on the custom or staging domain.

Generated schema automatically includes relevant fields such as name, address, price and image. Manually added schema needs dynamic Collection fields bound to the values that vary by item. Access requires a role other than Reviewer and either a paid Site plan or a paid Workspace.

Which CMS fields are supported?

Webflow's supported-field list includes Plain text, Image, Video link, Link, Email, Phone, Number, Date/Time, Switch, Color, Option and File.

Reference, Multi-reference and Multi-image fields are unsupported in the schema markup feature. The same documentation recommends choosing a supported field, such as Plain text, Option or Image. Deleting a Collection field used in schema breaks its connection and requires updating the schema to reference another field.

How does manual binding work in custom code?

For existing custom-code implementations, Webflow's Collection page documentation describes an explicit binding workflow: select the value in the template's custom code field, then click the purple + Add Field control at its upper right to replace that value with a Collection field.

For a blog Collection, this illustrative JSON-LD scaffold uses Schema.org's BlogPosting type and its headline property:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "BlogPosting",
  "headline": "REPLACE_WITH_CMS_TITLE"
}
</script>

REPLACE_WITH_CMS_TITLE is an editorial placeholder. In the custom code editor, replacing that value through + Add Field connects the headline to the relevant Collection field. This is a minimal binding example; the schema should describe the actual content of the page.

How should the published pages be checked?

Webflow's schema guidance recommends Schema Markup Validator for checking errors. A practical check is to publish the template, test individual Collection item URLs, and compare their schema values with their visible content.

The same guidance places schema from the dedicated field in the published page's <head> and recommends keeping schema in one location to avoid duplicate structured data. Google's content rules make the visible page the reference for what the markup describes.

Related terms

• Structured data
• JSON-LD
• How do I add schema markup in Webflow's page settings?
• How do I validate schema markup added in Webflow?

FAQ

Can I use an author Reference field directly?

Webflow's schema documentation excludes Reference fields from the schema markup feature. You can choose a supported Plain text field for a text value.

Must I move existing custom-code schema?

The same Webflow documentation says existing custom-code schema continues to work. You can keep that implementation and maintain its Collection field connections.

Sources

1. Webflow, "Add schema markup in Webflow to improve SEO and AEO", updated 27 January 2026
2. Webflow, "Structure and style Collection pages", updated 11 July 2025
3. Schema.org, "BlogPosting", accessed 17 October 2026
4. Google Search Central, "General structured data guidelines", updated 10 July 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer