Schema markup does not get you into AI answers. Google states directly that no special structured data is needed for AI Overviews or AI Mode. What schema still does is earn rich results in ordinary search and confirm which entity you are. Organization, LocalBusiness, Product, Article and a correct sameAs list do almost all of the work.
Two different questions get mashed into one every time schema comes up, and the confusion is where the wasted money lives.
The first question is whether structured data influences rich results — the star ratings, prices, event dates and breadcrumbs that appear in normal blue-link results. The answer there is yes, unambiguously and by design. That is what the markup is for.
The second question is whether structured data influences AI answers — AI Overviews, AI Mode, and the answer engines outside Google. That is a different question with a different answer, and the honest version of it is less flattering than most schema pitches.
What Google actually says about schema and AI
Google published a guide called Optimizing for generative AI search. It says: “Structured data isn’t required for generative AI search, and there’s no special schema.org markup you need to add.” It then adds that it’s still a good idea to use it, because it makes you eligible for rich results in Google Search.
Google’s AI features documentation is blunter: “You don’t need to create new machine readable files, AI text files, or markup to appear in these features. There’s also no special schema.org structured data that you need to add.” To appear as a supporting link, a page has to be indexed, eligible for Search, and able to show a snippet. That is the stated bar.
So the accurate position is this: schema is a rich-results tool that Google recommends you keep using, not an AI-visibility tool. Anyone selling schema as the way into AI answers is selling something Google has explicitly said is not required. Whether it helps at the margin — by making a page easier to parse, or by making an entity easier to reconcile — is a practitioner theory, not a documented mechanism. Treat it as a theory.
The types that earn their keep
Google’s structured data gallery lists roughly two dozen supported features. Most sites need four or five of them.
Organization
The one type nearly every site should have and most don’t do properly. Google says some Organization properties are used “behind the scenes to disambiguate your organization from other organizations,” while others influence what shows in results and in your knowledge panel — including which logo gets picked. Put it on one page, sitewide, with name, logo, URL, contact details and sameAs.
LocalBusiness
For anyone with a location or a service area. Google documents it as helping pages appear in a knowledge panel and in business carousels. It does not replace your Google Business Profile — the map pack is a separate system — but it makes the business on your website and the business on the profile unmistakably the same one.
Product
The highest-value markup on the list, because price, availability and review ratings show up directly in results. Google notes that some experiences combine data from structured data and Merchant Center feeds, and that supplying both “maximizes your eligibility to experiences and helps Google correctly understand and verify your data.” If you sell things, this is where the effort goes.
Article and BlogPosting
Worth adding, worth low expectations. Google says it helps it “understand more about the web page and show better title text, images, and date information.” There are no required properties and no markup requirement for Top stories. It is cheap, it is usually automatic in a CMS, and it is not a lever.
Person and ProfilePage
Useful on author bios and team pages. Google’s ProfilePage documentation uses Person or Organization as the main entity and supports name, alternateName, identifier and sameAs. This is the markup that ties a byline to a real, findable person.
FAQPage
Gone. See below.
sameAs is the underrated one
Everything above is about a search engine answering one question: which known thing is this page about. That is entity resolution, and sameAs is the property that does it. It points from your entity to other pages about the same entity — your LinkedIn company page, your Crunchbase entry, your Wikipedia article if you have one, your author’s profiles.
Google is explicit about this for authors: in its author markup guidance it says “Google can understand both sameAs and url when disambiguating authors” and recommends adding more than just a name so it can tell who the author is.
Two rules make sameAs actually work. Point only at profiles you control or that genuinely describe you — a padded list of thin directory profiles is noise. And make the links reciprocal where you can: your site names the profile, the profile names your site. A one-way claim is weaker than a matched pair.
This is the part of schema most likely to matter for how machines describe your business, including machines that are not Google. It is also the part almost nobody bothers to get right.
What Google has actually deprecated
This is where a lot of published advice is now wrong, so the dates matter.
- HowTo is finished. In August 2023 Google announced it was dropping HowTo rich results and narrowing FAQ rich results. Per Google’s documentation update log, the HowTo documentation was removed on September 14, 2023.
- FAQ was narrowed, then killed. The 2023 change limited FAQ rich results to well-known, authoritative government and health websites. Google then added a deprecation notice in May 2026, the feature stopped appearing in Search on May 7, 2026, and the documentation was removed on June 15, 2026.
- Others went with them. Google’s update log records removals for course info, estimated salary, learning video, special announcement and vehicle listing in September 2025, and practice problems after November 2025. The sitelinks search box was retired in 2024.
Unused markup is not a penalty — Google has consistently said structured data it doesn’t use doesn’t cause problems. But if an agency is still charging you to build out FAQ blocks for the rich result, you are paying for a feature that no longer exists.
The validation workflow
- Run the page through the Rich Results Test. This tells you one thing only: whether Google sees a supported rich result on this URL. It does not validate schema in general, and it will show nothing for valid markup Google has no feature for.
- Run the same page through the Schema Markup Validator. This checks the markup against schema.org itself, so it catches structural errors and typos the Google tool ignores because it never looked at that type.
- Check the rendered page, not the source. If your markup is injected by a tag manager, test the live URL rather than pasting code, so you see what a crawler sees.
- Watch Search Console’s enhancement reports at the site level. One valid page proves syntax. The report proves the template is right across a few thousand pages, which is the failure mode that actually costs you.
- Re-test after any template change. Schema breaks silently — nothing on the page looks different when a field stops populating.
Where the effort gets wasted
Marking up pages that have no eligible feature. Building elaborate nested graphs of Service, Offer and WebPage entities for a site that needs Organization and nothing else. Adding aggregateRating that isn’t backed by real, visible reviews on the page — that is a guidelines problem, not a clever one. Buying schema as a monthly line item on a site where it was finished in an afternoon two years ago. And treating schema as the AEO strategy, when Google has published, in plain English, that it isn’t required for any of it.
The honest scope of this
Schema is plumbing. It is cheap, it should be correct, and correct is a state you reach and then leave alone. It will not rescue a page that has nothing to say, and it will not put you in an AI answer that would otherwise skip you. If a proposal puts structured data at the top of the plan, ask what specific rich result it is meant to earn. If there isn’t one, the work is maintenance, and it should be priced like maintenance.