Google states plainly that no special schema markup is required to appear in AI Overviews or AI Mode: "There's also no special schema.org structured data that you need to add" (Google Search Central, AI features documentation). If you have been implementing FAQPage or HowTo schema specifically to chase AI Overview citations, that premise does not hold — and the underlying rich results are gone too. The FAQPage rich result, once narrowed to government and health sites in 2023, was removed from Google Search entirely on 7 May 2026. The HowTo rich result has shown nothing on mobile or desktop since September 2023.
None of this means FAQPage and HowTo schema are pointless — Google says the markup "can stay in place" and continues to help the company understand your page, and clear Q&A/step structure is good practice independent of any schema wrapper. But the pitch has to be honest: implementing this JSON-LD will not, on its own, get you into an AI Overview. What earns citation is well-structured, extractable, directly-answering content — the schema is a bonus layer, not the mechanism.
This guide gives you the current, source-linked status of each schema type, copy-ready validated JSON-LD, a decision table for which type fits which content, and the validation tools that still actually work in 2026 (some no longer do). If you run AI chatbots on your website, the final section shows how to connect your knowledge base to your content pipeline.
Table of Contents
- How Google AI Overviews Work in 2026
- Why Schema.org Still Matters Despite What Google Says
- FAQPage Schema: Complete Guide
- HowTo Schema: Complete Guide
- Decision Table: Which Schema for Which Content
- Other Schemas That Help With AI Overviews
- Practical Implementation: Jinja2, PHP, JavaScript, and Scale
- Validation and Monitoring
- Common Errors and How to Avoid Them
- FAQ
How Google AI Overviews Work in 2026
AI Overviews are the production evolution of what Google called SGE (Search Generative Experience) during its 2023 beta. Rolled out broadly in May 2024 in the United States, then progressively across the UK and Europe, they are now the first visible element on a large and growing share of SERPs. Third-party trackers disagree sharply on the exact figure because of differing methodologies and keyword sets — BrightEdge reported roughly 31% in early 2025, rising to around 48% by March 2026, while other trackers (Conductor, Safari Digital) report figures closer to 21–25% for the same period (verified 2026-07-16). Treat any single precise percentage you see quoted, including ours, with that caveat.
The mechanism is fundamentally different from a classic search engine. When a user asks a complex informational query, Google no longer just ranks pages: it generates a real-time synthesis drawn from several selected sources, cited below the AI block. This is Retrieval-Augmented Generation (RAG) applied directly to search.
What types of queries trigger AI Overviews?
AI Overviews appear primarily on informational queries: "how to do X", "what is Y", "what's the difference between X and Z", "best way to...". Pure transactional queries ("buy", "pricing", "quote") generate them far less often. Local queries ("pizza near me") and navigational queries ("Gmail login") almost never trigger them.
This is precisely where FAQPage and HowTo schemas become strategic: your pages that answer questions are exactly the ones AI Overviews are trying to cite.
How Google selects its sources for AI Overviews
Google does not disclose its selection algorithm, and — importantly — Google's own documentation is explicit that no schema markup is required or specially rewarded for AI Overview inclusion: "the same fundamental SEO best practices that apply to Search apply to your appearance in AI Overviews" (Google Search Central). Based on that guidance and general helpful-content principles, the patterns that correlate with citation are the same ones that correlate with good organic rankings generally:
- Topical authority: sites that cover a specific domain in depth are generally favored over generalist publications.
- Extractable content: short, direct, clearly delimited passages are easier to lift into a summary than dense wall-of-text content.
- Clean HTML structure: genuine headings, lists, and Q&A formatting help any crawler — human or AI — parse your page, independent of whether you also add JSON-LD.
- Freshness: an accurate, actually-updated
dateModifiedproperty is a legitimate signal for content that has genuinely changed — but backdating it without real edits is a documented spam pattern Google's guidelines warn against. - E-E-A-T: identified author, cited sources, domain-level coherence and depth.
What is not on this list, per Google's own statement: FAQPage or HowTo JSON-LD as a direct lever for AI Overview selection. Treat the rest of this guide as "how to implement this schema correctly and know its real, current limits" rather than "how to hack your way into an AI Overview."
Is Schema.org Still Worth Implementing? What Google Actually Says
Google has been consistent on two separate points, and it is worth keeping them separate. First, structured data is not a ranking factor — John Mueller (Google Search Relations) has repeated this for years. Second, and more specific to this guide, Google's AI features documentation states there is no special schema required to appear in AI Overviews or AI Mode. Neither statement leaves room for "but it secretly helps AI citation" — Google does not claim that, and no independent, methodologically transparent study confirms it either. We are not going to assert otherwise.
So why implement FAQPage, HowTo, or Article schema at all? Three honest, more modest reasons:
Reason 1 — Removing ambiguity for any machine reader, not just Google's ranking algorithm
A FAQPage schema tells any parser — Google, another search engine, a third-party AI crawler — "this text is a question, this text is its answer" explicitly, instead of leaving it to infer that from your HTML. This is a legitimate technical benefit for parsing accuracy. It is not evidence that doing so increases your odds of being cited in an AI Overview specifically — Google has not made that claim.
Reason 2 — Machine-readable E-E-A-T signals
An Article schema with complete author, datePublished, dateModified, and publisher fields gives Google (and other crawlers) a structured version of information that's already on your page in HTML. It is a convenience layer on top of E-E-A-T signals that must already exist in the visible content — the schema does not create trust that isn't there.
Reason 3 — Forcing yourself to write extractable content
The real value of building a FAQPage or HowTo block is usually the discipline it imposes: a genuine question, a direct and complete answer, one idea per unit. That structure helps readers and any extraction system, schema or not. If you write that way, the JSON-LD is a low-cost, harmless addition — but the writing discipline is what does the work, not the markup.
To understand the broader logic of optimizing for generative AI search engines, our article on GEO (Generative Engine Optimization) covers what independent research (not just markup) suggests actually correlates with being cited by ChatGPT, Perplexity, and Gemini.
FAQPage Schema: Complete Guide
What is the FAQPage schema and what does it actually do?
The FAQPage type from schema.org describes a page whose primary content is a list of questions and answers. It is implemented as JSON-LD inside a <script type="application/ld+json"> tag, placed in the <head> or at the end of <body>. Google reads it without executing JavaScript — JSON-LD is rendered immediately visible to the crawler.
When to use the FAQPage schema
Use FAQPage in these situations:
- Dedicated FAQ pages: a standalone "/faq" or "/help" page with answers written by your team.
- Blog articles with a Q&A section: if your article contains a "Frequently Asked Questions" section with complete answers.
- Landing pages addressing common objections: sales or pricing pages that answer prospect questions directly.
- Technical documentation pages: only if you are the sole author of both the questions and the answers.
- Product support pages: provided that answers are written by your team, not submitted by users.
When NOT to use the FAQPage schema
Google's official guidelines (developers.google.com/search/docs/appearance/structured-data/faqpage) are explicit about prohibited cases:
- Forums and community Q&A sites: if multiple users can submit competing answers to the same question (Stack Overflow, Quora, Reddit).
- User-generated content: comments, reviews, reader contributions.
- Promotional content disguised as FAQ: questions engineered solely to promote a product without genuinely answering user intent.
- Questions whose answers are not visible on the page: the JSON-LD content must exactly match the content visible to users in the HTML.
Critical context for 2026: the FAQPage rich result no longer exists on Google Search, for anyone. Google restricted it to government and health domains in September 2023, then removed it from Search entirely on 7 May 2026 — Search Console stopped reporting it in June 2026, and API support ends in August 2026 (Google's FAQPage documentation). Google has said the markup "can stay in place" without causing harm and continues to help the company parse your content, but it will not produce a visual result for any site, government or otherwise, and Google has made no statement tying it to AI Overview citation.
Complete FAQPage JSON-LD — copy-ready example
Here is a validated example with required and recommended properties, using English-language questions relevant to an AI chatbot SaaS context:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is a RAG chatbot and how is it different from a standard AI chatbot?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A RAG (Retrieval-Augmented Generation) chatbot combines a large language model with a custom knowledge base. Unlike a standard rule-based chatbot or a generic LLM, a RAG chatbot searches your internal documents before generating a response — which allows it to provide accurate, grounded answers about your products, services, or processes, without hallucinating information it was never trained on."
}
},
{
"@type": "Question",
"name": "How long does it take to deploy an AI chatbot on a website?",
"acceptedAnswer": {
"@type": "Answer",
"text": "With a platform like Heeya, the initial deployment of an AI chatbot takes between 5 and 30 minutes: create the agent, upload your knowledge base documents, customize the widget appearance, and embed it on your site with a single script tag. Advanced configuration — tone, behavior, form capture tools — requires an additional 1 to 2 hours."
}
},
{
"@type": "Question",
"name": "Does the FAQPage schema improve Google rankings?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Google confirms structured data is not an algorithmic ranking factor, and its AI features documentation states no special schema is required to appear in AI Overviews either. FAQPage schema no longer produces any rich result in Google Search as of May 2026. Its remaining value is helping machine parsers read your content unambiguously, not a guaranteed visibility boost."
}
}
]
}Content rules you must follow
- The value of
namemust be the complete question, phrased as a genuine user question. - The value of
textinsideacceptedAnswermust match word-for-word (or be a direct subset of) the visible text on the page. - Limited HTML is allowed inside
text:<h1>–<h6>,<br>,<ol>,<ul>,<li>,<a>,<p>,<div>,<b>,<strong>,<i>,<em>. - Only one FAQPage instance per URL — no duplicate FAQPage schemas on the same page.
- Do not mark up the same FAQ content across multiple different URLs on your site.
How to validate your FAQPage schema
Two tools, in this order — note that neither reports FAQPage rich-result eligibility anymore, since the feature was removed in May 2026:
- Schema Markup Validator (validator.schema.org): conformance validation against schema.org specs — this is now your primary tool for FAQPage syntax correctness.
- Rich Results Test (search.google.com/test/rich-results): Google dropped FAQPage support from this tool in June 2026. Use it for other schema types that still generate rich results (Product, Recipe, Article).
After validation, submit your URL in Google Search Console (URL Inspection → Request Indexing) to accelerate crawl pickup — the "Rich results" report itself stopped tracking FAQPage in June 2026.
HowTo Schema: Complete Guide
What is the HowTo schema and where does it stand in 2026?
The HowTo schema describes a sequential step-by-step procedure: a tutorial, a recipe, an installation guide, assembly instructions. Google removed the HowTo rich result from mobile and desktop Search results in September 2023. In 2026, HowTo steps produce no visual rich result on any surface — this is not a partial reduction, it is a complete removal that predates this article.
As with FAQPage, Google has not stated that HowTo markup improves AI Overview citation. What it can still do is remove ambiguity for any parser reading your page: a HowTo schema marks steps as steps, in order, rather than leaving that structure to be inferred from your HTML.
Legitimate use cases for the HowTo schema
- Technical tutorials: installing software, configuring an API, setting up a developer tool.
- Step-by-step guides: product onboarding flows, documented internal procedures.
- Recipes and manufacturing instructions: the most classic pairing (time, ingredients, steps).
- Business procedures: "how to write an invoice", "how to submit an insurance claim", "how to create a project proposal".
Do NOT use HowTo for opinion pieces, comparisons, or content without a clear sequential dependency between steps.
Complete HowTo JSON-LD — copy-ready example
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Deploy an AI Chatbot on Your Website in 5 Steps",
"description": "A practical guide to building and embedding a RAG chatbot on your website using Heeya, without requiring advanced technical skills.",
"totalTime": "PT30M",
"estimatedCost": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": "0"
},
"tool": [
{
"@type": "HowToTool",
"name": "Heeya account (free to start)"
},
{
"@type": "HowToTool",
"name": "Your knowledge base documents (PDF, DOCX, TXT)"
}
],
"step": [
{
"@type": "HowToStep",
"name": "Create your agent",
"text": "Log in to your Heeya dashboard and click 'New Agent'. Give it a name, a description, and write your 'System Guidance' — the instructions that define your chatbot's personality, scope, and boundaries.",
"url": "https://heeya.fr/en/solutions/chatbot#step-1",
"image": "https://heeya.fr/static/img/blog/heeya-blog-default.webp"
},
{
"@type": "HowToStep",
"name": "Upload your knowledge base",
"text": "In the 'Files' tab, import your documents (PDF, DOCX, PPTX, TXT). Heeya automatically splits them into chunks, generates vector embeddings, and stores them in your dedicated Qdrant collection. You can also scrape URLs from your existing website.",
"url": "https://heeya.fr/en/solutions/chatbot#step-2",
"image": "https://heeya.fr/static/img/blog/heeya-blog-default.webp"
},
{
"@type": "HowToStep",
"name": "Test your chatbot",
"text": "Use the preview chat inside the dashboard to check the quality of responses. Ask the questions your typical visitors ask. Adjust the System Guidance if the answers drift or miss the mark.",
"url": "https://heeya.fr/en/solutions/chatbot#step-3",
"image": "https://heeya.fr/static/img/blog/heeya-blog-default.webp"
},
{
"@type": "HowToStep",
"name": "Customize the widget",
"text": "In the 'Integration' tab, configure the widget appearance: primary color, welcome message, avatar, and position. Match it to your brand identity.",
"url": "https://heeya.fr/en/solutions/chatbot#step-4"
},
{
"@type": "HowToStep",
"name": "Embed on your website",
"text": "Copy the generated embed script and paste it before the closing 