INDEXED.
Webflow SEO guide

How to Add FAQ Schema on Webflow

Published · Updated

FAQ schema marks up visible question-and-answer content so machines can read it as structured data. Google stopped showing FAQ rich results in search on 7 May 2026, so the markup no longer creates dropdowns in Google. Any value today is in helping other search engines and AI tools read the Q&A, which Google has not said anything about either way.

The fix on Webflow

Add an Embed component to your page and paste a JSON-LD FAQPage schema block into it. Use a schema generator to create the JSON from your Q&A content.

Builder menus change over time. If a label looks different, look for the closest option and check Webflow's help centre.

What this usually looks like on Webflow

Webflow has no built-in schema, so FAQ markup is something you write and paste yourself, usually into an Embed element or the page's custom code. Google stopped showing FAQ rich results on 7 May 2026, so this is now about describing a question-and-answer section clearly to machines, not about a search feature. The detail that catches people out is the CMS: custom code cannot loop over a list, so an FAQ stored as many CMS items does not turn into one tidy FAQPage block by itself.

What to know about Webflow

No native schema markup

Yes, with custom code on CMS plan+

Unlike Shopify, which ships Product schema by default, adding JSON-LD for FAQ, Article, Product, or LocalBusiness schema requires custom code and a CMS plan or higher.

Why this matters

This helps ChatGPT and Google AI Overviews identify your Q&A content as structured data they can extract directly, instead of having to parse it out of regular paragraphs.

Common mistakes on Webflow

  • Putting the markup in site-wide custom code

    Site-wide code appears on every page, but FAQ markup must describe the questions visible on that page. Use page-level custom code or an Embed element on the page itself.

  • Dropping rich text CMS fields into the JSON

    Rich text contains HTML, line breaks and quotation marks, and any of them can break JSON. Use plain text fields for questions and answers, or write the JSON by hand.

  • Expecting the markup to loop over CMS items

    Custom code cannot repeat for each item in a list. Either give the collection a fixed set of fields, such as question 1 with answer 1 up to question 5 with answer 5, or write the JSON for each page by hand.

  • Forgetting to publish

    Custom code changes only appear on the live site after you publish, and Webflow's preview does not show the final markup the way a published page does.

How to check it worked

  1. Make sure the questions and answers appear as visible text on the page. Markup for content that is not visible can be ignored.
  2. After adding the code, paste the URL into the Schema Markup Validator to check the JSON-LD is valid. Google's Rich Results Test no longer supports FAQ.

Publish the site, open the live page, view the source and search for FAQPage. Validate the live address at validator.schema.org, because Google's Rich Results Test no longer checks FAQ markup. Check that every question in the markup also appears in the visible text of the page, word for word. Then ask whether the FAQ itself is useful to a reader. That matters more than the markup.

Generate FAQ schema with the Schema Markup Generator →

Common questions

Will FAQ schema give me a rich result in Google?

No. Google stopped showing FAQ rich results on 7 May 2026, and Google has said the markup can stay on the page without harming search performance. Whether other tools use it is not something Google has confirmed.

Where do I paste the code on Webflow?

Into the custom code or header injection area for the page, if the platform offers one. See the steps above for this platform.

Can I generate FAQ schema from my Webflow CMS automatically?

Only in a limited way. Webflow lets you insert fields from the current CMS item into a template page's custom code, so a fixed set of fields works. Looping over a variable number of items does not, so a long FAQ that changes often is easier to write by hand.

Same fix on other builders

Check your Webflow site for free