FAQ schema is the structured-data type with the most dramatic backstory: for years it turned search listings into expandable question-and-answer accordions for anyone who added it, it was abused into ubiquity, and Google pulled the feature back hard. The markup still matters, for reasons that survived the crackdown, but anyone implementing it deserves the full story rather than a 2021 tutorial. This guide is the full story, with our free FAQ schema generator producing the markup correctly when you want it.
In this guide
What FAQ schema declares
The FAQPage type states that a page contains a list of questions with accepted answers, as a JSON-LD block listing each pair: the question text as the name, the answer as HTML-capable text beneath it. The contract has one load-bearing clause: the marked-up questions and answers must be visible on the page, the markup restating content rather than smuggling extra text to crawlers. It suits pages that genuinely answer discrete questions, support pages, product FAQs, the question sections of guides like this one, and does not suit forums or pages where users supply competing answers, which have their own QAPage type.
The honest history: what Google changed
The accordion era ended in August 2023, when Google announced that FAQ rich results would show only for well-known, authoritative government and health websites, removing the expandable listings for everyone else in the same sweep that retired How-To results. The reason was visible to anyone searching: marked-up FAQ blocks had spread to every commercial page regardless of usefulness, occupying screen space without earning it. The crackdown is the context any current tutorial owes you: adding FAQ schema today, for most sites, will not produce expandable Google listings, and any guide promising otherwise is describing the previous internet. What survives is everything else the markup does, which turns out to be a real list.
What it is still worth, and to whom
Three audiences still read the markup. Other search surfaces: Bing continues to use FAQ markup in its results, and search features change often enough that present-tense absolutes age badly in both directions. AI systems: assistants and answer engines that summarize the web consume structured Q&A gratefully, a clean question paired with a self-contained answer being the most citable shape content takes, which folds FAQ markup into the generative-engine side of SEO. Your own structure: the discipline of stating questions exactly as users ask them, with answers that stand alone, improves the visible page for the long-tail queries those questions are. The calculation changed from “free rich result” to “cheap structural clarity”, and at one generated block per page, the price fits the value.
Writing Q&A pairs that deserve markup
The markup amplifies whatever quality the pairs have, so the writing rules carry the weight. Ask real questions, phrased the way a person types them, not marketing prompts (“Why is our product the best?”) that no one asks. Answer completely in the answer: each response should survive being read alone, without the page around it, since alone is exactly how machines lift it. Keep one fact per pair rather than essay answers, and as many pairs as the page honestly supports, four strong beating ten padded. Match the visible text exactly: the generator takes the same pairs the page shows, and any drift between markup and page is the one implementation error that reads as deception rather than sloppiness.
Implementing and checking
Implementation is one paste: the generator turns your pairs into a valid FAQPage JSON-LD block, which goes into the page alongside the visible FAQ section, no plugin needed, as covered for every type in the schema markup pillar. Verification is two tools: Google’s Rich Results Test confirms the block parses and lists property warnings, and our schema markup extractor reads the markup back from the live URL, the check that catches the template that silently strips script tags. Run the extractor on competitors while you are there: which sites in your niche still maintain FAQ markup, and how carefully, is a one-paste research question.
Frequently asked questions
Should I remove FAQ schema that I added before 2023?
No need: valid markup that matches visible content costs nothing and keeps serving the non-Google audiences above. Removal makes sense only where the markup was always padding, in which case the visible accordion of filler questions deserves the same audit.
Does FAQ schema work on every page type?
It belongs where discrete Q&A content actually lives. Marking up a page whose “questions” are section headings rewritten with question marks is the pattern that got the feature revoked; the type works exactly as far as the content is honestly what it claims.
How many questions should one page mark up?
As many as are real, which in practice is three to eight for most pages. There is no bonus for volume, and the page-level quality signal runs the other way: every padded pair dilutes the ones that earn their place.
Can the same question appear on multiple pages of my site?
Better not: duplicated Q&A blocks across pages read as boilerplate to exactly the systems the markup addresses. Keep each question with the page that owns its topic, and link between pages rather than copying answers around.