Mar 2, 20266 min read
FAQ Schema Markup: How to Add It in 2026
FAQPage JSON-LD example, how to implement it on any site, and the eligibility rules Google enforces in 2026.
FAQPage schema used to win you a giant rich result on every page. Google has tightened the rules since 2023 — now FAQ rich results only appear for authoritative health, government, and well-known sites. But the schema is still worth adding: it powers AI Overviews, ChatGPT citations, and voice answers.
The schema
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "How long should a meta description be?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Aim for 50–160 characters. Shorter than 50 and Google ignores it; longer than 160 and it gets truncated."
}
}]
}How to add it
- Embed the JSON-LD inside a <script type="application/ld+json"> tag in your page <head>
- Make sure every Q&A in the schema is also visible on the page — hidden FAQs violate Google's guidelines
- Validate with Google's Rich Results Test before shipping
Common mistakes
- Schema Q&A doesn't match the on-page text — instant disqualification
- Adding FAQPage to category or product pages — should be on a real FAQ page or a content page with a clear Q&A section
- Forgetting the <script> tag wrapper — JSON alone doesn't validate
When to use FAQPage vs HowTo vs QAPage
- FAQPage — multiple unrelated questions on one page
- QAPage — single user-asked question with multiple answers (forum posts)
- HowTo — step-by-step instructions with images
Run a free SEO audit on your site
No signup, no credit card. Get prioritized fixes in 30 seconds — then explore the full free toolkit.
Frequently asked questions
Will FAQ schema get me rich results?
Probably not on its own. But it helps with AI Overviews, ChatGPT citations, and voice search — all growing channels.
How many FAQs is too many?
Quality over quantity. 5–10 well-written ones beat 30 thin ones.