FAQ Schema Is Not Dead — It Just Changed Jobs

When Google cut FAQ rich results back to a narrow set of authoritative sites, a lot of teams stripped the markup out entirely. That was an overcorrection. The dropdown in the search result was only ever one of the jobs FAQ schema did — and it is no longer the most valuable one.

What Actually Changed

The change was to display eligibility, not to the vocabulary or how the markup is processed. Google decided the expandable FAQ blocks cluttered results and restricted them to a small group of well-established government and health sources. FAQPage markup on a commercial page is still parsed; it just usually does not produce a visual enhancement.

Job One: Feeding Generative Answer Engines

AI assistants assemble answers by retrieving passages and paraphrasing them. The easiest passage to retrieve is one where the question is stated explicitly and the answer sits immediately after it, self-contained, without needing the rest of the page for context. That is exactly the shape FAQ markup enforces.

The markup is not magic on its own — the visible text does the work. But writing to satisfy FAQPage markup pushes you into short, quotable, standalone answers, which is the single most useful content habit for AI visibility. This connects directly to why brands go missing from ChatGPT search: most pages simply have no extractable answer on them.

Job Two: Featured Snippets and People Also Ask

Featured snippets and PAA boxes are still very much alive, and both favour the same format: a question-shaped heading with a direct answer of roughly forty to sixty words beneath it. Pages built around a genuine FAQ block tend to pick these up because the structure matches what gets extracted.

• Phrase the heading the way a person types or speaks the question.
• Answer in the first sentence. Do not build up to it.
• Keep each answer independent — no "as mentioned above".
• Add the detail, caveat, or example after the direct answer, not before it.

Job Three: Entity and Topic Clarity

An FAQ block is also one of the cheapest ways to state facts about your business in machine-readable form: what you do, who you serve, where you operate, how engagements work, what things cost. Combined with Organization and Service markup, it gives retrieval systems consistent, repeatable statements to draw on when someone asks about your category.

How to Implement It Properly

• Mark up only visible text. The JSON-LD answer must match the on-page answer word for word.
• One FAQ set per page, and make it topical. Do not paste the same six questions across the site.
• Use FAQPage, not QAPage, when you author both the questions and the answers.
• Keep answers in the initial HTML. Collapsed with details and summary is fine; loaded by JavaScript on click is not.
• Validate it. Invalid JSON-LD fails silently, so test after every template change.
• Write real questions. Pull them from sales calls, support tickets, and PAA boxes rather than inventing them.

The Honest Summary

FAQ schema is no longer a way to win a bigger search result. It is now a structural discipline that makes pages easier to quote — by snippets, by PAA, and by AI assistants. That is a less flashy job than it used to have, and a more durable one.

Frequently Asked Questions