How to Write FAQ Schema That Wins Rich Results

To write FAQ schema that wins rich results, mark up questions and answers that visibly appear on the page, using valid FAQPage JSON-LD, on a site type Google still shows FAQ rich results for. The markup must mirror on-page content exactly; invisible or promotional Q&A gets ignored or penalized.

The eligibility reality first

Google restricted FAQ rich results to well-known, authoritative government and health sites for the visible dropdown treatment. So why bother? Because the markup’s value moved rather than died: it feeds Google’s understanding of your Q&A content, strengthens eligibility for other answer surfaces, and hands AI assistants clean question-answer pairs to quote. Structured answers are currency across every answer engine, with or without the dropdown.

The correct JSON-LD skeleton

A FAQPage type containing a mainEntity array of Question items, each with a name (the question text) and an acceptedAnswer holding the answer text. Place it in a script tag of type application/ld+json, one FAQPage per page, questions phrased exactly as they appear on screen. Keep answers self-contained: forty to eighty words that resolve the question without needing the rest of the page.

The rules that actually get enforced

Content parity: every marked question and answer must be visible to users on that page. No advertising inside answers. No duplicating the same FAQ block across dozens of URLs. One question, one best page: cannibalizing yourself with repeated questions splits whatever eligibility you have.

Writing answers machines love to lift

Lead with the direct answer in the first sentence, add the one caveat that matters, stop. Question phrasing should match how people actually ask, mined from People Also Ask, autocomplete and your sales calls. This exact structure is what AI Overviews and assistants extract, which is the modern payoff.

How do I test my FAQ markup?

Run the page through Google’s Rich Results Test for validity, then check Search Console’s enhancement reports for indexing of the markup. Validity is table stakes; parity and quality decide the rest.

Should every page get FAQ schema?

Every page with genuine questions, yes: service pages, product pages, guides. Pages with manufactured filler questions, no; thin Q&A dilutes rather than helps.

FAQ architecture runs through our Answer Engine Optimization service, with page-level wins via Featured Snippet Optimization and full markup audits in Technical SEO.