FAQ schema in 2026
Google removed FAQ rich results from most search listings in 2023, which led a lot of people to strip FAQPage markup out entirely. That was a mistake. The rich result is gone; the machine-readable question-answer pairing is still read by answer engines, and it is one of the cleanest ways to hand a model an extractable answer.
What changed and what didn't
What changed: FAQ rich results — the expandable questions under a search listing — now appear only for a small set of authoritative government and health sites. For everyone else, adding FAQPage markup will not change how the listing looks.
What did not change: the markup still explicitly pairs a question with its answer in a structure that retrieval systems parse trivially. That is exactly the shape a generative engine wants when it is looking for a passage to quote.
How to write FAQs worth marking up
Use real questions. The ones from sales calls, support tickets and the 'People also ask' box beat invented ones every time, because they match how people actually phrase things.
Answer in two to four sentences, completely, with a checkable fact where one exists. An answer that says 'it depends on your needs' is worse than no answer, because it teaches the model that your page does not resolve the question.
Include the uncomfortable questions — pricing, limitations, who the product is not for. Pages that address objections are cited disproportionately often, because models favour sources that read as balanced.
Implementation rules
The markup must match visible page content exactly. Marking up questions that a visitor cannot see is a guidelines violation and gets the markup ignored.
One FAQPage block per page. Do not duplicate the same questions across many pages — pick the page that owns each question and link the others to it.
When to skip it
Skip it when the questions are padding. Three genuine questions beat twelve manufactured ones, and a page stuffed with thin Q&A reads as low quality to both people and models.
Skip it on pages where the whole page is already the answer to one question — there, answer-first structure does the job and an FAQ block just repeats it.
Frequently asked questions
Should I remove existing FAQPage schema?
No. Removing valid markup gains nothing and loses the machine-readable pairing that answer engines use.
Do FAQs still win featured snippets?
Yes. The question-and-direct-answer pattern is still the most common source of paragraph snippets, independent of the schema.
How many questions is right?
Three to eight genuine ones. Beyond that you are usually padding, and padding is visible.
Related guides
- Answer-first content structure — The answer-first structure that gets pages lifted into AI answers and featured snippets, with the exact block pattern to use.
- Entity clarity and schema — How to make an AI model certain about what your brand is, using Organization and Person schema, sameAs links and consistent naming.
- AEO vs SEO vs GEO — SEO wins rankings, AEO wins the answer, GEO wins the citation. What each term actually means, how they overlap, and how to measure all three.