FAQ Schema

FAQ schema is FAQPage structured data — JSON-LD embedded in a page marking its questions and answers so machines can parse them as Q&A pairs (this glossary's own pages carry it; the SCHEMA-MARKUP entry covers the wider family). Its famous payoff was the expandable FAQ rich result in Google's SERPs — and that era largely ended in August 2023, when Google restricted FAQ rich results to authoritative government and health sites. The markup outlived its dropdown: machine-legible Q&A still feeds search understanding and the AI surfaces that now answer questions directly.

The markup itself is simple: an FAQPage entity whose mainEntity lists Question items, each with an acceptedAnswer — emitted as JSON-LD, mirroring visible on-page content exactly (Google's policies require the marked-up Q&A be present to users; invisible-FAQ tricks were the spam that helped earn the 2023 demotion, alongside the dropdowns' sprawl across every commercial SERP). The 2023 change rewrote the ROI math, not the practice: for most sites the rich-result real estate is gone, so FAQ schema's remaining returns are quieter — clean machine extraction of your answers (the structure AI assistants and answer engines parse when deciding what to cite), eligibility wherever Q&A structure feeds other features, and the discipline benefit that writing true 40-60-word answers imposes on content (the answer-shaped writing this site's build spec enforces for exactly that reason). The craft rules survived intact: mark up genuine FAQs only (the FAQ content has to deserve existence — the strip-test logic of every schema type), match visible text, keep answers self-contained (an answer that depends on the page around it extracts as nonsense), and never schema-stuff pages whose 'FAQs' are keyword bait wearing question marks.

FAQ schema matters now as answer-engine plumbing rather than SERP decoration — sites whose content gets cited by AI surfaces, and anyone whose pages genuinely answer questions, benefit from machine-legible Q&A. It matters as housekeeping at audit time: pre-2023 implementations chasing dropdowns deserve review (keep the honest markup, retire the bait). The discipline is content-first — real questions users ask, self-contained answers worth extracting, markup mirroring the visible truth — with expectations set to the post-2023 reality: the payoff is being understood, not being decorated.

FAQPage entered schema.org's vocabulary and Google's rich-result lineup in 2019, sprawled across commercial SERPs for four years, and was demoted in August 2023 to government and health authorities — a compressed lesson in feature lifecycles, with the markup's machine-readability outliving its decoration.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where faq schema is a core concern: