Google's rich results engine shows FAQ accordions directly in search results when it finds FAQPage schema.org markup on your page. Most sites ignore it. LLMs (Claude, ChatGPT, Perplexity) crawl the same pages and cite FAQ content with much higher confidence when it's wrapped in structured data — they can distinguish the question from the answer with certainty. One markup layer, two wins.
What Is FAQPage Schema?
FAQPage is a schema.org type that marks up a list of question-answer pairs. Each pair gets wrapped in mainEntity objects with @type: Question and acceptedAnswer properties. Google parses this and either shows the FAQ as an accordion in the SERP or feeds it into its AI Overview answers. LLMs parse it to cite specific answers more confidently because the structure is explicit.
Without FAQPage schema, crawlers infer Q&As from heading structure and heuristics — slow, unreliable, easily confused. With schema, the boundary is crystal-clear: this text is a question, that text is the answer, they belong together.
Why FAQPage Matters Now
In 2025–2026, Google's AI Overview (generative results shown above the traditional organic links) pulls answers from structured data first. If your FAQ content has FAQPage schema, Google surfaces it directly in the Overview. If it doesn't, Google has to infer or skip your FAQ entirely.
The LLM layer is where most sites miss the boat. When Claude or ChatGPT cites your FAQ, they say "According to [your site], the answer is…" (with the answer pulled cleanly from schema) versus "The site mentions…" (with the answer inferred, truncated, or misquoted). The schema version reads more authoritative and actually drives more click-through back to your site.
The Architecture: FAQ Block → JSON-LD Output
Velocity X parses any `
` + paragraph pattern (or explicit FAQ component) and auto-generates FAQPage JSON-LD at build time. The output looks like this:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQPage schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQPage marks up Q&A pairs so Google and LLMs can parse them with certainty..."
}
}
]
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQPage schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQPage marks up Q&A pairs so Google and LLMs can parse them with certainty..."
}
}
]
}This gets embedded in the page `
` alongside the visible FAQ section. Crawlers read the JSON-LD; users see the styled Q&As. One source, two outputs.Validation & Real-World Impact
Paste your FAQ page URL into Google's Rich Results Test and you'll see FAQPage schema parse cleanly with a live preview of how Google will display it in search. No errors = you're shipping structured data correctly.
In practice: FAQPage pages rank higher CTR in Google search (10–15% boost), appear in AI Overviews consistently, and get cited by LLMs with full context. A site without FAQPage schema on the same content ranks lower and gets cited tentatively ("the site mentions" rather than "the site answers").
Frequently Asked Questions
Do I need FAQPage schema to rank for FAQ queries?
No. Google ranks on relevance and authority. But schema unlocks rich results and AI Overview placement, which boost visibility and CTR by 10–20%. You need schema to convert.
What's the difference between FAQPage and FAQ rich results?
FAQ rich results are the accordion UI you see in Google search. FAQPage is the schema markup that generates them. You need the schema to get the rich result.
Can I hand-code FAQPage instead of auto-generating it?
Yes, but every time you add or edit an FAQ, you have to update the JSON-LD manually. Velocity X automation removes that friction — write the visible FAQ once, schema generates automatically.
How many FAQs should I include?
Google recommends 2–10. More than 10 and the accordion becomes unwieldy; fewer than 2 and schema has minimal impact. Sweet spot is 5–7 per page.
Does FAQPage schema improve my ranking on Google?
Not directly. Google's ranking algorithm doesn't favour schema. But schema unlocks rich results and AI Overview placement, which compound into higher visibility and authority signals over time.
Will better FAQPage schema improve LLM citations?
Yes, measurably. LLMs crawl pages with comprehensive, valid schema more thoroughly and cite answers with full context rather than inferred snippets. Schema is a trust signal that pays off in citation confidence.
The Bottom Line
FAQPage schema.org markup is table-stakes in 2026 if you want to compete in Google's AI Overview and earn confident LLM citations. Define your FAQs once in HTML or MDX, let the schema generator output JSON-LD automatically, and validate in Google Rich Results Test. The gap between a FAQ page with schema and one without is now 10–20% in CTR plus higher citation authority from every major LLM. Ship FAQ schema, win twice.