Will FAQPage schema get me a rich result on Google?

Only if your site is well-known and authoritative in the government or health categories, per Google's August 2023 guidance and the current FAQPage documentation. For other sites, FAQPage schema is primarily useful as an AI-extraction signal.

Is it a penalty risk to use FAQPage on a non-eligible site?

Not if the schema describes genuine FAQ content matching visible page text. Search Engine Land's coverage of the 2023 change is consistent on this. The risk is misuse — promotional or fabricated FAQs — which Google's documentation explicitly disallows.

How long should answers be?

The practical sweet spot for AI extraction is roughly 40-60 words, per Frase.io's analysis. Longer than ~80 words tends to be too large for AI to extract as one unit; shorter than ~30 often lacks the substance AI needs to cite confidently.

Does FAQ schema affect AI Overviews coverage?

Industry analyses suggest pages with clean FAQPage markup are more likely to be extracted into AI Overviews, but Google has not published a direct multiplier. Treat FAQPage as one of several extraction-friendly signals, alongside answer-first prose, semantic HTML, and complete TechArticle / Article markup.

Should I keep FAQ schema if my rich result has disappeared since 2023?

For AEO purposes, yes. Removal is only worthwhile if you suspect mismatched-markup penalties or maintenance overhead. Otherwise the schema continues to feed AI extraction systems independently of Google rich-result eligibility.

FAQ Schema for AEO: Implementation Guide

FAQ schema (FAQPage) helps AI answer engines identify question-answer pairs for extraction. Since August 2023 Google has restricted FAQ rich results to authoritative government and health sites, so for most sites FAQ schema is now an AI-extraction signal rather than a SERP rich-result play.

TL;DR

FAQPage JSON-LD still matters in 2026 — but for a different reason than most older guides claim. Google restricts the FAQ rich result to government and health sites. For everyone else, the value of FAQPage markup is helping ChatGPT, Perplexity, Google AI Overviews, Claude. Copilot identify clean question-answer pairs to extract and cite. Use it on genuine FAQ content, keep answers in the ~40-60 word range, and don't expect a SERP rich result outside the eligible categories.

For broader pattern context, see the /aeo hub and the AEO Content Checklist.

What FAQ schema is

FAQ schema is a FAQPage JSON-LD object containing a mainEntity array of Question items, each with an acceptedAnswer Answer. It is the structured-data way to tell search and AI systems: "this section is question-and-answer content, not free-form prose." The full type definitions live on schema.org/FAQPage, schema.org/Question, and schema.org/Answer.

Why FAQ schema matters in 2026

The 2023 rich-result restriction (read this first)

In August 2023, Google announced that FAQ rich results are only available for well-known, authoritative websites that are government-focused or health-focused (Google Search Central blog: "Changes to HowTo and FAQ rich results"). The Google Search documentation for FAQPage structured data has carried the same restriction since (developers.google.com/search/docs/appearance/structured-data/faqpage).

That means for most marketing, SaaS, e-commerce, and editorial sites, adding FAQPage schema will not produce a rich result in Google Search. Doing so anyway is not a penalty risk if the schema describes genuine FAQ content (Search Engine Land, "The rise and fall of FAQ schema"). However, it should not be sold to stakeholders as a rich-result tactic.

Why it still matters for AEO

FAQ schema retains value as an AI-extraction signal:

AI answer engines scan structured Q-A pairs to identify clean, extractable answer units.
FAQ schema enforces a one-question / one-answer discipline that improves extractability whether the schema is consumed or not.
Eligible sites (gov/health) still earn the rich result.
Pairs well with broader Structured Data for AI Search implementations.

How FAQ schema works

The Google-supported FAQPage type defines:

One FAQPage per page.
Multiple Question objects under mainEntity.
Exactly one acceptedAnswer per question.
name (the question text) and text (the answer text) as the core fields.

Text in JSON-LD must match visible HTML on the page. Mismatched markup is a manual-action risk.

Step-by-step implementation

Step 1. Identify genuine FAQ content

Use FAQPage only where the page (or page section) actually answers user questions: support articles, product FAQs, pillar FAQ blocks at the bottom of guides. Do not use it on testimonials, marketing copy, or promotional content — Google's documentation specifies it must not be used for advertising.

Step 2. Structure your HTML

<section>
<h2>Frequently asked questions</h2>
<h3>What is GEO?</h3>
<p>GEO is the practice of structuring content so AI systems can understand and cite it.</p>
<h3>How is GEO different from SEO?</h3>
<p>GEO extends SEO by optimizing for citation in AI-generated answers, not only ranking in result lists.</p>
</section>

Step 3. Add JSON-LD

{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is GEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "GEO is the practice of structuring content so AI systems can understand, retrieve, synthesize, and cite it in generated answers."
}
},
{
"@type": "Question",
"name": "How is GEO different from SEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "GEO extends SEO by optimizing not only for search-result ranking but also for citation in AI-generated answers from systems like ChatGPT, Perplexity, and Google AI Overviews."
}
}
]
}

Step 4. Place the script

Embed the JSON-LD as a