FAQ Schema Generator

How to use the FAQ schema generator

1. Add your questions and answers. Write them the way readers should see them on the page. Click Add question for each one.
2. Copy the JSON-LD (the <script> tag view) and paste it into the page's HTML, in the <head> or anywhere in the <body>.
3. Copy the visible FAQ HTML if the page doesn't show the questions yet. It is built from the same text, so the markup and the page always match.
4. Check the published page in our schema markup validator.

The live check under the code applies the same rules as the validator: every question needs its text and an answer.

What FAQ schema is

FAQ schema is structured data of type FAQPage. It lists the questions on a page as Question items, each with an acceptedAnswer:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Do you offer same-day service?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. Calls received before 2 p.m. on weekdays are usually scheduled the same day."
    }
  }]
}

Search engines can read the questions and answers as pairs instead of guessing them from headings and paragraphs.

What changed in 2026

For years FAQ markup earned expandable question rows under a search result. Google limited those rows to well-known government and health sites in 2023 and stopped showing them for every site on May 7, 2026.

The markup itself was not deprecated. FAQPage is still valid schema.org, Google still parses it, and AI assistants that read structured data still get clean question-and-answer pairs. What's gone is the extra space in the results. Our article Should you delete your FAQ schema? covers when keeping it makes sense.

Rules that still apply

• The FAQ must be visible on the page. Markup that describes questions readers can't see breaks Google's structured data guidelines.
• Questions and answers are written by the site. Pages where users post questions and other users answer them, like forums and support communities, use QAPage instead.
• One FAQ per page. If the same questions appear on several pages, mark them up on the page where they belong most.
• No ads in answers. An answer is not the place for promotional copy or a list of links.

Where FAQ schema helps

• Service pages: price ranges, timing, licensing and guarantees, the questions people ask before they call.
• Product and pricing pages: what is included, cancellation, payment.
• Support pages with a fixed list of answers written by your team.

It helps least on blog posts padded with generic questions written for the old rich result. If the questions don't help readers, they don't help in the markup either.

Common mistakes

• Answer text that differs from the page. Edit both at once; the generator's HTML output keeps them in sync.
• Broken JSON from pasted quotes. Copying answers from a word processor can bring curly quotes and line breaks into hand-written code. The generator escapes text for you.
• Two FAQPage blocks on one page, often one from a theme and one from an SEO plugin. Keep one.
• Expecting the rich result back. Valid FAQ markup no longer changes how your result looks in Google.