FAQ schema generator

Turn a list of questions and answers into valid FAQPage markup. Read the status note first: Google no longer shows FAQ rich results.

Status: Google no longer shows this rich result. Google stopped showing FAQ rich results on May 7, 2026 and removed the documentation in June 2026. The markup is still valid schema.org and does no harm. See the full timeline.

Required

4/4

Recommended

none

Rich result retired by Google: valid markup, no special search appearance.

Wrap in <script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders placed before 2 pm ship the same day. Standard delivery takes 2–4 business days within the continental US."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return worn boots?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, within 30 days if they were worn indoors only. Outdoor-worn boots are covered by the 1-year sole warranty instead."
      }
    }
  ]
}
</script>

When to use FAQPage markup

A page where the site itself answers a list of questions (not user-submitted questions: that's QAPage).
Help-centre or product FAQ sections whose answers are visible on the page.
When other consumers of schema.org, such as other search engines or your own tools, can use it.

Getting it right

Every question and answer in the markup must be visible on the page.
Answer text may contain basic HTML such as links and lists.
Don't use FAQPage for advertising copy or for forums where users post answers.
If you already have FAQPage markup, Google says you can leave it; it won't hurt rankings.

Source: Google Search Central, FAQ structured data documentation, and schema.org/FAQPage.

Google's property list

Property	Google says
`mainEntity`	required
`mainEntity.name`	required
`mainEntity.acceptedAnswer`	required
`mainEntity.acceptedAnswer.text`	required

Example output

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders placed before 2 pm ship the same day. Standard delivery takes 2–4 business days within the continental US."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return worn boots?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, within 30 days if they were worn indoors only. Outdoor-worn boots are covered by the 1-year sole warranty instead."
      }
    }
  ]
}

FAQ schema questions

Does FAQ schema still work in 2026?

The markup is still valid schema.org, but Google stopped showing FAQ rich results on May 7, 2026 and removed the FAQ documentation and Rich Results Test support in June 2026. Before that, since August 2023, FAQ results had only been shown for well-known government and health sites.

Should I remove my FAQ markup?

You don't have to. Google's changelog says the markup can stay in place without affecting visibility. Remove it only if maintaining it costs you effort.

Do AI search features use FAQ schema?

Google has not said that FAQ markup affects its generative AI features. Its guidance on AI features stresses helpful, visible content over any particular markup.

Related generators

HowTo schemaStep lists (rich result retired 2023)Article schemaNews, blog posts and guides Breadcrumb schemaBreadcrumbList trails Schema validatorCheck any page or snippet