FAQ schema generator (FAQPage JSON-LD)

How to use the FAQ schema generator

1. Add your questions and answers. Type them in the rows, or open Paste an existing FAQ and paste text with "Q:" and "A:" lines, headings, or question lines that end with a question mark.
2. Fix the notes. The generator flags rows with a question but no answer, duplicates, and answers longer than 1,500 characters.
3. Copy both outputs. The JSON-LD script goes into the page code. The visible FAQ HTML goes into the page content, so people see the same questions the markup describes.

What the generator outputs

A JSON-LD script with the schema.org FAQPage type, ready to paste:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I cancel anytime?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Cancel from Billing and your plan stays active until the end of the period."
      }
    }
  ]
}
</script>

Inside the script, every < is written as \u003c. That stops an answer that contains HTML from closing the script tag early and breaking the page.

The HTML output uses native <details> and <summary> elements: an accordion that works with a keyboard and a screen reader and needs no JavaScript. Style it with your own CSS.

Rules for FAQ structured data

• Match the page. Every question and answer in the markup must be visible on the same page.
• Use it for real FAQs. Questions written by the site owner with one answer each. Forum threads and questions with many user answers use a different type (QAPage).
• No ads in answers. Answers explain; they do not sell.
• One FAQPage per page. Repeating the same FAQ on many pages adds nothing and looks like spam.

Does FAQ schema still help?

For Google rich results, no. In August 2023 Google limited FAQ rich results to well-known government and health websites, and on 7 May 2026 it stopped showing them for all sites. The markup will not make expandable questions appear under your search result.

It can still be worth adding:

• Bing and other search engines read structured data.
• AI assistants and answer engines parse pages for clear question and answer pairs. Markup makes those pairs explicit.
• It is cheap: one script per page, generated from text you already wrote.

The visible FAQ matters more than the markup. Well-written questions in the customer's own words, with direct answers, help visitors on the page, get quoted by assistants, and reduce the questions your support team receives.

How to test the markup

1. Publish the page with both the script and the visible FAQ.
2. Run the URL through the Schema Markup Validator (validator.schema.org) to check the structure.
3. View the page source to check that the script is in the HTML the server sends, not only added by JavaScript.
4. Check the page source once more after your CMS saves it: some editors strip script tags from content fields.

Common mistakes

• Markup without visible text. Hiding the FAQ in a closed tab is fine; leaving it out of the page is not.
• Out-of-date answers. When a price or policy changes, the answer in the script must change too. Generate it again from the same rows.
• Two FAQPage blocks on one page, often one from a plugin and one pasted by hand. Keep one.
• Broken JSON. A missing comma or quote makes the whole block unreadable. Copy the output as it is, without editing it by hand.

Writing the questions

Take questions from your support inbox, chat logs and sales calls, not from a brainstorm. Write them as customers ask them, start each answer with the answer, and keep it to two or three sentences with a link to the full page. If you have the content but not the questions, the FAQ generator drafts them from a page for you.