FAQ schema in 2026 — when to actually use it (and when to skip)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is the FAQ schema still useful?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes — it qualifies for AI Overview citations and Bing rich results."
      }
    },
    {
      "@type": "Question",
      "name": "How many FAQs should I include?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "3–8 is the sweet spot. Fewer looks thin; more dilutes topical focus."
      }
    },
    {
      "@type": "Question",
      "name": "Can I reuse FAQ schema across pages?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Only if each FAQ is genuinely relevant to that page topic."
      }
    }
  ]
}
</script>

Quick frame: Google restricted FAQ rich results to a narrow list of authoritative sites in August 2023. The schema is still worth shipping — it qualifies for AI Overview citations, Bing rich results, and may regain broader eligibility later. Cost to emit is essentially zero.

What changed in August 2023

Before the restriction, almost any page with valid FAQ schema could earn the expandable FAQ widget in Google SERPs. That widget consumed a lot of vertical space and was being abused for marketing FAQs. Google cut eligibility to government and authoritative health sites, citing user experience.

Why ship FAQ schema anyway

Three reasons:

1. AI Overview citations. Google's AI Overview pulls answers from FAQ-marked content and credits the source. This is a non-trivial traffic source for high-intent commercial queries.
2. Bing rich results. Bing still surfaces FAQ rich results broadly. India's Bing share is small but growing.
3. Eligibility recovery. If Google re-expands FAQ rich results (it's happened before for other types), pages with existing markup get back in immediately.

The FAQ schema generator embedded above produces the markup. Pair with the FAQ block HTML generator to keep visible HTML and schema in sync.

What makes a good FAQ

The marked-up Q&A must match what users see on the page — Google's guideline is explicit, and hidden / schema-only FAQs lose eligibility entirely. Beyond that:

• 3–8 FAQs per page (fewer = thin; more = diluted).
• Each Q is a real user question, not promotional fluff.
• Each A is under 1000 characters (Google truncates longer ones).
• No links inside answer text — Google ignores them.

What NOT to mark up

Promotional FAQs ("Why is our product the best?") violate Google's structured data guidelines and can trigger manual actions. Stick to genuine user-intent questions.

The wider FAQ pattern (HTML + schema together) is in FAQ blocks vs FAQ schema.

FAQ

Q. Does FAQ schema help ranking? A. Not directly. It helps eligibility for AI Overview citations and Bing rich results, both of which indirectly drive traffic and brand signals.

Q. Can I reuse the same FAQ block across many pages? A. Only if each FAQ is genuinely relevant to that page topic. Boilerplate FAQs duplicated across many pages can trigger structured-data spam flags.

Q. Should answer length match across all FAQs? A. No fixed rule — answer thoroughness to each question's genuine need. A one-line answer is fine for a yes/no question.