FAQ Schema in 15 Minutes: JSON-LD That Actually Earns Rich Results

FAQ rich results are one of the few schema types Google still shows widely in search results. They expand your listing, push competitors down the page, and — increasingly — feed the exact passages AI Overviews quote when answering questions.

Most implementations fail on small technicalities, not big mistakes. Here is the minimal correct pattern and the five rules that break nearly every failed deployment I’ve seen.

The template

Drop this JSON-LD in the <head> (or before </body>) of any page that has visible Q&A content:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does SEO take to show results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most small business sites see movement in 3–6 months. Competitive keywords and brand-new domains take longer; technical fixes can move the needle in weeks."
      }
    },
    {
      "@type": "Question",
      "name": "Is FAQ schema enough to get rich results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Valid markup makes you eligible, but Google decides whether to show the rich result based on the page’s overall quality and relevance."
      }
    }
  ]
}

That’s the whole data model: FAQPage → one or more Question → each with one acceptedAnswer. If your markup doesn’t nest exactly like this, validators will flag it.

The five rules that break most implementations

1. The Q&A must be visible on the page. This is the #1 reason markup gets ignored. If the question and answer exist only in the JSON-LD and nowhere in the rendered HTML, Google treats it as misleading markup. Every name/text pair should match content a visitor can actually read.

2. One FAQPage per page. Don’t combine FAQ schema with other page-level types in ways that confuse the entity. A page can carry FAQPage plus Article or WebPage, but keep the FAQ block to a single FAQPage node.

3. No promotional or empty questions. “Why is our company the best?” with a sales pitch as the answer is exactly what Google’s spam policies describe. Questions should be genuine questions your visitors ask; answers should answer them.

4. Keep answers self-contained. Short, complete answers perform best — both for rich results and for AI citation. One to three sentences that fully answer the question beats a paragraph that trails off. (This is the same extractability principle behind getting cited in AI Overviews.)

5. Validate before you ship, monitor after. Run every page through Google’s Rich Results Test before deploying. After deployment, watch the Enhancements report in Search Console — it will tell you exactly which pages have valid items and which errored, so you fix reality, not guesses.

What to do this week

Pick your five highest-traffic informational pages. Add a genuine FAQ section to each (visible content first), mark it up with the template above, validate, and deploy. Then check Search Console’s Enhancements report in 7–14 days.

If you want the full walkthrough — including the edge cases (accordion FAQs, multi-page FAQ hubs, and the mistakes that trigger manual review) — we published a complete guide: How to Add FAQ Schema. It covers everything above in depth with tested examples.