The SEO Fields Every Webflow CMS Collection Should Have

Webflow generates clean HTML and gives you full control over page-level SEO settings. But CMS collection pages are different. When you have 200 blog posts or 80 property listings, SEO metadata needs to be per-item, not per-page. That means adding specific fields to your CMS collections so that each item can have its own meta title, meta description, OG image, and structured data.

Most Webflow CMS collections ship without these fields. The result: every collection page has the same generic meta description (or none at all), shares with a random or missing image on social media, and provides no structured data to search engines. This is fixable. It takes five minutes per collection and costs zero additional fields against your limit if you plan ahead.

The Seven Fields

Every CMS collection that generates public pages should have these seven fields. Not all are strictly "SEO" fields — some improve social sharing, some improve content quality — but together they ensure that every CMS page is optimized for search, social, and reader experience.

1. SEO Meta Title

Field type: Plain Text

What it does: Overrides the default page title in the browser tab and in search engine results. Without this field, Webflow uses the item's Name field as the page title. That is often fine, but sometimes you want the Name to be "Q1 2026 Market Report" while the meta title is "Q1 2026 Real Estate Market Report | Your Company Name" for better search targeting.

Why it matters: The meta title is the single most important on-page SEO signal. It appears in search results as the clickable blue link. A well-written meta title with relevant keywords directly affects click-through rate.

Help text for editors: "Custom page title for search results. 50-60 characters. Include the primary keyword near the beginning. If left empty, the item name is used."

In the Designer: Bind this field to the page's Title tag in the Page Settings panel. Use a conditional: if SEO Meta Title is set, use it; otherwise, fall back to the Name field.

2. SEO Meta Description

Field type: Plain Text

What it does: Provides the description shown below the title in search results. Google sometimes overrides this with its own snippet, but a well-written meta description still influences click-through rate and gives you control over how your pages appear in search.

Why it matters: Pages without meta descriptions leave Google to extract whatever text it finds on the page, which is often awkward or incomplete. A crafted meta description acts as ad copy for your search listing — it convinces people to click.

Help text for editors: "Summary shown in search results. 120-155 characters. Describe what the reader will learn or find. Include a call to action if natural."

In the Designer: Bind to the Meta Description field in Page Settings. This is a plain text field, not rich text — no formatting, just a sentence or two.

3. OG Image

Field type: Image

What it does: The image shown when someone shares the page on LinkedIn, Twitter/X, Facebook, Slack, iMessage, or any platform that reads Open Graph tags. Without this field, the platform either shows no image or grabs whatever image it finds first on the page, which might be your logo, a decorative element, or nothing.

Why it matters: Social shares with images get significantly more engagement than shares without them. An OG image sized correctly (1200x630 pixels) and designed for readability at small sizes turns every share into a visual link.

Help text for editors: "Image shown when this page is shared on social media. 1200x630px. Use a clear, readable image — it will appear as a small thumbnail in most contexts."

In the Designer: Bind to the OG Image field in Page Settings. If your collection already has a Hero Image or Featured Image, you can use the same image as the default OG Image, but having a separate field allows you to optimize the image specifically for social sharing dimensions.

4. Canonical URL

Field type: Plain Text (not Link, because Webflow's canonical tag binding expects text)

What it does: Tells search engines which URL is the "official" version of this content. This matters when the same content exists at multiple URLs (syndicated posts, cross-published content, print-friendly versions) or when URL parameters create duplicate pages.

Why it matters: Duplicate content dilutes search rankings. A canonical URL consolidates ranking signals to the preferred URL. For most CMS items, the canonical URL is simply the item's own URL, but having the field available means you can handle edge cases: cross-posted content, migrated URLs, or content that originally appeared on a different domain.

Help text for editors: "Only fill this in if this content also appears at a different URL that should be considered the primary version. Leave empty for most items."

In the Designer: Bind to the canonical URL tag in Page Settings. Most items will leave this empty, and Webflow will use the page's own URL as the canonical by default.

5. Structured Data / Schema Type

Field type: Plain Text (or Option, depending on implementation)

What it does: Powers schema.org structured data markup — the machine- readable information that search engines use to generate rich results. An Article with structured data can show publish date, author, and featured image directly in search results. A Product can show price and rating. A LocalBusiness can show address, hours, and reviews.

Why it matters: Rich results stand out in search listings. Pages with structured data have higher click-through rates because they provide more information directly in the search result. Google increasingly relies on structured data for featured snippets, knowledge panels, and AI-generated summaries.

Implementation: Structured data is more complex than the other fields here. You typically implement it with a custom code embed in the collection page template, populated with CMS field bindings. The JSON-LD format pulls from your CMS fields: Name becomes the headline, Published Date becomes datePublished, Author Reference provides the author name, and so on.

For simple cases, an Option field (Article / Product / LocalBusiness / Event) can control which schema type is applied. For complex cases, you may need multiple plain text fields for specific schema properties. The key point is that structured data should be derived from your CMS fields, not hardcoded — so when content changes, the structured data updates automatically.

6. Reading Time

Field type: Plain Text (or Number)

What it does: Displays estimated reading time on the page, typically near the title or byline. "8 min read" sets expectations for the reader before they commit to the content.

Why it matters: Reading time is not a direct ranking factor, but it affects user behavior. Readers who know a post will take 12 minutes are more likely to save it for later rather than bounce after 30 seconds. It also signals content depth — a 2-minute read on a complex topic suggests thin content, while a 15-minute read suggests comprehensive coverage. For search, anything that reduces bounce rate and increases time on page is worth doing.

Help text for editors: "Estimated reading time. Calculate at roughly 200-250 words per minute. Example: 8 min read."

In the Designer: Display near the article title, author, or publish date. This is a display-only field — it does not affect page metadata. If you are syncing content from an external source, Trellis can calculate this automatically based on word count.

7. Excerpt

Field type: Plain Text

What it does: A short summary of the content, distinct from the meta description. The excerpt appears on listing pages (blog index, category pages, search results within the site), in RSS feeds, and in internal collection lists. The meta description is for search engines; the excerpt is for your site's own UI.

Why it matters: Without an excerpt field, collection lists either show the first few lines of the body content (often awkward and cut off mid-sentence) or show nothing. A hand-written excerpt gives you control over how content appears in every listing context: cards, grids, featured sections, and related content modules.

Help text for editors: "1-2 sentence summary shown on listing pages and cards. 100-200 characters. Should make the reader want to click through to the full content."

In the Designer: Bind to text elements within collection lists. Use text truncation (CSS line-clamp or character limit) as a safety net, but a well-written excerpt should not need truncation.

Field Types Matter for SEO

All seven fields above use Plain Text or Image. This is deliberate. SEO metadata should never be Rich Text — you do not want bold, italic, or headings in a meta description. Using Plain Text ensures that editors cannot accidentally add formatting that breaks meta tags or looks wrong in search results.

For a comprehensive reference on how each Webflow field type works and when to use it, see the plain text field guide and the image gallery field guide in the Trellis wiki.

Help Text Is Part of SEO

The help text you write for each field directly affects whether editors fill it in correctly. If a meta description field has no help text, editors will either skip it or write something unhelpful. If it says "120-155 characters, describe what the reader will learn, include the primary keyword," they have a clear target.

Good help text acts as a mini style guide embedded directly in the CMS editing interface. Editors see it every time they create or edit an item. It is the difference between a CMS that produces SEO-ready content and one that produces content someone has to fix later.

Webflow supports help text on every CMS field. Use it. For every field. Not just SEO fields — every field benefits from a one-line description of what to put there and why it matters.

The Heading Hierarchy Check

While not a CMS field, heading hierarchy inside Rich Text content is one of the most common SEO mistakes in Webflow. The rule is simple: each collection page should have exactly one H1 (the item title), and the body content should use H2 and H3 for section structure. Editors working in the Rich Text field need to understand that H1 is reserved for the page title — they should start their body content at H2.

This is a training issue, not a CMS issue. But you can help by adding help text to the Rich Text body field: "Start with H2 for main sections. Use H3 for subsections. Do not use H1 — it is already set by the page title."

How Trellis Adds SEO Fields Automatically

When you use Trellis to create or audit a Webflow CMS collection, it includes SEO fields by default. Every collection that generates public pages gets SEO Meta Title, SEO Meta Description, and SEO OG Image. Blog and article collections also get Excerpt, Reading Time, and Canonical URL.

Each field comes with pre-written help text following the guidelines above. Editors see clear instructions the moment they open the CMS editor. This removes the most common failure mode: the fields exist but nobody fills them in because nobody knows what to put there.

If you are syncing content from Airtable or Notion, Trellis maps source fields to SEO fields automatically. An Airtable "Meta Description" column maps to the Webflow "SEO Meta Description" field. A Notion "OG Image" property maps to the Webflow OG Image field. The sync keeps them in sync — update the meta description in Airtable, and it updates on the live site at the next sync interval.

The Five-Minute Setup

Adding these seven fields to an existing collection takes about five minutes:

1. Open the collection in the Webflow Designer
2. Add each field with the correct type (Plain Text for all text fields, Image for OG Image)
3. Write help text for each field using the examples above
4. In the collection page template, bind each field to the appropriate meta tag in Page Settings
5. Publish and verify with a tool like the Twitter Card Validator or Facebook Sharing Debugger

Or let Trellis do it. The schema architect adds these fields automatically, with the right types, the right names, and the right help text. No manual field creation, no risk of choosing the wrong field type.

See pricing or try it free.