What Is FAQ Schema (FAQPage)? Markup for Question-Answer Content

FAQ schema — the schema.org FAQPage type — marks up a page's question-and-answer pairs in machine-readable form, with each question as a Question entity carrying an acceptedAnswer. It tells any consuming system precisely where the questions are and which text constitutes the complete answer to each, removing the extraction guesswork from the most answer-shaped content format on the web.

What changed in August 2023?

Google dramatically restricted the FAQ rich result, announcing that expandable Q&A snippets in search listings would appear only for "well-known, authoritative government and health websites." For everyone else, the SERP feature — once a reliable way to occupy extra result real estate — effectively disappeared. Many teams read that as "FAQ schema is dead" and stripped the markup. That conclusion confuses one consumer's display feature with the markup's value: Google's own documentation still parses FAQPage, and Google was never the only reader.

Why does FAQPage still matter for AI parsing?

Question-answer pairs are the native shape of AI answers. When a grounding pipeline fetches your page, FAQPage JSON-LD hands it pre-segmented, self-contained Q&A units — each answer already scoped to its question, no boundary detection needed. That aligns exactly with how answer engines chunk and quote content. The structure also mirrors the conversational queries users actually type into ChatGPT and Perplexity, so a well-marked FAQ section is simultaneously extraction-friendly and query-matched. The GEO literature consistently finds that content structured as direct answers gets surfaced more; FAQPage is that structure made explicit.

How should it be implemented now?

Three rules keep it honest and useful. First, parity: mark up only Q&As visible on the page, verbatim. Second, substance: each answer should be a complete 2–4 sentence response containing a concrete fact, not a teaser pointing elsewhere — a self-contained passage an engine can quote whole. Third, placement: FAQs belong on pages where the questions genuinely arise (product pages, glossary entries, guides), not as a bolt-on section repeated sitewide. Combine the markup with question-shaped H2 headings in the visible content so the human-readable and machine-readable layers reinforce each other — the pairing at the heart of any solid AEO checklist.