Definition
FAQ Schema refers to the implementation of the FAQPage type from the Schema.org vocabulary, embedded in a web page as a JSON-LD script block, to annotate a set of question-and-answer pairs as a machine-readable frequently asked questions section. When correctly implemented and validated, FAQPage structured data makes the annotated Q&A content eligible for FAQ rich results in Google Search — expandable accordion-style panels displayed directly in the Search Engine Results Page (SERP) beneath the page’s blue-link listing — and increases the probability of individual Q&A pairs being cited in AI-powered answer features including Google AI Overviews.
The underlying type — schema.org/FAQPage — is a subtype of WebPage within the Schema.org hierarchy, introduced to the vocabulary to address the common pattern of dedicated FAQ pages and inline FAQ sections on product, service, and informational pages. Each question is represented as a Question entity with a name property (the question text) and an acceptedAnswer property containing an Answer entity whose text property holds the answer content.
How It Works
The canonical implementation of FAQ Schema uses JSON-LD (JavaScript Object Notation for Linked Data), the format recommended by Google’s Search Central documentation. The structured data block is inserted as a <script type="application/ld+json"> element in the HTML <head> or <body> and does not require any modification to the visible page HTML.
A minimal but valid FAQ Schema block follows this structure: a root object of @type: "FAQPage" containing a mainEntity array where each element is an object with @type: "Question", a name property containing the question string, and an acceptedAnswer object with @type: "Answer" and a text property containing the answer string. Google’s guidelines specify that the question and answer text in the structured data must match the visible text on the page — marking up content that does not appear in the page’s rendered HTML violates Google’s spam policies for structured data, as detailed in the Search Central documentation.
Google’s Rich Results Test, available at search.google.com/test/rich-results, and the URL Inspection tool in Google Search Console validate FAQ Schema implementations and report errors or warnings. Common validation issues include missing required properties (name, acceptedAnswer), answers that are too short or consist only of a URL, and markup applied to content that is not a genuine FAQ format (e.g., using FAQPage on a page with a single question).
Google updated its FAQ rich results policy in September 2023, restricting the feature to pages from “well-known, authoritative government and health websites” for most queries, with FAQ rich results for general content pages appearing less frequently in SERPs. Despite this policy change, FAQ Schema retains value as a signal to both traditional search ranking systems and AI answer engines that the page contains structured, definitional Q&A content.
Where You Encounter It
FAQ Schema is implemented on any page whose content includes question-and-answer pairs that the publisher wants to surface in search features. Common use cases include:
Service pages with FAQ sections: E-commerce, SaaS, and service businesses commonly append FAQ sections to product and service pages, answering common pre-purchase questions. FAQ Schema markup on these sections made the accordions directly visible in SERPs prior to Google’s September 2023 policy restriction, and continues to provide structured signals to AI answer systems.
Support and help centre articles: Documentation portals from companies including Google, Microsoft, Atlassian, and Zendig use FAQPage markup on support articles to increase visibility in informational query results and to provide structured content for AI assistants integrated with their support workflows.
Glossary and definitional pages: Glossary entries structured as a primary definition followed by Q&A sub-sections benefit from FAQ Schema by providing machine-readable hooks for individual concepts within the page. This is particularly relevant for AI Overviews citation: an AI Overview answering a specific question may cite the FAQ-annotated sub-section of a page rather than the page as a whole.
Contest and competition pages: Contest organisers frequently include FAQ sections addressing eligibility, voting rules, prize details, and confirmation processes. FAQ Schema on these pages provides both search visibility and a structured format for AI systems that may answer user queries about the contest.
Practical Examples
A contest platform adds an FAQ section to its email confirmation vote page, covering questions such as “How long does the confirmation link remain valid?”, “What should I do if I did not receive the confirmation email?”, and “Can I vote for multiple entries in the same contest?”. The publisher implements FAQPage JSON-LD with three Question / Answer pairs. After validation via the Rich Results Test, Google Search Console confirms FAQ rich result eligibility. In subsequent weeks, Google Search Console’s Search Appearance report shows impressions attributed to FAQ rich results for queries related to contest voting confirmation.
An SEO team auditing a contest services website discovers that the existing FAQ sections have questions and answers in an HTML definition list (<dl>/<dt>/<dd>) format visible on the page but no accompanying JSON-LD FAQPage markup. Adding the structured data block does not require any visible page changes — only the addition of the <script type="application/ld+json"> block in the <head>. Post-implementation, the structured data begins contributing to the page’s eligibility as a citation source in Google AI Overviews for related definitional queries.
Related Concepts
FAQ Schema is part of the broader Schema.org vocabulary, which also includes DefinedTerm (for glossary entries), HowTo (for step-by-step instructions), and Service (for commercial offerings) — each targeting different rich result formats and machine-readability goals. The probability of FAQ-annotated content being cited in AI Overviews is influenced by the page’s E-E-A-T signals: authorship, primary source citations, and demonstrated expertise all factor into AI Overview source selection alongside the structural signals provided by structured data markup.
