← All Posts
November 6, 2026
Structured Data
7

Schema Markup on Webflow CMS Sites: Lessons From Four Client Builds

JSON-LD built from CMS fields rarely fails loudly. It parses, the validator stays green, and the values are wrong. Where the markup lives on four client sites, five ways it broke, and the checks that caught it.

Between July and November 2026 I rebuilt or audited the JSON-LD on four Webflow CMS sites: Carda Health, Oceans, Growthopia and ProfitPad. Schema generated from CMS fields rarely fails loudly. It parses, the validator stays green, and the values inside are wrong: an empty author, a date taken from another field, an apostrophe served as '. This is where the markup lives on those sites, what broke, and the checks that caught it.

Two Google changes frame the work. FAQ rich results stopped appearing in Google Search on May 7, 2026, according to the Search Central changelog, so FAQ markup is no longer a rich-result play. And Google's AI optimization guide (May 2026) says structured data is not required for its generative AI features, while it still helps pages qualify for rich results. What JSON-LD has to do is describe the business and its pages accurately. Accuracy is the whole job.

Where the JSON-LD Lives

Each kind of node has one home:

  • Site-wide head code holds Organization and WebSite, once. On Growthopia it is a single @graph in the site's head code, with the file in the project repo as the source of truth. On another site, the same block is byte-identical on every page.
  • The CMS template builds the page-level nodes (BlogPosting or Article, WebPage, BreadcrumbList) from CMS fields. One site uses each template's Page Settings schema field with field tokens; Carda uses a Code Embed on the template with bound fields.
  • A rich-text field per item holds FAQ blocks: two of the sites store each item's FAQPage as an ld+json block inside a rich-text field.
  • Hand-written JSON-LD covers one-off pages, such as Carda's main program page.

One rule holds it together: one @graph per page, and every page references the site-wide #organization and #website by @id instead of declaring them again. A Service's provider or a post's publisher is a reference, not a copy.

One practical limit: the Webflow API was no help for writing schema on these projects. On two of the sites the schema endpoint answered 403, and the page settings call reported success while storing nothing. Template schema went in by hand in the Designer. So I keep every block in the project repo and compare the served page with it after each paste; on one site, the pasted blocks were compared byte for byte on November 3, 2026. One more trap in that field: paste raw JSON or the full <script type="application/ld+json"> tag. A bare <script> tag is served as JavaScript.

Five Ways Bound Fields Break Schema

1. Characters come out escaped. A straight apostrophe in a CMS field bound into JSON-LD is served as &#39;, and an ampersand as &amp;. Inside a <script> block those entities are not decoded, so a name like O'Neill reads O&#39;Neill in the schema. Parsing still succeeds, so validators stay green. An October 2026 audit of one site found &#39; 21 times on 13 pages and &amp; 12 times on 8. The fix is typographic apostrophes in the CMS fields themselves.

2. A deleted field leaves an empty value. Deleting or replacing a CMS field empties every binding that used it, with no warning in the Designer and no error at publish. On one site, replacing a plain-text author with a reference field left posts with "author":{"@type":"Person","name":""}: valid JSON, nobody in it. On another, the author image in 66 posts' schema was bound to a field that no longer existed. My rule now: publish to staging, diff the JSON-LD against production, and keep the old field until the new binding is verified live.

3. Dates come from the wrong field. Bind datePublished to Webflow's Published On and it changes whenever a changed item is republished, so a bulk update restamps the whole archive. On one site an article showed April 29 on the page and June 18 in its schema. On another site, the schema date and the visible byline came from two different fields and disagreed on 24 of 66 posts. I bind datePublished to the field the byline shows, keep dateModified on Updated On, and set the date format to YYYY-MM-DD in the embed. The schema date and the visible date can also differ by one day: the schema renders in UTC, the page in the site's time zone, and it is the same instant.

4. Free text lands in typed properties. Some schema.org properties expect a fixed format. On one site, a free-text reading-time field produced timeRequired: "PT7 minM" on 72 pages, and the property was removed. On Carda, FAQ answers were placed inside a script string, so a single double quote in any answer broke the whole FAQPage.

5. Empty fields still emit the property. A binding renders whether or not the field has a value. On Carda, posts without an author emitted an author with an empty name, and posts without a medical reviewer an empty reviewedBy. Leave optional nodes out of the template, or put them in an embed that only shows when the field is set.

FAQ Schema Drifts Away From the Page

Google's structured data policy is plain: do not mark up content that readers cannot see. FAQ schema is the easiest to break this way, because the FAQ gets edited on the page and the JSON-LD copy does not. Before the fixes, a crawl of one site found 127 schema questions on 32 pages that did not match the visible text, and two landing pages where none of the 5 schema questions appeared at all. After the fixes, all 80 of its FAQ blocks matched the page (October 22, 2026). On another site, one page's FAQ schema kept an old claim after the page copy changed, and the FAQ check flagged it until the corrected block was pasted on November 3, 2026.

With FAQ rich results gone, the case for FAQ markup is weaker than it was. Where it stays, it needs a check that compares it with the page, because two copies drift.

How I Check It

  • Parse the live page, not the validator report. The Rich Results Test only reports types that can earn a rich result; WebSite and ItemList nodes do not show up there. I fetch the served HTML and parse every ld+json block.
  • Fetch it raw. A fetch tool that strips <script> tags can never see JSON-LD; I use curl with a browser user agent. Where a script injects part of the schema, check the rendered page too.
  • Crawl the whole sitemap. On one site the check covered every sitemap URL: absolute @id and url, ISO dates, no leftover {{wf field tokens, and every FAQ question and answer present in the visible text after normalizing quotes, dashes and spaces.
  • Staging first. Publish to staging and diff the JSON-LD against production before going live.
  • Keep watching. JSON-LD regressions are one of the checks in the monitor I built for client sites.

What It Added Up To

  • Carda: schema v2 live on October 22, 2026, verified on all 67 newer posts, plus a rewritten BlogPosting verified on all 102 older-design posts.
  • Oceans: 124 sitemap URLs re-crawled the same day: all answered 200, every block parsed, no leftover tokens, and 80 of 80 FAQ blocks matched the page.
  • Growthopia: a sitewide Organization and WebSite graph live since August 12, 2026, with the Trustpilot profile linked through sameAs instead of a rating in the schema. Google's review snippet guidelines make an organization's pages ineligible for review stars when it controls the reviews about itself, embedded third-party widgets included.
  • ProfitPad: FAQ unification published on November 3, 2026 across 9 pages, with zero FAQ alarms on the 37 pages the check covered.

None of this is visible to a visitor, and Google says none of it is required to appear in its AI features. It is still where "valid" and "right" part ways on a Webflow build without anyone noticing.

My free SEO audit checks a homepage's JSON-LD on the spot: whether it parses, and whether it declares an Organization, a Person or a similar type for the business.

Post
Long Form
Topic
Structured Data
Published
November 6, 2026
Read
7
Written by
Gregoire Geoffroy
Contents
In This Post

See What Your Site Is Missing

Start with a free audit of your site, checked by me. Or book thirty minutes with your project on screen: you leave with a scoped plan and a number, whether or not we work together.

Grégoire Geoffroy
Grégoire Geoffroy
Webflow Partner
Free audit
Report link within 3 business days
Call
30 min · Google Meet
Time zone
Europe/Paris
Reply
Within one business day