Key takeaways
- Webflow has a Schema markup field in each page's settings, and on CMS templates you can bind collection fields so every post gets its own schema.
- Most marketing sites need three types: Organization on the homepage, Article on blog posts and FAQPage on pages with a visible FAQ.
- Google stopped showing FAQ rich results for all sites on May 7, 2026. FAQ schema can stay, but it no longer changes how you look in search.
- Google says AI Overviews need no special schema. Schema helps machines read your page, but clear content still decides whether you get cited.
- Schema belongs in the CMS template, not in each post. On Kolibri, marketing published 30+ ebooks and articles in under 8 months, a pace where per-post code doesn't scale.
Does Webflow support schema markup?
Yes. Every Webflow page has a Schema markup section in its page settings, and whatever you add there is published in the page's head. Webflow's help article covers the details:
- Where: Pages panel, page settings, Schema markup. It works on static pages and on CMS collection pages.
- CMS fields: on collection pages, you can bind fields like the post name, image and dates, so each item gets unique schema.
- AI option: with Webflow AI turned on, a "Generate schema markup" button drafts the code from the page content.
- Plan: the site needs a paid site plan or a paid Workspace.
Schema you added earlier through custom code still works. Just don't keep it in both places, because duplicate schema sends Google two versions of the same page.
Which schema types does a Webflow site need?
Most marketing sites need three types, plus two small ones that support them. This is what each does:
Skip types that don't match the page. Product schema on a service page or review schema on your own testimonials breaks Google's guidelines and can get your rich results removed.
Is FAQ schema still worth adding in Webflow?
Yes, but for different reasons than before. Google stopped showing FAQ rich results on May 7, 2026, and has since removed FAQ reporting from its testing tools. Google's documentation now says plainly that FAQ rich results no longer appear in Search.
The markup itself is still valid and does no harm. It keeps your questions and answers in a format any machine can read, which is why we still deliver FAQ schema with every article we write. Just be honest about the payoff. Google's guide to AI features says there's no special schema you need to appear in AI Overviews or AI Mode. Clear, answer-first content is what gets cited. Our guide on getting a Webflow site cited by ChatGPT, Claude and Gemini covers the rest.
One rule hasn't changed: FAQ schema must match the FAQ visible on the page, word for word. Schema for questions nobody can see is the fastest way to lose Google's trust in your markup.
How do you add schema to a Webflow page?
Paste JSON-LD into the page's Schema markup field, validate it and publish. For the homepage, start with Organization:
- Open the page settings for the homepage and scroll to Schema markup.
- Paste your JSON-LD or use “Generate schema markup” and edit the draft.
- Publish the site, so the schema is live on your domain.
- Test the live page in Google's Rich Results Test and the Schema Markup Validator.
This is a simplified version of the Organization schema on our own homepage:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Polonio",
"url": "https://www.polonio.io/",
"logo": "https://cdn.prod.website-files.com/6a4ba3c00b0983d571e05c87/6a64d8259e493edffe36f493_logo_polonio_nav.png",
"sameAs": [
"https://clutch.co/profile/polonio-agency",
"https://www.linkedin.com/company/polonio-agency/",
"https://webflow.com/@polonio"
]
}The sameAs links do the most work. They tell Google that your LinkedIn page, review profiles and Webflow profile belong to the same company. If your brand name is also a common word, add `alternateName` with the version people search, like we did with “Polonio Agency”. Google also wants the logo to be at least 112 x 112 pixels and readable on a white background.
How do you add Article schema to Webflow blog posts?
Add it once to the blog's collection page and bind CMS fields, so every post, current and future, gets its own schema. Nobody should have to paste code into individual posts.
In the collection page's settings, write the Article schema and insert fields where the values change:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "[Name field]",
"image": "[Main image field]",
"datePublished": "[Published date field]",
"dateModified": "[Updated date field]",
"author": {
"@type": "Person",
"name": "[Author name field]",
"url": "[Author page link field]"
}
}Two details catch most teams:
- Reference fields don't work in schema. If the author is a reference to an Authors collection, add a plain text “Author name” field and a link field for the author page to the blog collection. Webflow's schema field supports plain text, image, link, date and a few other field types, but not reference, multi-reference or multi-image.
- Check the date format. Google wants dates in ISO 8601 format with a time zone. Test one published post to confirm what your date fields output.
This is why we build schema into templates during a site build, not after launch. We set it up for Kolibri, so their marketing team could publish 30+ ebooks and articles in under 8 months without a developer. At that pace, schema has to come with the template, or it stops being added after the first few posts.
How do you add FAQ schema in Webflow?
On a static page, paste FAQPage JSON-LD into the page's Schema markup field, with each question and answer copied exactly from the page. On CMS pages, the answers need to live in plain text fields.
That last point matters. Rich text fields aren't in Webflow's list of fields you can bind to schema. If your FAQ answers sit in one rich text block, the schema can't read them. For blog posts, a simple setup works:
- Five pairs of plain text fields in the collection, Question 1 to 5 and Answer 1 to 5.
- The visible FAQ on the template built from those same fields.
- The FAQPage schema bound to the same fields, so the page and the markup always match.
If your FAQs change rarely, pasting static schema per page is fine. Just update it every time the visible answer changes.
Our tip: Write and edit schema in a code editor, not in Google Docs or Word. Docs turn straight quotes into curly ones, and a single curly quote around a property name breaks the whole block.
How do you check that your schema works?
Test every template once, then check after big changes:
- Rich Results Test shows whether Google can read Article and Organization schema on a live URL.
- Schema Markup Validator checks every schema.org type, including FAQPage, which Google's tool no longer reports.
- Search Console lists errors for supported types under Enhancements, so you see problems across all posts, not just one.
The most common errors are duplicates (the same schema in page settings and custom code), FAQ schema that no longer matches the page, and logos that are too small or blocked from crawling. Our Webflow SEO checklist puts schema checks into the routine you run before publishing.
Which schema should you set up first?
Start with Organization on the homepage, because it takes ten minutes and helps Google connect every profile to your brand. Then bind Article schema to the blog template, so every post gets it automatically. Add FAQPage only where an FAQ is visible, and stop there until your content gives a reason for more.
If you're planning a new site or a rebuild, our Transform team builds schema into the CMS templates from the start, together with the fields your marketing team needs to publish on its own.



