Webflow schema markup: Article, breadcrumbs and visible FAQs
%20(1).avif)
Written by Derrick KityoAdd accurate JSON-LD to Webflow articles, connect the author and breadcrumbs, and generate FAQ markup from visible answers.
Schema markup describes the entities and content a page actually contains. For a Webflow article, start with a truthful Article or BlogPosting, its author, representative image and dates, then add breadcrumb information that matches the page hierarchy. Schema does not guarantee rankings or AI citations.
Start with visible facts
Write the article and identify its preferred public URL first. Use the visible headline and author, the real publication date and an honest modification date. The image should represent the article and be accessible. Do not invent reviews, credentials or results to fill a schema property.
Use one coherent article entity
Give the article a stable identifier based on its canonical URL, and use the same URL for mainEntityOfPage. Use a Person for a human author and an Organization for the publication where appropriate. Link the author to an about or profile page that identifies the person.
Generate markup from content fields
Use the same CMS fields for the visible title, summary, image and JSON-LD. Serialize data safely rather than manually inserting unescaped quotes into a template. Check one realistic page and an edge case with punctuation, long text and missing optional fields before applying the template broadly.
Add a breadcrumb hierarchy
A practical article path is Home, Insights and the article. Use ordered ListItem entries with stable public URLs, and align the hierarchy with the navigation readers see. Breadcrumb schema does not replace helpful internal links.
Want to apply this to your own website or app?
Tell me what you are working on and where it is getting stuck. I will help you turn the useful ideas into shipped work.
Keep FAQ answers visible and identical
Store each question and answer together. Render that data at the bottom of the article and use it verbatim for FAQPage mainEntity and acceptedAnswer. Do not mark up hidden marketing claims or questions whose answers are absent from the page.
Understand the current Google feature limits
Google stopped displaying FAQ rich results from 7 May 2026. FAQPage remains a schema.org description of question-and-answer content; it is not a shortcut to a Google enhancement. Google also says AI Overviews and AI Mode require no special schema. Clear, reliable content remains essential.
Validate syntax and meaning
Check that the JSON parses, the types and properties fit the content and all important URLs are correct. Use the relevant validator and Google’s Rich Results Test for supported Google features. A successful technical test does not prove every factual claim or guarantee that a feature will appear.
Maintain the template
When content changes, update the visible material and its corresponding fields together. Keep dates honest and remove retired promises from tutorials. Consult Google’s Article documentation, AI search guidance and the documentation changelog.
Tags
SEO & AI searchFrequently asked questions
Do I need special schema for AI Overviews or AI Mode?
Google says no special schema or extra technical optimisation is required for those features. Keep useful content crawlable, accurately structured and supported by clear text and evidence. Inclusion and citations are not guaranteed.
What makes an article easier to answer questions from?
State a clear answer near the start, define the scope and explain the evidence and exceptions. Use descriptive headings, original examples and primary sources where claims need support. The visible content should remain understandable without relying on schema.
Does FAQPage schema guarantee an AI citation?
No. It describes visible question-and-answer content, but does not guarantee a citation or ranking. Google retired FAQ rich results in May 2026. Add useful FAQs for readers and keep the schema text identical to their visible answers.
.jpg)
