FAQ schema: FAQPage markup and rich results
FAQ schema is structured data that labels a genuine list of questions and answers on a page as an FAQPage. It helps engines understand the Q&A, and at times display it as an expandable rich result beneath your listing.
Last updated
What FAQPage markup is
FAQPage is a schema type that describes a set of questions, each with its answer, contained on a page. Adding it tells an engine that this section is a structured set of Q&A rather than ordinary prose, which it can then handle intelligently.
It is usually implemented in JSON-LD alongside the visible FAQ, mirroring exactly the questions and answers a visitor can read. The markup describes what is on the page; it does not create content that is not shown.
The rich result and its caveats
When shown, FAQ rich results appear as expandable questions under a search listing, taking up more space and answering common questions in place. That prominence can lift click-through and pre-answer objections before a visitor even lands.
But eligibility and display have changed over time, and search engines have narrowed when FAQ rich results appear. The markup remains useful for machine understanding regardless, so it is worth adding for correctness even when the visual result is not guaranteed.
When to use it honestly
FAQ schema suits pages with a real, useful set of questions your audience actually asks — a product page’s common queries, a service’s eligibility questions, a guide’s follow-ups. The questions should be genuine and the answers substantive.
It is misused when questions are invented purely to game a rich result, or when the marked-up Q&A does not appear visibly on the page. Both break the rule that markup must match visible content, and both risk penalties rather than gains.
How Kirti approaches this
Kirti is being built to generate FAQ sections from the real questions in a brand’s topic — visible on the page and mirrored in valid FAQPage markup — as part of drafting content, with the team approving both the questions and their answers before publishing.
The agent is in active development and not yet generally available; FAQPage rules and rich-result eligibility shift over time, so validate against current guidance whatever tool you use.