What Is FAQPage Schema? The Complete Guide (2026)

Why FAQPage Schema Still Matters in 2026

Even without Google rich results, FAQPage schema continues to deliver measurable value in three areas:

AI Search and LLM Citations

AI search platforms — Google AI Overviews, ChatGPT Search, Perplexity, and Claude — actively parse structured data when forming answers. When a user asks a direct question, these systems look for the most machine-readable, authoritative answer available. A properly marked-up FAQPage gives AI systems structured, extractable question-answer pairs rather than raw prose they must interpret themselves. This makes your content significantly more likely to be cited as a direct answer.

Voice Search

Voice assistants (Google Assistant, Siri, Alexa) rely heavily on structured data to form spoken responses. FAQPage markup turns your Q&A content into pre-packaged answers that voice systems can read verbatim. A concise, well-structured Answer.text field is effectively a script for a voice response.

Knowledge Graph and Entity Understanding

FAQPage schema helps Google and other engines understand what your page is authoritative about. Even when the schema doesn't trigger a visual rich result, it contributes to how your site is understood at the entity level — influencing Knowledge Panel content, related searches, and topical authority signals.

FAQPage vs QAPage: Which One to Use?

Schema.org defines two distinct types for question-and-answer content, and they are not interchangeable:

Using FAQPageon a user-submitted Q&A page (where different users post different answers) violates Google's guidelines. The correct type for that format is QAPage.

Required Properties

FAQPage schema has a three-level nested structure: the page type wraps a list of questions, and each question wraps its answer. Every level has required fields.

Level 1 — FAQPage

Level 2 — Question (inside mainEntity)

Level 3 — Answer (inside acceptedAnswer)

Supported HTML Tags in Answer Text

The Answer.text field supports a limited set of HTML tags. Any tags outside this list are unsupported — Greadme warns when it detects them:

h1, h2, h3, h4, h5, h6, br, ol, ul, li, a, p, div, b, strong, i, em

Tags like table, img, span, script, and style are not in the supported list. Use plain text or the allowed HTML tags only.

Importantly, all content marked up in the schema must also be visible to the user on the page. You cannot mark up hidden FAQ content that is collapsed or off-screen — Google requires the questions and answers to be accessible in the rendered page.

Complete Implementation Example

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does standard shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard shipping takes 3–5 business days. Orders placed before 2 PM ship the same day."
      }
    },
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We accept returns within 30 days for unused items. Start a return at <a href='https://example.com/returns'>example.com/returns</a>."
      }
    },
    {
      "@type": "Question",
      "name": "Do you ship internationally?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes, we ship to 40+ countries.</p><ul><li>Canada/Mexico: 5–8 days</li><li>Europe: 7–14 days</li><li>Asia-Pacific: 10–21 days</li></ul>"
      }
    }
  ]
}

Content Rules and Disqualifiers

Even though FAQ rich results are deprecated, observing these rules keeps your schema aligned with how AI systems and future Google features may use it:

6 Common FAQPage Schema Mistakes

1. Using suggestedAnswer Instead of acceptedAnswer

suggestedAnswer is valid on Schema.org but it signals a speculative or community-submitted answer — appropriate for QAPage, not FAQPage. For curated FAQ pages, always use acceptedAnswer to signal the definitive, site-authored answer.

2. Marking Up Hidden Accordion Content

A common pattern: the FAQ is rendered as a collapsed accordion where answers are only shown after a click. If the answer text is not present in the HTML at page load (i.e., it is injected by JavaScript only after interaction), it may not be visible to crawlers. Ensure answers are in the initial DOM, even if visually hidden behind an accordion — use CSS for the collapse, not JavaScript content-injection.

3. Missing @type on Question or Answer Objects

The @type must be set on every level: FAQPage, Question, and Answer. Omitting "@type": "Question" or "@type": "Answer" from the nested objects is a common oversight. Greadme warns for missing types at each level.

4. Using FAQPage on a Community Q&A Page

If your page allows multiple users to post answers to a question — and different users may have contradicting answers — you need QAPage, not FAQPage. Using the wrong type tells search engines your page is something it is not, which can result in incorrect AI citations.

5. Short or Vague Questions

Questions like "Shipping?" or "Returns?" are too short and vague. Greadme warns for question text under 10 characters. Write questions the way users actually phrase them: "How long does standard shipping take?" — this also makes the content more likely to match voice search and AI query patterns.

6. Using Unsupported HTML Tags in Answer Text

Tags like <table>, <img>, or <span> are not in the supported HTML list. Greadme detects unsupported tags and warns. Strip them out or replace with supported equivalents (<ul>/<li> for tables of simple items, plain text for images).

FAQPage Schema and AI Search Visibility

The deprecation of Google FAQ rich results does not diminish the value of FAQPage schema for AI-driven search. AI Overviews, ChatGPT Search, and Perplexity parse structured data as high-confidence, machine-readable content. A well-formed FAQPage with clear, concise Answer.text values gives these systems pre-packaged answers they can extract and cite directly — rather than inferring meaning from surrounding prose.

For AI citation specifically, the quality of the Answer.text matters as much as the structure. Write answers that are self-contained: a reader (or AI) should be able to understand the answer without reading the question. Aim for 2–5 sentences per answer — long enough to be complete, short enough to be extracted cleanly as a snippet.

How to Validate Your FAQPage Schema

Paste your page URL into Greadme to validate your FAQPage schema. Greadme checks the required three-level structure (FAQPage → Question → Answer), verifies that name and text meet minimum length requirements, detects unsupported HTML tags in answer text, flags promotional content in questions and answers, and shows the Google deprecation status so you have full context on what the schema currently achieves.