How does FAQ Schema differ from DefinedTerm Schema?

DefinedTerm marks the page as defining a concept (concept-first); FAQPage marks question-and-answer pairs (interaction-first). Many pages benefit from shipping both: DefinedTerm for the canonical concept, FAQPage for common queries about it.

How many FAQ entries should a page have?

Three to five is the practitioner sweet spot. Fewer means thin coverage; more starts to look stuffed. Each Q should be a real query someone might issue, not a manufactured marketing pitch dressed as a question.

/terms/faq-schema · 4 min read · intermediate

FAQ Schema

FAQ Schema (FAQPage) is the schema.org JSON-LD type for marking up question-and-answer pairs on a page, commonly used to help search engines and other systems parse visible Q&A content in a machine-readable format. Google fully deprecated FAQ rich results on May 7, 2026; the markup remains valid for machine-readability purposes.

Citation status

ChatGPT·PerplexityClaudeCopilotGemini

Last checked 2026-06-16

What is FAQ Schema?

FAQ Schema, formally FAQPage on schema.org¹, is the JSON-LD vocabulary for marking up question-and-answer pairs. Each FAQPage contains a mainEntity array of Question objects, each with a name (the question) and an acceptedAnswer (an Answer object with text)². Practitioners commonly observe that FAQPage-structured Q&A is easier for AI engines to extract verbatim than equivalent free-form Q&A in prose; whether the independent effect comes from the FAQPage markup itself or from the underlying question-headed structure has not been isolated by public study.

Minimum viable FAQPage JSON-LD

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Google still show FAQ rich results in search?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Google fully deprecated FAQ rich results on May 7, 2026. The schema vocabulary remains valid and may still be parsed by AI engines for citation purposes."
      }
    }
  ]
}

Ship this inside a <script type="application/ld+json"> block in the <head> of the page that contains the matching prose Q&A.

Status in 2026

Repurposed for AI search. Google removed FAQ rich results from non-government / non-health pages in August 2023, and on May 7, 2026, fully deprecated them for all remaining sites (including the previously-protected government and health categories)³. Google is retiring FAQ support in the Rich Results Test in June 2026 and in the Search Console API in August 2026. The schema vocabulary itself remains valid. AI Overview, ChatGPT, Perplexity, and Claude may still parse FAQPage markup for citation purposes, though vendor confirmation that any specific engine privileges this markup as a citation ranking signal is absent. By 2026, the practical reason to ship FAQ schema is:

Underlying content structure: question-headed, scoped, self-contained answer blocks are good for human readers and machine readability regardless of schema.
Possible AI citation parsing: AI engines may use the structured Q&A as an extraction aid, though the empirical weight is not vendor-documented.

Ship FAQPage on pages with a real Q&A section. Do not ship it expecting SERP visual treatment; that is gone.

Live example, this entry's own citation behavior: in a 2026-05-17 ChatGPT search probe for the query "definition of FAQ Schema", this page surfaced in the expanded sources panel as relevant context (with a "Yesterday" indexing timestamp) but was not selected for the answer body's primary citations. ChatGPT cited Google Search Central + schema.org + several industry blogs instead. This illustrates a recurring AI-search citation pattern: when vendor-canonical documentation exists for a concept (Google + schema.org both publish FAQPage documentation), AI engines tend to retrieve third-party glossary entries but prefer the vendor sources for citation slots. The practical implication for GEO programs working in vendor-canonical territory: earning citation requires unique perspective, measurement data, or coverage angle the vendor docs don't supply; clarity of prose alone will not displace the vendor's primary source. Full evidence in internal evidence files.

How to apply

FAQ schema no longer earns Google rich results (the visual SERP treatment was first restricted to authoritative government and health sites in August 2023, then removed entirely for all sites on May 7, 2026)³. Whether AI engines specifically privilege FAQPage markup as a citation input is not vendor-documented; practitioners report seeing it parsed, but no public study has isolated its causal effect. Treat the markup as a structural/readability aid that may have AI citation upside, not as a SERP feature. The practical pattern:

Reverse-engineer your top organic queries into question-form FAQ: pull your GSC top 20 queries that surface this page, rewrite each as a question, then write a 40–60 word answer (common practitioner heuristic for citation-friendly density, though optimal length varies). Three to five questions per page is the typical range.
Match the prose Q&A on the page to the JSON-LD verbatim: Google's spec requires the JSON-LD content to be visible on the page. Don't ship "secret" FAQ schema that doesn't match what users see; that's penalized in classic SEO.
Validate then crawl-test (act fast on the validator): use the Rich Results Tester while it still accepts FAQ (Google is retiring FAQ support in the Rich Results Test in June 2026); after that, fall back to the schema.org validator. Then in GSC, run URL Inspection → Test Live URL → check the rendered JSON-LD matches what you shipped. Client-side rendering quirks occasionally break the round-trip.

What to skip: shipping FAQ schema on pages without a corresponding visible Q&A section. The "invisible markup" pattern violates Google's structured-data visibility policy and can trigger a manual action, and AI engines tend to ignore Q&A blocks that don't appear in the page's visible text.

How it relates to other concepts

Sibling schema type to DefinedTerm, HowTo, Article.
Direct implementation of the answer block structural pattern in machine-readable form.
Companion to AI Overview citation. Practitioners report FAQ-marked answers being cited, though no public study isolates this from confounding content-level factors (clear question phrasing, scoped answers, authoritative tone).
Commonly-discussed input for Answer Engine Optimization across answer surfaces; empirical weight relative to content-level signals is contested.

Schema.org FAQPage type specification. schema.org/FAQPage. ↩
Google Search Central: FAQPage structured data implementation guide. developers.google.com/search/docs/appearance/structured-data/faqpage. ↩
Two-phase Google deprecation of FAQ rich results. Phase 1 (August 8, 2023): Google Search Central announced rich results would be restricted to "well-known, authoritative government and health websites" only; all other sites lost the visual SERP treatment. The rollout completed within the following week. Primary source: Google Search Central Blog, John Mueller, "Changes to HowTo and FAQ rich results," August 8, 2023 (developers.google.com/search/blog/2023/08/howto-faq-changes). Phase 2 (May 7, 2026): full deprecation for all sites including the previously-protected government and health categories; Rich Results Test FAQ support retired in June 2026; Search Console API FAQ rich-result data removed in August 2026. The schema vocabulary itself remains valid, and Google has stated it will continue to use FAQ structured data to better understand pages even without the rich-result rendering. Primary documentation: Google's FAQPage structured data guide (developers.google.com/search/docs/appearance/structured-data/faqpage), the canonical destination, updated to reflect deprecation status. Industry coverage with explicit Google quotes: Search Engine Journal, "Google Drops FAQ Rich Results From Search" (searchenginejournal.com/google-drops-faq-rich-results-from-search/574429) and Search Engine Land, "Google to no longer support FAQ rich results" (searchengineland.com/google-to-no-longer-support-faq-rich-results-476957). ↩ ↩²

Part of Schema cluster· editorial cluster, not a semantic link

Also in this cluster: Article Schema · BreadcrumbList Schema · DefinedTerm schema · HowTo Schema · JSON-LD

Mentioned in· auto-generated from other terms' related lists

FAQ

Does Google still show FAQ rich results in search?: No. Google fully deprecated FAQ rich results on May 7, 2026 (the visual SERP treatment was first restricted to authoritative government and health sites in August 2023, then removed for all sites including those two categories on May 7, 2026). The schema vocabulary remains valid, and AI Overview, ChatGPT, Perplexity, and Claude may still parse it for citation purposes, though no public study has isolated FAQPage's causal effect on AI citation.
How does FAQ Schema differ from DefinedTerm Schema?: DefinedTerm marks the page as defining a concept (concept-first); FAQPage marks question-and-answer pairs (interaction-first). Many pages benefit from shipping both: DefinedTerm for the canonical concept, FAQPage for common queries about it.
How many FAQ entries should a page have?: Three to five is the practitioner sweet spot. Fewer means thin coverage; more starts to look stuffed. Each Q should be a real query someone might issue, not a manufactured marketing pitch dressed as a question.

Sources & further reading

New terms shipped that week, plus one observation from the AI-citation tracker.

More about what you'll get

Last fact-checked 2026-05-18. Spotted an error or stale claim? See editorial methodology.

Changelog (6 entries)

2026-05-30: Added the primary-source URL for the August 2023 Google Search Central blog post 'Changes to HowTo and FAQ rich results' to the deprecation footnote (the prior text described the August 2023 restriction without linking to the announcement post itself). The footnote now cites both deprecation phases by primary source: the August 2023 restriction post and the May 7, 2026 full-deprecation notice on Google's FAQPage structured-data documentation page.
2026-05-20: ChatGPT citation. A 2026-05-20 probe for 'FAQ Schema' returned this entry as the 4th source in a panel of ~10 ('FAQ Schema | GEO Glossary, May 16 2026'). Notable: surfaced despite Google's May 7 2026 deprecation of FAQ rich results (the entry's lead context); ChatGPT included us regardless. citationStatus.chatgpt from not-cited to cited. Part of a same-day seven-new-citation ChatGPT sweep; full probe evidence preserved internally.
2026-05-18: Softened the lead description from 'enabling AI engines to extract Q&A content as cite-able answer blocks' to 'commonly used to help systems parse Q&A content in a machine-readable format,' aligning with the already-hedged Status framing. Hedged the 'AI engines parse FAQPage more reliably than free-form Q&A in prose' comparative claim, because no public study isolates the structured-vs-prose effect. Source footnote replaced with a specific URL set.
2026-05-17: Surfaced in the ChatGPT search sources panel for 'definition of FAQ Schema' (with a 'Yesterday' indexing timestamp) but not in the answer's primary source list; ChatGPT cited Google Search Central + schema.org + 3 industry blogs instead. A recurring pattern: where vendor-canonical docs exist (Google and schema.org both publish FAQPage docs), engines surface third-party glossary entries in retrieval but prefer the vendor sources for citation. citationStatus.chatgpt unchanged (the binary does not model 'surfaced but not cited').
2026-05-16: Added Google's full FAQ rich results deprecation on May 7, 2026 (visual SERP treatment removed for all sites, including previously-protected government and health categories); flagged that Rich Results Test FAQ support retires June 2026 and Search Console API support retires August 2026; softened claims about AI engines citing FAQ-marked content.
2026-05-13: Initial publish