FAQ Schema: Complete Reference

By Amit Patel

FAQ schema (FAQPage) marks up a list of question-and-answer pairs so search engines and AI can read them as structured Q&A — but the rich result it once produced is now restricted to a narrow set of authoritative sites. Understanding FAQ schema in 2026 means separating two things: the visible rich result (mostly gone for regular sites) and the structured data itself (still useful for AI and understanding). This reference covers both, plus the exact markup and the mistakes that trigger warnings.

What FAQ Schema Does Now

FAQPage schema still validly describes Q&A content, but since Google’s 2023 change the expandable-answer rich result appears only for well-known, authoritative government and health sites — for everyone else the markup is valid yet produces no visible dropdown.

So the honest framing is: add FAQ schema for its structural and AI value, not to chase a rich result you almost certainly will not get. This is the same “valid but restricted/retired” situation as HowTo, and it is why this cluster tells you a type’s real status rather than just its syntax.

Who Still Gets the Rich Result

Google limited FAQ rich results to authoritative sites — in practice government and health organizations — so most commercial and editorial sites no longer see the FAQ dropdowns even with perfect markup.

Do not spend effort trying to “qualify”; the restriction is about site type, not markup quality. If you are not a government or health authority, assume no dropdown and value the markup for the reasons below. The FAQPage type this site adds to its own articles follows exactly this logic — present for structure and AI, not for a promised rich result.

Why It Still Helps AI

Structured Q&A is easy for AI systems and search features to extract and reuse — clear question-answer pairs map directly onto the way assistants and AI Overviews assemble answers, which is a genuine reason to keep the markup.

It also reinforces the on-page FAQ content and keeps your answers concise and quotable, the same source-worthiness the GEO & AEO pillar emphasizes. Generate valid FAQPage markup quickly with our free FAQ schema generator.

Structure and Rules

A FAQPage contains a mainEntity array of Question objects, each with a name (the question) and an acceptedAnswer Answer with text. The Q&A must be visible on the page and non-promotional.

Two rules matter most: the questions and answers in the markup must match visible page content, and FAQ schema is for informational Q&A, not advertising or user-submitted questions with multiple answers (that is QAPage). Mismatched or promotional FAQ markup can trigger a manual action. Validate with the Rich Results Test.

Example Markup

A minimal FAQPage (shown as code):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does FAQ schema still show dropdowns?",
    "acceptedAnswer": { "@type": "Answer", "text": "Only for authoritative government and health sites since 2023." }
  }]
}
</script>

See JSON-LD vs Microdata for the format.

Frequently Asked Questions

Does FAQ schema still show rich results?

Only for authoritative government and health sites since Google’s 2023 restriction. Most commercial and editorial sites no longer get the expandable-answer dropdowns, even with valid markup. The schema still has structural and AI value.

Should I still add FAQ schema?

Often yes — for the AI-extraction and understanding benefits, and to reinforce concise on-page answers. Just do not add it expecting the old rich result, and only mark up genuine, visible, non-promotional Q&A.

What is the difference between FAQPage and QAPage?

FAQPage is for a list of questions with single authoritative answers written by the site. QAPage is for a single user-submitted question with potentially many community answers (like a forum). Use the one that matches your content.

Can FAQ schema get me penalized?

It can if misused — marking up promotional content, questions not visible on the page, or advertising as Q&A can trigger a structured-data manual action. Keep it to genuine, visible, informational Q&A and you are fine.

The Bottom Line

FAQ schema is a type whose value shifted rather than disappeared: the rich result is gone for most sites, but structured Q&A remains genuinely useful for AI and understanding. Add it to real, visible FAQ content for those benefits — not for a dropdown — and keep it honest, following the status-aware approach across the schema cluster.