Skip to content

FAQ Schema Generator - FAQPage JSON-LD Markup

Import existing JSON-LD

Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.

FAQ Items

Google Search Preview
example.com
FAQ Page Title
All Google requirements met

JSON-LD Output

What is FAQ schema?

FAQ schema is structured data that marks up a list of questions and answers on a page, using the schema.org FAQPage type with one Question and acceptedAnswer pair per item. It tells search engines and AI assistants which text is a question and which text answers it. The page must show the same questions and answers to visitors.

FAQPage is for pages where the site itself wrote both the questions and the answers, such as a support page or a product FAQ. Pages where users ask and answer each other, like a forum thread, should use QAPage or DiscussionForumPosting instead.

FAQ schema example (JSON-LD)

A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a passport renewal take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Routine renewals take 4 to 6 weeks from the day we receive your application. Expedited service takes 2 to 3 weeks and costs an extra $60."
      }
    },
    {
      "@type": "Question",
      "name": "Can I renew my passport online?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, if your current passport was issued when you were 16 or older and expires within the next year. Otherwise you need to apply by mail."
      }
    }
  ]
}
</script>

Which Google rich result does it enable?

None in Google any more. The expandable questions under a listing were cut back to government and health sites in August 2023, and Google stopped showing them for every site on 7 May 2026. Its FAQ documentation was taken down in June 2026. Existing markup does no harm and does not need removing.

FAQPage is still valid schema.org, and Google has said it continues to read structured data to understand a page. Other search engines and AI tools can also parse it. None of that produces a visible change you can measure, so add the markup when the FAQ is already on the page and the effort is small, not as a ranking tactic.

Required and recommended properties

Property Status Notes
mainEntity Required An array of Question items, one for each question on the page.
Question.name Required The full text of the question.
Question.acceptedAnswer Required An Answer object. A question without an answer is invalid, so the generator drops it and shows an error.
Answer.text Required The full answer. Links, lists, and basic formatting tags are allowed.

Common FAQ schema mistakes

  • Adding an FAQ section to a page only to win FAQ rich results. That result no longer exists in Google.
  • Marking up questions that are not visible on the page, or that are hidden behind a login.
  • Using FAQPage for user generated questions. That content belongs in QAPage or forum markup.
  • Repeating the same FAQ block on every page of the site. Mark it up once, on the page where it belongs.
  • Writing answers as advertising copy. Answers should answer the question directly in the first sentence.

How FAQ rich results were phased out

Google added FAQ rich results in 2019, and for a few years any page with valid FAQPage markup could take up extra space in the results with expandable questions. Sites added FAQ blocks to almost every page for that reason. In August 2023 Google limited the feature to well-known government and health websites. In May 2026 it added a deprecation notice and stopped showing FAQ rich results on 7 May, and in June 2026 it removed the documentation altogether.

The generator still builds valid FAQPage markup, and it only outputs questions that have an answer. Write the FAQ for readers first: if a question would not be on the page without the markup, it does not need to be on the page at all.

Related Tools

Frequently Asked Questions

Does FAQ schema still produce rich results in Google?
No. Google limited FAQ rich results to well-known government and health sites in August 2023, then stopped showing them for all sites on 7 May 2026. The FAQ structured data documentation was removed in June 2026.
Should I remove FAQ schema from my pages?
There is no need. FAQPage is valid schema.org, it causes no penalty, and Google says it still reads structured data to understand pages. If the markup is generated by a plugin you are happy with, leave it. If you were maintaining it by hand only for rich results, you can stop.
How do I test FAQ markup now?
Use the Schema Markup Validator button above, which checks the markup against schema.org. Google's Rich Results Test was built around Google's rich result features, so with FAQ gone it is no longer the right tool for this type.
Can I use HTML in FAQ answers?
schema.org allows it, and FAQ markup has traditionally permitted links, lists, paragraphs and bold or italic text in the answer. The generator writes your answer text exactly as you type it, so plain text stays plain and any tags you type are kept.
What is the difference between FAQPage and QAPage?
FAQPage is for questions and answers written by the site, such as a support page. QAPage is for a page where one user asks a question and others answer it, like a Stack Overflow thread. Google still documents QAPage.