FAQ Schema Generator

Read This First — What Changed in May 2026

Almost every page about FAQ schema still promises expandable question-and-answer dropdowns beneath your search listing. That stopped being true on 7 May 2026.

What did not change is the part that still matters

FAQPage remains a valid Schema.org type. Markup already on your pages will not throw errors, will not trigger a manual action, and will not harm your rankings. Google confirmed it continues to parse FAQ markup to understand pages. Other search engines and AI systems parse it too.

Why You Are Here

Given the above, there are three reasons people still generate FAQPage markup, and all three are legitimate.

The first is machine comprehension. A FAQ section written as ordinary HTML is just text a parser has to interpret. The same content in FAQPage markup is explicitly labelled as question-and-answer pairs, which makes it trivially extractable. That matters increasingly for AI-generated answers, which lean on structured data to identify what a page actually asserts.

The second is other platforms. Google is one consumer of structured data among several. Bing, other search engines, and various AI systems all parse Schema.org markup, and Google's decision about one SERP feature does not bind any of them.

The third is consistency. If your site already marks up FAQ content across hundreds of pages, keeping the pattern intact costs nothing and stripping it out costs engineering time for no benefit. Google has been explicit that unused structured data causes no problems.

What This Tool Does

The FAQ Schema Generator builds valid FAQPage JSON-LD from your question and answer pairs.

Enter each question with its answer, add as many pairs as your page has, and the tool assembles correctly nested Question and Answer objects inside a FAQPage wrapper, with the script tag included. Copy it and paste it into your page.

The One Rule That Still Matters

Google's structured data guidelines require FAQ markup to reflect content that is actually visible on the page.

This mattered when rich results were at stake, because violating it could cost you the feature or trigger a manual action. It still matters now, for a simpler reason: marking up questions that do not appear on the page is a false description of your own content, and it undermines the comprehension benefit that is the entire remaining point of the markup.

Property Reference

The structure is simpler than most schema types. A FAQPage contains a mainEntity array, each entry is a Question, and each Question has exactly one acceptedAnswer.

Example Output

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard delivery takes three to five working days."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return an item after 30 days?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Returns are accepted within 30 days of delivery."
      }
    }
  ]
}

FAQPage or QAPage

These are frequently confused and they describe genuinely different things.

Where to Put the Code

<script type="application/ld+json">
{
  ... your FAQPage JSON-LD here ...
}
</script>

Google processes JSON-LD wherever it appears in the document. The head is conventional. One FAQPage block per page is correct. Do not create a separate block for each question.

Should You Remove Existing FAQ Schema?

No, and Google has said so directly. Unused structured data does not cause problems for Search.

Common Mistakes to Avoid

Quick Reference