Schema markup is structured data, usually written as JSON-LD, that labels a page’s content so search engines and AI systems understand it. On a Webflow site, add Organization schema site-wide and Article schema on blog posts, paste it into the custom code fields, and test it in Google’s Rich Results Test. It doesn’t raise rankings directly.
Which schema types matter on a Webflow site?
| Schema type | Where to add it | What it does in 2026 |
|---|---|---|
| Organization or LocalBusiness | Site-wide, in Project Settings | Establishes your brand as a clear entity |
| Article | Each blog post | Marks the headline, author and publish date |
| FAQPage | Pages with visible Q&A | No Google rich result since May 2026; describes visible Q&A |
| Speakable | Selected sections | Limited eligibility; check the platform first |
What does schema markup do?
Schema markup, usually written as JSON-LD, is a standard way of labelling content so machines understand what a page is about. It doesn’t change rankings directly. It changes how search engines and other systems interpret your content and, sometimes, how they display it. Some types help specific search features; others show little measurable effect on AI citations.
- Schema (structured data, usually written as JSON-LD) is a standardized way of labeling content so machines, not just humans, can understand what a page is about
- It doesn’t change your rankings directly, it changes how search engines and other systems can interpret and sometimes visually display your content
- The honest 2026 picture is more nuanced than most guides admit: some schema types genuinely help specific surfaces, others have shown little to no measurable effect on AI citation specifically
Which schema types are worth adding?
Organization or LocalBusiness schema is worth adding to every site, because it gives your brand a clear identity across search and knowledge panels. Article schema helps blog posts by marking the publish date, author and headline. FAQPage no longer earns FAQ rich results in Google, and Speakable has narrow eligibility, so check before investing in either.
- FAQPage: describes visible questions and answers, but Google discontinued FAQ rich results in May 2026. Do not add it expecting an FAQ dropdown or a ranking boost.
- Speakable: is not a general-purpose shortcut to AI citations. Check the consuming platform’s current eligibility requirements before investing in it.
- Organization and LocalBusiness: helps establish a clear entity identity for your brand across search and knowledge panels, useful baseline even if its direct ranking impact is modest
- Article: useful for blog content to clearly mark publish date, author, and headline, supporting basic content classification
What doesn’t schema markup do?
Schema doesn’t guarantee rankings, rich results or citations in AI answers. Different search and AI systems read pages differently, so the important information should be visible in the content itself. Treat schema as a description of what the page already shows clearly, never as a way to add meaning the visible content doesn’t support.
- Structured data does not guarantee search rankings, rich results, or citations in AI-generated answers. Evaluate claims of a measurable lift against a named source and its methodology.
- Different search and AI systems process pages differently. Keep important information visible in the article rather than relying on structured data alone.
- The practical takeaway: schema should describe what’s already clearly written and visible on the page, not serve as an attempt to add hidden meaning the content itself doesn’t support
How do you add schema markup in Webflow?
For a single page, paste JSON-LD into the Before </head> tag field in Page Settings, available on all paid Site plans. For schema on every page, like Organization, use the custom code section in Project Settings. For blog posts and other CMS content, build the JSON-LD from CMS fields so each item generates its own schema.
- Page-level: paste JSON-LD into the page’s custom code
Before </head> tagfield in Page Settings, available on all paid Site plans - Site-wide: use the global custom code section in Project Settings for schema that should appear on every page (like Organization schema)
- CMS-driven schema: for blog posts or other dynamic content, build the JSON-LD dynamically using CMS field bindings inside the custom code embed so each item generates its own correct schema automatically rather than needing manual edits per post
How do you validate schema markup?
Test every new piece of schema in Google’s Rich Results Test before you treat it as live. Then check that it matches what visitors can see: schema that describes content the page doesn’t show, such as an FAQ that isn’t on the page, can look manipulative to search engines instead of helpful.
- Always test new schema in Google’s Rich Results Test tool before considering it live
- Check that the schema content actually matches the visible page content; mismatched schema (claiming an FAQ exists that isn’t visibly on the page) risks being seen as manipulative rather than helpful
What schema should a small business site add first?
Start with Organization schema across the whole site, which you set once. Write useful, visible FAQs for readers without expecting Google rich results from them. Add Article schema to blog posts. Then validate everything and check Google’s current documentation before adding any further schema types.
- Organization schema sitewide (set it once, forget it)
- Write useful, visible FAQs for readers; do not expect Google FAQ rich results from marking them up.
- Article schema on blog posts specifically
- Validate supported markup and check current Google documentation before adding more schema types.



