Does FAQ schema still show rich results in Google?

Selectively. In August 2023 Google narrowed FAQ rich result eligibility to "well-known authoritative government and health websites" — most commercial sites lost the visible FAQ block. However, FAQPage schema is still valuable: (1) it remains required for FAQ rich results on the eligible sites; (2) Bing continues to show FAQ rich results broadly; (3) AI engines (ChatGPT, Perplexity, Gemini, AI Overviews) heavily weight FAQPage schema when extracting Q&A snippets for answers. Deploy it for AI citation, not for Google rich results.

Should I still use FAQ schema in 2026 if Google rarely shows the rich result?

Yes, for two reasons. First, AI answer engines have replaced the visible Google FAQ block with something arguably more valuable: direct citation in AI-generated answers. FAQPage-marked Q&A pairs are among the most-cited content forms by ChatGPT and Perplexity. Second, Bing still surfaces FAQ rich results regularly; if you have any meaningful Bing organic traffic (and you should — Bing powers ChatGPT search), the rich result alone makes it worth the markup.

How do I add FAQ schema to a page?

Wrap your Q&A content in JSON-LD structured data of type FAQPage. Each Q&A becomes a Question with an acceptedAnswer (containing an Answer with the text). Place inside a tag in the page or anywhere in the body. Use our free schema generator to build the markup without writing JSON by hand.

What questions should I include in FAQ schema?

Real questions users ask, not invented questions for SEO purposes. Pull from: (1) actual support tickets and customer email; (2) Google's "People also ask" box for your target keyword; (3) AnswerThePublic, AlsoAsked, or similar tools; (4) the questions sales reps repeatedly answer. Avoid the temptation to stuff in keyword-loaded questions nobody asks — Google can detect "spammy" FAQs and removes the rich result eligibility entirely.

How many FAQs should a page have?

There is no hard limit, but quality matters more than count. A page with 5-8 substantive Q&A pairs typically outperforms a page with 20 thin ones. Each answer should be 50-200 words — long enough to be substantive, short enough to be extractable as a snippet. Pages with extremely short answers (one sentence) get cited less often by AI engines because there is no meaningful content to extract.

Can I use FAQ schema on every page or only on FAQ pages?

You can use it on any page with genuine Q&A content — service pages, product pages, location pages, blog posts. The "rule" is content match: the Q&A pairs in the schema must visibly appear on the page (Google flags hidden FAQs as spam). FAQ schema embedded on regular content pages is one of the highest-ROI uses; the page already gets traffic from informational queries, and the Q&A blocks lift citation eligibility on top of existing rank.

What is the difference between FAQ schema and Q&A schema (QAPage)?

FAQPage describes a list of authoritative Q&A pairs — typically by the page owner. QAPage describes a single question with multiple user-submitted answers (forum-style content like Stack Overflow or Quora). For business websites, you want FAQPage. QAPage is reserved for community Q&A platforms.

Schema

FAQ Schema in 2026

Google narrowed FAQ rich results in 2023, so why is FAQ schema more valuable than ever? Because AI answer engines absorbed the role and cite FAQPage-marked content heavily.

Last Updated: April 2026

Quick Answer

FAQ schema (FAQPage) is structured data that labels question-and-answer pairs on a page. Google narrowed visible FAQ rich results to authoritative government and health sites in 2023, but AI answer engines (ChatGPT, Perplexity, Gemini, AI Overviews) now cite FAQPage-marked content heavily — making it one of the highest-ROI schema deployments in 2026. Bing also still shows FAQ rich results broadly. Deploy on any page with genuine Q&A content.

What changed and what didn't

In August 2023, Google announced that FAQ rich results would be restricted to "well-known authoritative government and health websites." Commercial sites lost the visible expandable FAQ block in search results overnight. Many SEO teams stopped deploying FAQ schema in response.

That was a mistake. The visible rich result is one use case for FAQ schema; AI citation is another, and it's grown from negligible to significant in the same window. ChatGPT, Perplexity, Gemini, and Google AI Overviews all extract Q&A snippets readily from FAQPage-marked content because the markup makes the question-answer relationship explicit and machine-parseable.

Bing also continues to show FAQ rich results broadly without the Google-style restrictions. For sites that get meaningful Bing traffic — and given Bing powers ChatGPT's web search, that's increasingly every site — the visible rich result alone justifies the markup.

The minimum-viable FAQPage JSON-LD

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema is structured data that..."
      }
    },
    {
      "@type": "Question",
      "name": "Why does FAQ schema still matter in 2026?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Because AI answer engines cite FAQPage-marked content heavily..."
      }
    }
  ]
}

Wrap this in <script type="application/ld+json"> tags and place in the page <head> or body.

Five rules for FAQ schema that actually works

Every Q&A pair in the schema must visibly appear on the page. Google flags hidden FAQs as spammy structured data and removes rich result eligibility for the entire site.
Use real questions users actually ask. Pull from support tickets, "People also ask" boxes, AlsoAsked. Don't invent keyword-stuffed questions.
Aim for 5-8 substantive Q&A pairs per page. Quality and answer length matter more than count. AI engines cite 50-200-word answers more than one-sentence answers.
Deploy on existing content pages, not just dedicated FAQ pages. Service pages, product pages, location pages, blog posts — any page with natural Q&A content benefits.
Validate with Google Rich Results Test. Invalid markup is silently ignored. Always validate before deploying to production.

Generate FAQ schema in seconds

Don't write JSON-LD by hand — use our free schema markup generator. Add your questions and answers in a simple form and copy the validated JSON-LD directly into your page.

Frequently Asked Questions

What is FAQ schema? +

FAQ schema (technically the FAQPage type from schema.org) is structured data that explicitly labels question-and-answer content on a page. Adding it tells Google, Bing, and AI engines that this section contains FAQs, with each Question and Answer paired. The markup is JSON-LD inside a