FAQ Schema Generator

Use one question per line: Question | Answer

Paste your list of questions and answers and get back a FAQPage JSON-LD block ready to drop into <head>. Google reads the structured data and, when it judges the page eligible, surfaces the questions as collapsible rich snippets in the SERP, which typically doubles the listing’s real estate.

How to generate FAQPage markup

  1. 1

    Add Q/A pairs

    Enter each question and its answer. HTML inside the answer is allowed: it is preserved in the markup.

  2. 2

    Optional: page URL

    Set the canonical URL for the FAQ page so the `@id` fields resolve correctly.

  3. 3

    Generate

    You get a valid `<script type="application/ld+json">` block containing a `FAQPage` with nested `Question` and `Answer` entities.

  4. 4

    Validate

    Paste the snippet into Google's Rich Results Test to confirm eligibility before deploy.

Shape of the output

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Your question here",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Your answer, which may contain HTML like <a href='...'>links</a>."
    }
  }]
}

Google’s eligibility rules (the ones that bite)

  • The FAQ must be visible on the page. Markup-only Q/A blocks hidden in the source code will be ignored and can trigger manual actions.
  • Answers must be informational, not promotional. “Our product is the best” answers get stripped.
  • Content cannot be user-generated (forum posts, comments). Use QAPage schema, not FAQPage, for those.
  • Each Q/A pair must be a distinct, standalone fact, not a sub-heading of a longer how-to.
  • As of August 2023, Google shows FAQ rich results only on authoritative health and government sites for many queries; non-authoritative sites still benefit from the markup but should not count on SERP real estate.

Common errors

Error Fix
The FAQ on the page appears hidden Ensure the visible HTML matches the schema 1:1
Missing field name Every Question needs a non-empty name
Missing field text in acceptedAnswer Every answer needs prose, not an empty string
Not eligible for FAQ rich results Usually the policy change above, keep the markup anyway

Tips

  • Keep questions under 140 characters, Google truncates longer ones in the SERP anyway.
  • Put the most important question first; if only one rich result is shown, that is the one.
  • Avoid duplicate questions across pages on your site; Google may demote both.

Frequently Asked Questions

As of Google’s August 2023 update, FAQ rich results are limited to well-known authoritative sites (mostly government and health). The markup is still worth adding, it helps voice assistants and some third-party search engines use your content, but don’t budget SERP real estate on it unless you qualify.

Yes. Google supports a limited set: <p>, <a>, <b>, <i>, <ul>, <ol>, <li>, line breaks and basic tables. Anything else is stripped.

Only on pages that genuinely have an FAQ section visible to the user. Spraying it everywhere is a signal of manipulation and can earn a manual action.

No. Product Q&A (where users ask and others answer) should use QAPage schema, not FAQPage. FAQPage is for editorial answers from the site owner.

Related Tools

Tool available in other languages