← Blog · By Mars LLC editorial team · September 28, 2026 · Editorial standards

FAQ schema: how to earn FAQ rich results

How FAQPage structured data works, when Google shows it, and how to avoid the common rejections.

FAQPage structured data tells search engines that a page contains a list of questions and answers. When eligible, those questions can appear as expandable results directly in search.

The rules Google actually checks

  • The questions and answers must be visible on the page
  • Only include Q&A that a real user can read — not content hidden behind JavaScript that never renders
  • You may mark up multiple FAQs on one page
  • A single page should be about one topic; FAQ markup is not for a site-wide list of everything
  • Do not use FAQPage for user-generated Q&A on a forum — that is QAPage

A minimal FAQPage

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is it free?",
      "acceptedAnswer": { "@type": "Answer", "text": "Yes, with a daily limit." }
    }
  ]
}

How to write good FAQ answers

  • Answer the question in the first sentence — do not bury it
  • Keep answers to 1–3 short paragraphs
  • Target questions people actually type: "how much does X cost", "is X safe", "X vs Y"
  • One question per topic; do not merge two questions into one
  • Match the answer to the page's visible text exactly in substance

Where to get real questions

  • People also ask boxes in your target SERPs
  • Google autocomplete and related searches
  • Search Console queries phrased as questions
  • Support tickets and sales chats (the most underrated source)

Why results may not show

Google does not guarantee rich results even with valid markup. Elements that reduce eligibility include: markup for questions not on the page, duplicated markup across many pages, and low-quality or spammy content. Monitor the FAQ report in Search Console and fix warnings.

Test the markup

1. Paste the block into the JSON-LD validator to confirm it parses and the @type is FAQPage.

2. Run the page through the Rich Results Test.

3. Check Search Console → Enhancements → FAQ for errors.

Worked example

A pricing page answers three real questions and marks them up:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "Can I cancel anytime?",
      "acceptedAnswer": { "@type": "Answer", "text": "Yes — cancel from your dashboard and access continues until the end of the billing period." } },
    { "@type": "Question", "name": "Do unused credits roll over?",
      "acceptedAnswer": { "@type": "Answer", "text": "Unused monthly credits do not roll over; pay-as-you-go balance does not expire." } }
  ]
}

Each answer is short, specific and matches the visible copy.

Build it

Use the free FAQ schema generator — paste each question and answer, copy the JSON-LD, and add it to the page. For niche page types, we have variations for SaaS, e-commerce and restaurants.

Try the free tool

Generate valid FAQPage schema (JSON-LD) for any page. Paste your questions and answers, copy the code, and pass Google's Rich Results test.

Open FAQ Schema Generator