Draftcamp

FAQ schema generator

Turn question and answer pairs into FAQPage JSON-LD that qualifies for rich results

Runs entirely in your browser - your text is never uploaded

Question 1
Question 2

Add a question and its answer

Both halves are needed - a Question node without an acceptedAnswer is invalid schema.

FAQ schema after Google took the rich result away

In August 2023 Google restricted FAQ rich results to authoritative government and health sites. For everyone else, the accordion that used to appear under your result simply stopped appearing. A lot of teams removed their FAQ markup at that point, reasonably enough - the visible payoff was gone.

That was the right call for the old reason and the wrong call for the new one.

Why it matters more now, not less

FAQ markup is the most explicit machine-readable statement available of "this page answers this question, and here is the answer". Answer engines - ChatGPT, Perplexity, Gemini, AI Overviews - are in the business of finding exactly that and quoting it. An unambiguous question-answer pair is far easier to extract cleanly than the same content buried in prose.

The rich result was a Google feature that came and went. The structure underneath is a distribution advantage that got more valuable.

Getting it right

  • The Q&A must be visible on the page. Collapsed behind an accordion is fine. Absent entirely is a policy violation.
  • Answer completely in the answer text. "See below" or "it depends" gives an engine nothing to quote.
  • Write real questions. Phrase them the way someone would actually ask, because that is what gets matched against.
  • Do not pad. Six genuine questions beat twenty invented ones.

For other content types, the schema markup generator covers Article, Product, Organization, HowTo and LocalBusiness.

Common questions

Does FAQ schema still show rich results?
Rarely, and only for a narrow set of sites. In August 2023 Google restricted FAQ rich results to well-known, authoritative government and health sites. For everyone else the accordion no longer appears. The markup is still worth adding, but not for that reason.
Then why add it at all?
Because it is machine-readable question-and-answer structure, and answer engines consume exactly that. Explicitly pairing a question with its answer is the clearest possible signal of what your page answers - which matters more now for citation in ChatGPT, Perplexity and AI Overviews than it ever did for a Google accordion.
Do the questions and answers have to be visible on the page?
Yes, and this is not negotiable. Google policy requires that FAQ markup describes content the user can see. Marking up answers that are hidden, collapsed behind a click is fine, but answers absent from the page entirely is a policy violation that can earn a manual action.
How many questions should I include?
As many as the page genuinely answers. There is no minimum and no bonus for volume. Padding a page with invented questions to reach some count makes the content worse and gives an answer engine weaker material to quote.
Can I use HTML inside answers?
A limited set - links, lists and basic formatting are permitted in the answer text. Keep it minimal. Plain text is easier to extract cleanly, and extraction is now the point.