FAQ schema generator. Q+A in JSON-LD.
Add as many Question + acceptedAnswer pairs as you need. The right panel renders the FAQPage block live. Google's restricted-domain policy explained inline.
Add Q+A pairs in the left panel; the right panel renders FAQPage JSON-LD live with inline validation. Pure browser code — no fetch, no log. Note: as of August 2023, Google restricts FAQ rich results to gov/health authority sites only — schema still helps AI search and content extraction.
Google restricts FAQ rich results to gov / well-known authoritative health sites since Aug 2023. The schema still helps Google AIO + Perplexity + ChatGPT cite passages, so ship it — just don't expect the SERP rich result.
Sources used by this generator
- schema.org/FAQPage · /Question · /Answer
- Google FAQ rich-result restriction (Aug 2023)
- Visible-mirror policy: every Question.name + acceptedAnswer.text must match visible page text 1:1.
Privacy: form runs in-browser only.
FAQ schema after August 2023.
Google announced in August 2023 that FAQ rich results are restricted to "well-known authoritative" gov and health-information sites. Commercial sites lost the visible expandable rich result on SERPs.
Should you still ship FAQ schema? Yes, for three reasons. First, Google still ingests the data even when it doesn't render the rich result; it feeds AI Overviews and the search-Q+A extraction layer. Second, AI engines (ChatGPT, Perplexity, Claude) preferentially cite content with structured Q+A markup — Ahrefs Dec 2025 data shows FAQ-schemed pages get ~30% more citations than identical content without schema. Third, FAQ schema costs almost nothing to add; the upside is asymmetric.
Visible-mirror policy is non-negotiable: every Question.name in the JSON-LD must match a visible heading or summary text on the page, and every acceptedAnswer.text must match the visible answer body. Mismatches violate Google's structured-data policy and risk a manual action.
How many Q+A pairs? Match what's visible. Most service / product pages run 5-8. Comparison and pricing pages run 10-15. Long-form journal posts can run 20+ if the Q+A list is the page's main structure. The JSON-LD has no hard cap.
Six questions users ask.
Will FAQ schema get me a rich result?
Maybe. As of August 2023, Google restricts FAQ rich results to government and well-known authoritative health sites. Most commercial FAQ schema gets ingested but no longer renders the expandable rich result on SERPs. The data still helps with AI Overviews and Q+A passage extraction in ChatGPT and Perplexity, so the schema is still worth shipping.
How many Q+A pairs should I include?
Match what's actually visible on the page. The schema must mirror the rendered DOM 1:1. Most pages have 5-8 Q+A pairs; more is fine if they're all visible.
Can I include HTML in the answer?
Yes. The acceptedAnswer.text field accepts HTML. Keep it readable; Google parses the text content for indexing but the visible rich result strips most formatting.
Why does Question.name need to match the visible heading?
Google's verifier compares the JSON-LD Question.name to the visible question heading on the page. Mismatch (typo, abbreviation, casing diff) = the question gets dropped from the rich-result eligibility pool.
Can I have an empty answer?
No. Every Question must have a non-empty acceptedAnswer.text or the schema fails validation. The generator flags empty answers in red and refuses to include them in the output.
Does this tool log my Q+A?
No. The form runs entirely in JavaScript on your device. Nothing is sent to Digital Heroes servers.