New

Offer Showdown Discover

Tonaily
All free tools

Free tool · Technical

FAQ schema generator.

Add your questions and their answers. The FAQPage JSON-LD is built as you type, checked against the rules Google documents, and ready to paste into the head of the page. Everything stays in your browser.

  • Free
  • Open access
  • Checked as you type
  • Unlimited questions
tonaily.com / tools / faq-schema-generator
Questions and answers
Example
Valid JSON-LD 2 questions 
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema is FAQPage JSON-LD that lists the questions a page answers and the answer to each one, so search engines and AI assistants read them as pairs."
      }
    },
    {
      "@type": "Question",
      "name": "Does FAQ schema still show rich results in Google?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Only for government and health sites since August 2023. For everyone else it helps machines read the page."
      }
    }
  ]
}
</script>
  • Every question has an answer, ends with a question mark and is unique.
  • The rule to check yourself: all of this text must be visible on the page itself.
Output
  • Every question has an answer, ends with a question mark and is unique.
  • The rule to check yourself: all of this text must be visible on the page itself.

How to use the output.

  1. 01

    Write what is on the page

    Google requires every question and answer in the markup to be visible on the page itself. Paste the text as it is published, word for word. An accordion is fine. A block that only exists in the markup is spam.

  2. 02

    One answer per question

    FAQPage is for pages where the site author gives the single answer. A thread where readers submit competing answers is QAPage. A product page with three support notes falls outside both types, so leave both off it.

  3. 03

    Copy it into the head

    The output is a complete script tag. Paste it once in the head of the page, one FAQPage block per page, listing every question that page answers. Check it with the Schema.org validator before you ship.

Beyond the rich result: a page machines can read.

FAQ markup used to buy space in the results: the accordion under the listing. Since August 2023 Google shows FAQ rich results only for government and health sites. For everyone else the listing keeps its standard look, and a generator that promises an accordion is selling a feature Google switched off.

What it still does is read. A FAQPage block states, in a form every crawler reads precisely, which questions the page answers and what the answer to each one is. Google uses it to understand the page. Answer engines, from AI Overviews to ChatGPT and Perplexity, quote a clean question-and-answer pair more easily than a paragraph they have to cut themselves.

Most invalid FAQ schema is valid JSON with the wrong content: text missing from the page, the same block pasted on every page of a site, or answers written as pitches. The generator checks what it can see: a question for every answer, an answer for every question, a question mark, unique questions. The rest is on the page, and it is the part Google penalises.

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, so they can read the pairs directly from the markup.
Does FAQ schema still produce rich results in Google?
Only for a small group of sites. In August 2023 Google restricted FAQ rich results to well-known authoritative government and health websites; for everyone else the listing now appears in its standard form. The markup itself is still worth adding: Google reads it to understand the page, Bing reads it, and answer engines quote a clean question-and-answer pair more easily than a paragraph. Its value today lies in how machines read the page.
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. Keep FAQ markup for pages whose main purpose is answering questions: a product page with a support section remains a product 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 reader on that page. Marking up content that is absent from the page, or that appears only after a JavaScript injection on load, is treated as spam and can cost a manual action.
What is the difference between FAQPage and QAPage?
FAQPage assumes the site author wrote the single authoritative answer to each question. QAPage is for pages where readers submit competing answers, with votes or replies, and it has its own fields for them. A forum thread is QAPage. A help page you wrote is FAQPage. A product page with three support notes falls outside both.
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. An 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, each one real. Three to eight is the usual range for a useful page. Inventing questions to pad the markup produces a page that reads as written for a crawler, which is exactly what quality raters are asked to spot.

Tools that go with it

One FAQ block is a copy-paste. Forty, kept in sync, is a system.

Tonaily writes the FAQ section of every article and emits its FAQPage markup with it, so what is published and what is marked up always match. Plug your site and see what it would mark up first.

Audit my site for free See how articles are written

Free audit, open access · Free plan, just your email

Cette page est disponible en français.

Lire en français