FAQ Schema Generator
Build valid FAQPage JSON-LD, checked against Google's rules as you type — then copy it into your page head.
Add a question and its answer to generate the markup.
Every question has an answer and the markup is well formed. Remember the rule the validator cannot check for you: all of this text must be visible on the page itself.
The four rules that decide whether FAQ markup counts
Most invalid FAQ schema is not malformed JSON — it is valid JSON describing content that is not on the page. These are the constraints Google documents, in the order they get broken.
The text must be visible
Every question and every answer in the markup has to appear on the page for the reader. An accordion is fine — the content exists in the HTML. Content injected after load, or never rendered at all, is not.
The page must be an FAQ
FAQPage is for pages whose purpose is answering questions. A forum thread where users submit competing answers is QAPage instead, and a product page with three support notes is neither.
One answer per question
FAQPage assumes the site author wrote the single authoritative answer. Multiple candidate answers, votes or replies belong to QAPage, which has its own fields for them.
No promotional or duplicate content
The same FAQ block pasted across every page of a site, or answers that are pitches rather than answers, are what the policy calls out by name. Write the answer you would give if asked out loud.
Why still add it, now that the rich result is gone?
Since August 2023 Google shows FAQ rich results only for well-known authoritative government and health sites, so for most sites the accordion no longer appears. The markup kept two jobs that matter more than it did before: it is read by assistants that build answers — ChatGPT, Gemini, Perplexity — where a clean question-and-answer pair is the easiest thing in a page to quote, and it remains an unambiguous statement to any crawler about what the page answers. It stopped being a way to look bigger in the results and became a way to be citable.
Need markup for something other than an FAQ? The schema markup generator covers Article, Product, Local Business, Organization and Breadcrumb.
Frequently asked questions
What is FAQ schema?
FAQ schema is structured data that marks up a list of questions and their answers as FAQPage JSON-LD. It tells search engines and AI assistants that a page answers specific questions, and which answer belongs to which question, rather than leaving them to infer it from the layout.
Does FAQ schema still produce rich results in Google?
Rarely. In August 2023 Google restricted FAQ rich results to well-known authoritative government and health websites. For everyone else the accordion no longer appears in search results. The markup itself is still worth adding: it is read by AI assistants building answers, by Bing, and by Google to understand the page — it just no longer changes how the listing looks.
Where do I put FAQ schema on my page?
Inside a script tag with type="application/ld+json", in the head of the page. One FAQPage block per page, listing every question that page answers. Do not put FAQ markup on a page whose purpose is something else — a product page with a support section is not an FAQ page.
Do the questions and answers have to be visible on the page?
Yes, and this is the rule most often broken. Google requires that the full text of every question and answer in the markup appears visibly to the user on that page. Marking up content that is not on the page, or that only exists behind a click you generate in JavaScript after load, is treated as spam and can cost a manual action.
Can I use HTML inside FAQ answers?
A limited set: paragraphs, line breaks, lists, bold and italic, and links. Anything else is stripped. Keep answers to plain prose where you can — the answer is more likely to be reused verbatim by an AI assistant if it reads as one self-contained passage.
How many questions should a FAQPage have?
As many as the page genuinely answers, and no filler. Three to eight is the usual range for a useful page. Inventing questions nobody asks to pad the markup produces a page that reads as written for a crawler, which is exactly what quality raters are asked to spot.
Schema on every article, without the copy-paste
Tonaily writes the FAQ section and emits its FAQPage markup with it, so what is published and what is marked up never drift apart.