FAQ schema generator: FAQPage JSON-LD plus matching HTML

How to add FAQ schema to a page

1. 1.Write the questions people actually ask: from support tickets, sales calls, or the search queries in Search Console. One question per row.
2. 2.Answer each one in a full sentence that makes sense on its own. Answer engines quote single passages, so the first sentence should carry the answer.
3. 3.Put the rows in the order a reader needs them, using Move up and Move down. The JSON-LD follows the same order as the visible list.
4. 4.Fix every error the validator flags. Paste your live page's HTML into the check box if the FAQ already exists, so mismatched wording shows up as warnings.
5. 5.Copy the HTML into the page where the FAQ should appear and the script tag anywhere in the same page, then test the URL with Google's Rich Results Test or the Schema Markup Validator.

Example: FAQ section with matching JSON-LD

<section class="faq">
  <h2>Frequently asked questions</h2>
  <details>
    <summary>Is there a free trial?</summary>
    <p>Yes. Every plan includes a 14-day free trial.</p>
  </details>
</section>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is there a free trial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Every plan includes a 14-day free trial."
      }
    }
  ]
}
</script>

Why <details> and <summary>

A native <details> element collapses without JavaScript, works with the keyboard and screen readers, and keeps the answer in the HTML that crawlers read, even while it's closed. Crawlers that don't run JavaScript, which includes most AI crawlers, still see every answer.

Common FAQ schema mistakes

• Marking up Q&A that isn't on the page, or that's only loaded after a click by JavaScript. Google's guidelines require the content to be visible to users.
• Different wording in the markup and on the page, usually because one was edited and the other wasn't.
• Empty or one-word answers. acceptedAnswer.text is required and should answer the question in full.
• The same question twice, often from a theme block and a plugin both adding FAQ markup. Check the page source for more than one FAQPage block.
• Using FAQPage for user-submitted questions with several answers. That's QAPage, a different type.
• Unescaped JSON-LD built by string concatenation. A quote or </script> in an answer breaks the JSON or the whole page.

Is it worth adding FAQ schema in 2026?

For Google's rich results, only if you run a well-known government or health site. For everyone else, it's a cheap, accurate description of content you already have. A clear FAQ section helps readers and gives search and answer engines self-contained answers to quote. The markup labels which text is the question and which is the answer. Don't expect a ranking or traffic jump from it alone.

VisitTrack can show you whether that content gets read and whether it sends visitors. AI crawler tracking records which AI crawlers, such as ChatGPT, Claude and Perplexity, fetch the page, and visits referred by AI assistants appear in their own AI channel. To see which questions readers open, send a custom event when a <details> element is toggled open, for example window.visitrack?.("faq_opened", { question }).