Glossary entry
FAQPage Schema
Definition
FAQPage is a specific schema.org type that marks up a page's Q&A pairs as structured data. Search engines use it to render rich FAQ accordions in search results; AI engines extract the Q&A pairs as ready-to-quote answers.
Origin
Where the term comes from.
FAQPage schema was added to schema.org's vocabulary in 2018 and became a Google rich-result eligible type in May 2019. Initial uptake was strong because the rich-result format (FAQ accordion expanding inline in search results) captured significant visual space and click-through. Google narrowed FAQPage rich-result eligibility in August 2023 — restricting display to authoritative government and health sites — which reduced the standalone Google rich-result use case for most brands. However, the schema type's value increased dramatically with the rise of AI engines in 2023-2026. ChatGPT, Perplexity, Gemini, and Claude all heavily prefer FAQPage-marked content for their answer extraction because the structured Q&A pairs are unambiguous quotation surfaces. By 2026 FAQPage schema is the single highest-leverage AI citation win — even though Google's rich-result display is now limited.
How it works
The mechanism.
FAQPage schema is added via JSON-LD inside a <script> tag. The structure declares the page is a FAQPage and lists each Q&A pair as a Question entity with an acceptedAnswer Answer entity. AI engines parse this JSON during retrieval, treat each Q&A as a discrete answer block, and quote the Answer text verbatim when responding to matching user queries. The Q&A pairs should be substantive (40-200 word answers, not one-liners), match real user query patterns, and contain unique information not buried elsewhere on the page. The visible page content should mirror the schema content — hidden FAQ content (display:none) violates Google's guidelines. Multiple FAQPage schema blocks on the same page are allowed if covering different topical clusters, but most senior implementations use one FAQPage block per page with 6-15 Q&A pairs.
Why it matters
Why this matters in 2026.
FAQPage schema is the highest-leverage AI citation win in 2026. Sites with FAQPage schema get cited by AI engines materially more often than sites without — internal Adsomia client engagement data shows 2-4x AI engine citation lift within 60 days of FAQPage deployment across top 15-20 pages. The schema gives AI engines pre-packaged Q&A pairs they can quote verbatim with attribution, which they prefer over having to extract answers from unstructured prose. Even with Google's reduced rich-result display, the AI engine extraction value alone justifies deploying FAQPage schema on every page with 4+ substantive FAQ pairs. For Kerala SMBs, FAQPage schema deployment on top buyer-intent pages is typically the single highest-ROI 4-hour engineering investment available.
How to check
How to test for it.
Three tests. (1) Open Google's Rich Results Test at search.google.com/test/rich-results. Paste your page URL. If FAQPage schema is present and valid, the test reports 'FAQ' or 'FAQPage' as detected. Errors prevent extraction; warnings reduce confidence. (2) View page source (Ctrl+U), search for 'FAQPage' — should appear inside a <script type='application/ld+json'> block with type:FAQPage and mainEntity array of Question objects. (3) Citation test: ask ChatGPT a question that matches one of your FAQ Q&As verbatim. If your FAQPage schema is deployed and indexed, ChatGPT typically quotes your Answer text directly with attribution. Compare before and after deployment to measure lift.
Common misconceptions
What people get wrong.
Wrong: FAQPage schema is dead because Google removed rich results
Right: Google narrowed Google rich-result DISPLAY in 2023, but FAQPage schema still feeds AI engine extraction strongly. The schema is more valuable in 2026 than in 2022 because AI citation lift outweighs the lost Google snippet display. Don't remove existing FAQPage schema; keep deploying new instances.
Wrong: FAQs hidden in accordions don't count for FAQPage schema
Right: Visible accordion content (display:block by default, collapsible via JS) counts. Hidden content (display:none) violates Google guidelines. Accordions are fine if the FAQ text is server-rendered or hydrated client-side without being initially hidden.
Wrong: Add as many FAQs as possible per page for maximum schema benefit
Right: Quality dominates quantity. 6-15 substantive Q&A pairs (40-200 word answers, real buyer questions) beats 30 padded ones. AI engines downweight FAQPage schema with padded or duplicate content; Google ignores it.
Real-world example
Kerala marketing agency — FAQPage on 18 pages, 4x AI citation lift
An Adsomia client (mid-sized Kerala D2C brand) had 600+ FAQ-formatted Q&A pairs across product pages, but no FAQPage schema deployed anywhere. AI engine citation baseline: 0 mentions across ChatGPT, Gemini, Perplexity for category queries. A 3-week FAQPage schema sprint deployed structured markup on the 18 highest-traffic pages with 8-12 Q&A pairs per page (selected from existing visible FAQ content, no new writing needed). Pages updated: homepage, top 5 product category pages, pricing page, returns/shipping FAQ page, and 10 high-intent product detail pages. Within 6 weeks the brand was cited by Perplexity for 3 buyer queries. By week 10 ChatGPT was citing 7 queries; Gemini 5. By week 16 all four engines (Claude added) had the brand cited for 11+ queries each. Demo + purchase traffic from AI-engine-attributed sources grew from ~3 sessions/day to ~22 sessions/day within 4 months. Total engineering cost of the FAQPage deployment: ~₹95K (one-time). Attributable revenue lift over 12 months following deployment: ~₹1.4 crore. FAQPage schema rarely makes news because it's not the dramatic top-line driver, but it's almost always the highest-ROI single technical SEO investment for AI engine visibility.
Adsomia services
Where this fits in our work.
Common questions
About FAQPage Schema.
How many FAQs per page is optimal?
6-15 substantive Q&A pairs per page. Below 6 and AI engines have too little to extract; above 15 and individual Q&A quality typically drops. Each Q&A should be a real buyer question with a 40-200 word answer containing unique information.
Should FAQs be visible on the page or hidden?
Visible. Hidden FAQ content (display:none) violates Google's guidelines and gets the rich result removed. Accordions are fine — the content is technically visible to crawlers even when collapsed in the UI. Use accordions when space is constrained; render expanded by default when space allows for better engagement.
Do AI engines really quote FAQPage answers verbatim?
Yes. ChatGPT, Perplexity, Gemini, and Claude all extract FAQPage Answer text as direct quotes when responding to matching user queries — often with attribution back to the source page. This is materially different from how AI engines treat unmarked prose (which they paraphrase rather than quote).
Does Google still show FAQ rich results?
Limited. Google narrowed FAQ rich-result display in August 2023 to authoritative government and health sites. Other brands lose the inline accordion snippet but keep the schema's AI engine extraction value, which is now the primary benefit. The schema is more valuable in 2026 than in 2022 despite the Google display change.
Can I add FAQPage schema to a page that doesn't have visible FAQs?
No. Schema content must match visible page content. Adding FAQPage schema without corresponding visible FAQ content violates Google's guidelines and can trigger manual actions. Either add visible FAQ content first, or don't deploy the schema.
How long does FAQPage schema take to show effects?
Google: indexes within days; rich-result eligibility (where applicable) within 2-4 weeks. AI engine citation lift: first measurable changes in 4-6 weeks; material lift in 8-12 weeks; sustained category visibility in 4-6 months. Faster than most SEO investments because AI engines re-crawl frequently.
Related terms
Read next.
Want us to fix this on your site?
Talk to us about a 30-min discovery call. We'll scope what you need + send a written engagement letter inside 48 hours.