There is a lot of nonsense circulating about schema markup and AI Overviews. ‘Add schema and you’ll appear in the AI answers’ is the most persistent one. It is not true. In this article I give you the actual rules: what schema does and does not do for AI Overviews, which types still work, which are deprecated, and where you should really spend your time.
I do this work daily in technical audits under JSResults. And schema in particular is where I see clients waste a lot of time on the wrong things. Let me set it straight, with Google’s own documentation as the basis.
The biggest myth: schema is not an entry ticket
Let me get straight to the point. Google itself says, in the official documentation on AI features, that you do not need special schema to appear in AI Overviews or AI Mode. There is no ‘AI Overviews schema’. You do not have to add new machine-readable files or markup.
AI Overviews run on the same systems as the regular search results. Rank well in Google and you stand a chance in the AI summary. Schema is not a switch you flip for that. Anyone who promises otherwise is selling air.
What schema does do
Does this mean schema is pointless? No, absolutely not. It just does something different from what people think. Schema has three real functions, and ‘access to AI Overviews’ is emphatically not one of them:
For the AI side, mainly the first two count. Google’s AI systems read your schema as a trust and entity signal, not as a trigger to show you. That is an important difference, and it lines up with how AI judges your entity.
The real rule: schema must match what the visitor sees
If there is a golden rule, this is it. Google checks your schema against the visible content of your page. Claim something in your markup that is not on the page, and it works against you. It undermines the very trust you are trying to build.
So: no reviews in your schema that appear nowhere on the page. No author in your markup that you do not show. Accurate, correct schema that maps one to one onto your content, that is what helps. No more, and certainly no less.
Which types work, and which don’t
Here is the overview you really need. Pay special attention to the bottom two rows, because that is where it often goes wrong.
| Schema type | Status in 2026 | What it is useful for |
|---|---|---|
| Organization | Works | The basis of your entity. Tells Google who you are, with logo and profiles. |
| Person / Author | Works | Ties content to a real author. A strong E-E-A-T signal. |
| Article / BlogPosting | Works | Helps Google understand your article, with author and dates. |
| BreadcrumbList | Works | Shows the path structure and can produce a rich result. |
| Product + Review | Works | For web shops. Price, stock and ratings as a rich result. |
| LocalBusiness | Works | For local businesses. Name, address, opening hours, location. |
| FAQPage | Rich result ends (May 2026) | Markup stays valid for understanding, but no longer produces a rich result. |
| HowTo | Deprecated (since 2023) | No longer produces a rich result in Google. |
Watch FAQ and HowTo. Google dropped HowTo rich results back in 2023, and as of May 7, 2026 it also stops FAQ rich results. The markup itself stays valid and can still help with understanding and for AI, but don’t count on those eye-catching expandable questions in Google anymore. Anyone still adding FAQ schema in 2026 purely for the rich result is too late.
Where you do spend your time
Based on what I see in audits, this is the order that delivers the most. At the top, the basics every site should have.
- Organization and Person or Author. This is your entity foundation. Establish who you are, connect your logo, profiles and authors. This is the strongest AI signal.
- Article or BlogPosting with author link. On every article, with a date and a real author that points to an author page.
- BreadcrumbList. Simple, safe, and it helps Google understand your structure.
- Product, Review or LocalBusiness, if that fits you. For web shops and local businesses these still produce real rich results.
- Make sure everything matches the visible page and validate it. Accurate over abundant.
How to check it
Never place schema without validating. These are the tools I use:
- Google Rich Results Test: checks whether your markup qualifies for the still-supported rich results.
- Schema Markup Validator by schema.org: checks whether your JSON-LD is technically correct, also for types without a rich result.
- Google Search Console: shows which enhancements Google recognises on your site and where the errors are.
My advice: validate every new schema before you put it live, and after publishing check in Search Console whether Google picks it up. This belongs to a healthy technical SEO foundation, alongside speed and structure.
Common mistakes
- Placing schema that doesn’t match the page. The fastest way to squander trust.
- Placing FAQ or HowTo schema purely for the rich result. That effect is gone.
- Thinking schema pushes you into AI Overviews. It is an understanding and trust signal, not an entry ticket.
- Loose, unconnected schema. Link your Organization, Person and Article together into a coherent whole.
- Never validating. One typo in your JSON-LD and the whole block is ignored.
Frequently asked questions
Do I need schema to appear in AI Overviews?
No. Google itself says no special schema is needed for AI Overviews or AI Mode. Schema helps Google understand your content and verify your entity, but it is not a requirement to be shown.
Does FAQ schema still work in 2026?
The markup is still valid, but Google stops FAQ rich results as of May 7, 2026. So you will no longer get expandable questions in the search results. For understanding and AI it can still help, but not for that rich result.
Which schema type is the most important?
Organization and Person or Author. Together they form your entity foundation, and that is the strongest signal towards both Google and AI systems.
What is the most important rule for schema?
Your schema must match exactly what the visitor sees on the page. Google checks this, and a mismatch undermines your trust rather than strengthening it.
Sources
This article is based on my own audit practice and on Google’s official documentation. I checked the facts against:
- Google Search Central, AI Features and Your Website: developers.google.com
- Google Search Central Blog, Changes to HowTo and FAQ rich results (2023) and the announcement about ending FAQ rich results in 2026.
- Google Search Central, documentation on structured data and the Rich Results Test.