Free FAQ Schema Generator Tool

As code, yes. As a way to change your Google listing, no. Google narrowed FAQ rich results to well-known government and health websites in 2023, then stopped showing the feature altogether on 7 May 2026 and retired its FAQ documentation the following month, according to the Google Search Central documentation changelog.

The markup is still valid Schema.org, so search engines, browsers and other tools that read structured data can parse it. Google’s own guidance on generative AI search also says structured data is not required to appear in its AI features and that no special markup is needed, while still recommending it as part of normal SEO practice.

What changed, at a glance

Below is a complete FAQ page schema example with two questions. Every property shown is needed; anything else is optional.

Valid A correct FAQPage block

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most orders arrive in 3 to 5 working days."
      }
    },
    {
      "@type": "Question",
      "name": "Can I change my order after paying?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, within two hours. Reply to your confirmation email."
      }
    }
  ]
}
</script>

Reading the example

A broken example and how to fix it

Broken Three common errors

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What sizes do you stock?",
      "acceptedAnswer": [
        { "@type": "Answer", "text": "UK 3 to 12." },
        { "@type": "Answer", "text": "Half sizes too." }
      ]
    },
    {
      "@type": "Question",
      "name": "Do you offer a "fit guarantee"?",
    }
  ]
}

• Two answers to one question. acceptedAnswer takes a single Answer. Merge the replies into one text.
• Unescaped quotation marks. The straight quotes around fit guarantee end the string early and break the whole block. Escape them as \" or use curly quotes. The generator handles this for you.
• A question with no answer, and a trailing comma. Every Question needs an acceptedAnswer, and JSON does not allow a comma before a closing brace.

Test twice: the code before you publish, and the live page after.

1. Before publishing, read the checks panel next to your code. It works as an FAQ schema checker, confirming the JSON parses and every question has a name and one answer.
2. For a second opinion, press Open Schema.org validator. The code is copied for you; paste it into the code snippet tab and run the test.
3. After publishing, enter the page URL in the same validator to confirm the server actually delivers the markup. Caching, plugins and templates sometimes strip or duplicate it.
4. Compare with the page. Read the questions in the validator output against the visible FAQ. They should match word for word.

What the checks look at

• Mark up what people can see. Every question and answer in the code should appear on the page in the same words.
• Write the answer once. Give each question a single, complete reply rather than splitting it.
• Keep it current. When you edit the FAQ, regenerate the code, or better, have your CMS build it from the FAQ content.
• Use it for real FAQs. A sales pitch dressed as questions helps no one reading the page.