Schema Markup for AI

TL;DR — Schema markup is code you add to a page that labels what your content means so machines don’t have to guess. You’ll hear that adding it boosts your odds of getting cited in AI Overviews or ChatGPT. The best evidence says it doesn’t do that directly. What it does do is help AI systems understand who you are and what your pages are — useful, just not the magic switch it’s sold as.

What schema markup is

When you read a page, you can tell a phone number from a price from an author’s name just by looking. A machine can’t — it sees text. Schema markup (also called structured data) is extra code you add to a page that spells it out: “this is the author,” “this is the published date,” “this is the price.” It uses a shared vocabulary from schema.org that many search engines and other documented consumers understand. That does not mean every AI platform reads every type or uses the markup in the same way.

Most of the time it’s written in a format called JSON-LD — a little block of code that sits in the page’s HTML and describes the content without changing how the page looks to a visitor. It still has to describe content readers can actually see on the page. Evidence for this claim Google requires structured data to represent visible page content and does not guarantee feature display. Scope: Google structured-data policies, not claims about every AI system. Confidence: high · Verified: 2026-07-28 Google Search Central: Structured data guidelines

The AI hype vs. what’s real

Here’s the pitch you’ve probably heard: add schema markup and you’ll get cited more in AI search. It sounds plausible — structured data is “AI-readable,” so surely the AI rewards it, right?

The data says no. When researchers at Ahrefs tracked 1,885 pages that added schema and measured their AI citations before and after, the citations basically didn’t move on any tested platform. Google now states even more directly that structured data is not required for generative AI search and that there is no special schema.org markup to add. Evidence for this claim Google says structured data is not required for generative AI search and there is no special schema.org markup to add; existing structured data remains useful for ordinary rich-result eligibility. Scope: Google Search generative AI features; not a claim about every AI platform or documented feed/integration. Confidence: high · Verified: 2026-07-28 Google Search Central: Optimizing your website for generative AI features So if a tool or agency is promising that bolting on schema will get you into AI answers, be skeptical.

What schema actually does

It’s still worth doing — just for the right reasons:

• It can clarify declared entity facts for systems that consume it. Organization and Person markup with a property called sameAs, which links your brand or author identity to authoritative profiles. This can reduce ambiguity in systems that use the markup, but it is not proof of AI citation selection.
• It powers rich results. Star ratings, product cards, breadcrumbs, sitelinks — those visual extras in regular search still come from schema.
• It helps search engines understand your content so it can be categorized and surfaced correctly.

So: keep using schema. Just don’t expect it to be the lever that gets you into the AI answer. Want the deep version — the studies, the Google vs. Bing split, and the exact types that matter? Switch to the Advanced tab.

TL;DR — Google says structured data is not required for generative AI search and there’s no special schema.org markup to add. Evidence for this claim Google says structured data is not required for generative AI search and there is no special schema.org markup to add; existing structured data remains useful for ordinary rich-result eligibility. Scope: Google Search generative AI features; not a claim about every AI platform or documented feed/integration. Confidence: high · Verified: 2026-07-28 Google Search Central: Optimizing your website for generative AI features Bing’s Fabrice Canel is the one rep to confirm schema helps their LLMs. The Ahrefs 1,885-page study found adding JSON-LD moved AI citations a statistically insignificant amount on every platform (−4.6% AIO, +2.4% AI Mode, +2.2% ChatGPT). The most plausible mechanism is entity disambiguation via sameAs feeding Google’s Knowledge Graph — not a proven citation lever, since the Knowledge-Graph-to-AI-Overview chain hasn’t been isolated in any study. Watch out for two traps: feature eligibility can change while a Schema.org type remains valid, and client-side markup may not be processed consistently by every crawler.

Regardless of delivery method, the markup must match content visible on the page. Evidence for this claim Google requires structured data to represent visible page content and does not guarantee feature display. Scope: Google structured-data policies, not claims about every AI system. Confidence: high · Verified: 2026-07-28 Google Search Central: Structured data guidelines

Start from the official position, because it’s clearer than the hype

Google has been unusually blunt here. Its July 2026 guidance says structured data is not required for generative AI search and there is no special schema.org markup to add. Existing structured data remains useful for ordinary rich-result eligibility, and it still has to match what readers can verify on the page. That is longstanding structured-data policy, not an AI-specific tactic.

That doesn’t mean schema is useless to Google. It means Google separates two jobs structured data does: it drives rich results (the appearance enhancement) and it helps Google understand content and entities — “information about the people, books, or companies that are included in the markup.” The second job feeds the Knowledge Graph, and the Knowledge Graph feeds AI Overviews. So there’s a plausible indirect path. There is no documented direct one.

Bing is the one platform that says schema helps its LLMs

This is the cleanest affirmation in the whole space. At SMX Munich in March 2025, Fabrice Canel, Principal Product Manager at Microsoft Bing, confirmed that schema markup helps Microsoft’s LLMs understand content. He’s the only AI-search rep to say it on the record about an LLM specifically — not just about crawling. He paired it with a push on freshness: “Gen AIs value fresh content in particular, partly as a reference check of their LLM training data. Use the API at indexnow.org to push that information as it’s published or updated.”

So when people ask “do LLMs even read schema?”, the honest answer is platform-split: Bing/Copilot, yes, by their own statement; Google, only indirectly via the Knowledge Graph; ChatGPT and Perplexity, unconfirmed either way.

The evidence on citations: the Ahrefs 1,885-page study

This is the most rigorous test I’m aware of. The Ahrefs team (Louise Linehan and Xibeijia Guan, reviewed by Ryan Law, published May 2026) identified 1,885 pages that added JSON-LD schema between August 2025 and March 2026, matched them against ~4,000 control pages with similar prior citation levels, and measured citations 30 days before and after — across four statistical tests (t-test, difference-in-differences, event study, sensitivity analysis).

The headline from the study: “Adding schema produced no major uplift in citations on any platform.” Earlier, a Search/Atlas analysis in December 2024 found the same shape of result — no consistent correlation between schema coverage and citation rates.

The one honest caveat. The study only measured pages already being cited — every treated page had 100+ AI Overview citations before schema was added. So it answers “does adding schema lift citations on pages already in the consideration set?” (no) but it can’t answer “does schema help a page get into that set in the first place?” — that’s still open. The correlation people cite — AI-cited pages are ~3× more likely to have JSON-LD — almost certainly reflects that technically strong sites use schema and publish good content, not that schema is the cause.

The most plausible mechanism: entity disambiguation

If schema doesn’t move citations, why do I still tell people to invest in it for AI search? Because of the one job it’s actually documented to do: help resolve entities — connecting Organization and Person markup to authoritative external IDs so a knowledge graph can tell your company or author apart from a namesake.

sameAs is the property that does this. It’s the most direct way to point at authoritative external identifiers:

• Organization sameAs (priority order): Wikidata Q-number → Wikipedia → LinkedIn company page → Crunchbase → GitHub (for tech companies).
• Person sameAs: LinkedIn → Wikidata (if an entry exists) → ORCID (academic authors) → X → GitHub.

This is the part of schema I’m most confident changes something — it feeds Google’s Knowledge Graph, which Google documents as an input to AI Overviews. But I want to be precise about what’s confirmed and what isn’t: schema’s role in entity resolution for the Knowledge Graph is documented; the Knowledge-Graph-to-AI- Overview-citation chain is a plausible hypothesis, not something any study has isolated and confirmed. Treat it as the best-supported bet, not a guarantee.

One frequently cited example: SchemaApp, a schema vendor, reported that Wells Fargo corrected AI hallucinations about its business hours by adding schema to location pages. That’s a vendor-published case study I haven’t been able to verify independently — treat it as an anecdote consistent with the entity-disambiguation mechanism, not confirmed proof of it.

Which types are worth implementing

There’s no confirmed, universal ranking of schema types by AI-visibility value — no study isolates that. What follows is what each type documentedly does; treat “helps AI” as the plausible entity/rich-result path described above, not a scored priority order:

A note on FAQPage: Google deprecated the FAQ rich result on May 7, 2026. The visual enhancement in the SERP is gone, but the FAQPage schema type itself is still valid — “the markup can stay on your pages without causing problems” — and may still help AI systems identify question-and-answer passages. Don’t rush to strip it out; removing it buys you nothing.

The trap that quietly kills schema for AI: JavaScript

Here’s the implementation detail that catches people. AI-crawler rendering is provider- and version-specific. If your schema is injected client-side, the classic example being Google Tag Manager, then Googlebot (which renders) may eventually see it, but any AI crawler that uses only the raw HTML will miss it. For broad AI-search coverage, server-render schema into the HTML response. If entity disambiguation is the reason you’re doing this, JS-injected schema defeats the purpose.

Use JSON-LD (Google, Bing, and schema.org all prefer it over Microdata/RDFa), keep it server-side, and connect your types with @graph + @id so your Organization, Person, and Article reference each other instead of duplicating data — that connected-graph pattern is the one most associated with Knowledge Graph recognition.

The bottom line

Schema is infrastructure, not a citation cheat code. Implement Organization and Person with real sameAs links, put Article and BreadcrumbList on your templates, render it all server-side, and make it match your visible content. Then stop expecting it to be the thing that gets you into AI answers — that work happens in your content, your brand mentions, and your authority, which I cover across the rest of the AI search optimization cluster.

AI summary

A condensed take on the Advanced version:

• Schema markup ≠ AI citation lever. The Ahrefs May 2026 study (1,885 pages, four statistical tests) found adding JSON-LD moved citations a statistically insignificant amount everywhere: −4.6% Google AIO, +2.4% AI Mode, +2.2% ChatGPT.
• Google’s official line: structured data is not required for generative AI search, and there is no special schema.org markup to add. Existing markup still matters for supported rich results and must match visible content.
• Bing is the exception. Fabrice Canel (Microsoft) confirmed schema helps Bing’s LLMs — the only AI-platform rep to say so on the record.
• The most plausible mechanism is entity disambiguation. Organization and Person with sameAs (Wikidata, Wikipedia, LinkedIn) feed Google’s Knowledge Graph — documented. Whether that graph inclusion drives AI Overview citations is a reasonable hypothesis, not something any study has isolated.
• Correlation ≠ causation. AI-cited pages are ~3× more likely to have schema — but that reflects technically strong sites using both schema and good content.
• Two traps: FAQ rich results were deprecated May 7, 2026 (the FAQPage type still works); and AI-crawler rendering varies by provider, so client-side / Tag Manager schema can be missed — server-render it to maximize coverage.
• What to actually do: Organization + Person + sameAs, Article, BreadcrumbList, JSON-LD, server-side, matching visible text.

Official documentation

Primary-source documentation from the search engines and schema.org.

Google

• Optimizing Your Website for Generative AI Features — Google’s July 2026 statement that structured data is not required for generative AI search and there is no special schema.org markup to add.
• AI Features and Your Website — the source of the “no special schema.org structured data that you need to add” statement.
• Intro to How Structured Data Markup Works — what structured data does for understanding and rich results.
• General Structured Data Guidelines — the “markup must match visible content” policy.
• FAQPage Structured Data — the type’s documentation, post-deprecation.
• Speakable (BETA) — marking audio-suitable sections; still beta, US English only.

Bing / Microsoft

• Marking Up Your Site with Structured Data — Bing Webmaster Help — Bing’s structured data guidance; JSON-LD recommended, must match page context.

schema.org

• schema.org — the shared vocabulary itself.
• Organization · Person · sameAs — the entity-disambiguation core.

Quotes from the source

On-the-record statements from Google and Microsoft on schema and AI.

Google — no special schema for AI features

• “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.” — Google Search Central, AI features documentation. Source

Google — what structured data does

• “Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general, such as information about the people, books, or companies that are included in the markup.” — Google Search Central. Source

Google — FAQ deprecation

• “FAQPage as a Schema.org type is still valid, and the markup can stay on your pages without causing problems.” — as reported by Search Engine Journal on the May 2026 FAQ rich-result deprecation. Coverage

Fabrice Canel, Principal Product Manager, Microsoft Bing (SMX Munich, March 2025)

• Confirmed on stage that schema markup helps Microsoft’s LLMs understand content — the only AI-platform rep to state this about an LLM specifically. Coverage
• “Gen AIs value fresh content in particular, partly as a reference check of their LLM training data. Use the API at indexnow.org to push that information as it’s published or updated.” Coverage

Schema-for-AI implementation checklist

A pass to make sure your structured data actually does its entity-disambiguation job — and doesn’t get silently dropped by AI crawlers:

• Organization schema sitewide, with a populated sameAs array (Wikidata, Wikipedia, LinkedIn at minimum), plus name, url, logo.
• Person schema on author/bio pages, with sameAs (LinkedIn, Wikidata if one exists) and knowsAbout for topical authority.
• Article on content pages — author (linked by @id to the Person), datePublished, dateModified, headline, publisher (linked to the Organization).
• BreadcrumbList on interior pages to signal hierarchy / cluster.
• Schema is server-rendered, not injected client-side via Tag Manager — confirm it’s in the raw HTML (View Source / curl) so coverage does not depend on any AI crawler’s provider-specific JavaScript support.
• Markup matches visible content — no fields describing things not on the page (Google policy; mismatches risk a manual action).
• Format is JSON-LD, ideally connected with @graph + @id.
• FAQPage left in place if you have it — the rich result is gone (May 2026) but the type is still valid; removing it gains nothing.
• Validated in the Rich Results Test and schema.org validator.
• Expectations set: schema is entity infrastructure, not a direct AI citation lever — don’t bolt it onto already-cited pages expecting a lift.

Schema types — cheat sheet

Type → what it declares → what’s actually documented

No study confirms a universal priority order for AI visibility across these types — read the right column as “documented function,” not a ranking.

Fast facts

• Ahrefs study (1,885 pages, May 2026): −4.6% AIO / +2.4% AI Mode / +2.2% ChatGPT — all statistically insignificant.
• Google: “no special schema.org structured data that you need to add” for AI Overviews / AI Mode.
• Bing: Fabrice Canel confirmed schema helps Bing’s LLMs — the one platform that has.
• FAQ rich result: deprecated May 7, 2026; FAQPage type still valid.
• AI-crawler rendering varies by provider → server-render schema so Tag Manager execution is not a coverage dependency.
• Format: JSON-LD, ideally @graph + @id. Must match visible content.

Schema-for-AI mistakes to avoid

Promising a citation boost

Schema helps machines interpret entities and page meaning; it is not a switch that forces an AI answer to cite the page.

Marking up facts users cannot verify

Structured data should represent visible, accurate page content. Do not add awards, reviews, authors, prices, or relationships solely because the vocabulary permits them.

Linking the wrong entity with sameAs

A wrong identifier is worse than a missing one. Confirm that every URL represents the same person, organization, product, or place.

Injecting all markup after client rendering

Search engines may render it, but many AI crawlers will not. Put important JSON-LD in the server-delivered HTML when possible.

Common schema-for-AI problems

The markup validates but describes a different entity

Symptom: Syntax passes while names, URLs, or identifiers point to a namesake. Likely cause: Entity resolution was skipped. Fix: Compare the visible page, canonical URL, official profiles, and sameAs values before correcting the graph.

Structured data is missing from raw HTML

Symptom: Browser tools find JSON-LD but curl does not. Likely cause: A tag manager or client component injects it after load. Fix: render stable entity and page markup on the server, then compare raw and rendered output again.

Rich-results tools report ineligible markup

Symptom: Schema is valid vocabulary but not eligible for a Google rich result. Likely cause: Schema.org validity and Google feature requirements are different checks. Fix: Use the general validator for vocabulary and the Rich Results Test for supported search features; do not equate feature eligibility with AI citations.

Frameworks for schema that supports machine understanding

Entity first, syntax second

1. Identify: Name the real person, organization, product, place, or creative work.
2. Corroborate: Confirm stable facts and authoritative identifiers.
3. Model: Choose the most specific appropriate type and relationships.
4. Expose: Match visible page content and serve important markup in HTML.
5. Validate: Check both Schema.org structure and any feature-specific requirements.
6. Monitor: Recheck when templates or entity facts change.

Separate three outcomes

• Valid markup: The graph follows the vocabulary and syntax.
• Feature eligibility: A search engine may consider the page for a supported rich result when all additional rules are met.
• AI visibility: A model may mention or cite the page based on a much broader retrieval and trust system.

Do not report one outcome as proof of another.

Schema extraction snippets

List JSON-LD blocks in Chrome DevTools

Run in the Console:

[...document.querySelectorAll('script[type="application/ld+json"]')].map((el, index) => ({ index, json: JSON.parse(el.textContent) }))

Check whether JSON-LD exists before rendering

Run in a terminal:

curl -sS https://example.com/page/ | grep -n 'application/ld+json'

If the rendered DOM contains markup but this response does not, the implementation is client-dependent.

Extract declared types from a crawl

Use this regular expression against JSON-LD source. Capture group 1 returns a string or array value following @type:

"@type"\s*:\s*("[^"]+"|\[[^\]]+\])

Parse JSON for production analysis; regex is only a quick extraction aid.

Tools for schema and AI understanding

• Schema Markup Validator: Check JSON-LD structure, vocabulary, and graph issues without promising a search feature.
• Schema Markup Generator: Create a starting graph from facts you have already verified against the visible page.
• Rich-Result Eligibility Checker: Separate Google’s supported rich-result requirements from general schema validity.
• Entity Coverage Analyzer: Review whether the page clearly establishes the entities and relationships the markup describes.
• Raw-response and rendered-DOM comparison: Confirm important JSON-LD is available without depending on client-side execution.

Validate a schema change

Test graph validity and page agreement

Test to run: Validate the JSON-LD, then compare every important property with the visible page. Expected result: The graph parses and all stated facts are accurate and user-verifiable. Failure interpretation: Syntax is broken or markup overstates the content. Monitoring window: Immediate. Rollback trigger: A release asserts a wrong entity, unsupported fact, or invalid graph.

Test server delivery

Test to run: Fetch the page without JavaScript and locate the intended JSON-LD. Expected result: Stable entity and page markup appears in the response. Failure interpretation: Non-rendering crawlers cannot receive the change. Monitoring window: Immediate after deployment. Rollback trigger: Previously server-visible markup becomes client-only.

Test entity identifiers

Test to run: Open each sameAs, url, and external identifier and verify the entity match. Expected result: Every edge resolves to the same intended entity. Failure interpretation: The graph connects a namesake or obsolete profile. Monitoring window: Immediate and after rebrands. Rollback trigger: Any identity edge points to an unrelated entity.

Test yourself: Schema Markup for AI

Resources worth your time

Related Ahrefs writing

• We Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved. — Louise Linehan & Xibeijia Guan, May 2026. The controlled study at the center of this article.
• Schema Markup: What It Is & How to Implement It — the implementation walkthrough (Despina Gavoyannis, Chris Haines).
• What is Structured Data? — the glossary primer.

Official references

• schema.org — the vocabulary.
• Google — AI Features and Your Website — Google’s stated position on schema and AI.

From others

• How schema markup fits into AI search — without the hype — Search Engine Land — also references the December 2024 Search/Atlas study finding no consistent citation correlation.
• What 2025 Revealed About AI Search and the Future of Schema Markup — SchemaApp — the Wells Fargo entity-correction case.
• Microsoft Bing/Copilot use schema for its LLMs — Search Engine Land — coverage of Fabrice Canel’s SMX Munich confirmation.
• Schema Helps Microsoft’s LLMs (Copilot) Understand Your Content — Search Engine Roundtable — Barry Schwartz’s write-up of the Bing/Copilot schema confirmation.
• Google Confirms: Structured Data Still Essential in AI Search Era — Search Engine Journal — coverage of Google Search Central Live Madrid 2026 guidance.
• Schema Markup Has No Meaningful Impact on AI Citations — Stan Ventures — independent summary of the Ahrefs findings.
• Structured Data in the AI Search Era — BrightEdge — enterprise perspective on schema in the AI search transition.

Stats worth citing

• Adding schema barely moved AI citations. The Ahrefs study of 1,885 pages that added JSON-LD (vs. ~4,000 controls, four statistical tests) measured −4.6% on Google AI Overviews, +2.4% on AI Mode, and +2.2% on ChatGPT — all statistically insignificant. “Adding schema produced no major uplift in citations on any platform.” Source
• The “already cited” caveat. Every treated page in that study already had 100+ AI Overview citations before adding schema — so the study tests pages already in the consideration set, not whether schema helps a page enter it. Source
• Correlation, not causation. Across Ahrefs’ dataset, AI-cited pages are nearly 3× more likely to carry JSON-LD than non-cited pages — a reflection of technically strong sites, not a causal schema effect. Source
• An earlier signal pointed the same way. A Search/Atlas analysis (December 2024) found no consistent correlation between schema coverage and AI citation rates. Coverage

Schema Markup for AI

Schema markup (structured data) is machine-readable code — usually JSON-LD — that labels what your content means using the schema.org vocabulary. For AI search it's infrastructure for entity disambiguation, not a direct citation lever: controlled studies found no meaningful uplift in AI citations from adding it.

Related: AI Search Optimization, AI Search, Entity SEO, Structured Data

Schema Markup for AI

Schema markup (also called structured data) is machine-readable code added to a page — typically as JSON-LD inside a <script type="application/ld+json"> tag — that uses the vocabulary at schema.org to describe what a page is about in a form search engines and AI systems can parse without ambiguity. Where a human reads a paragraph and infers it’s a recipe, a machine reads a Recipe type with recipeIngredient and cookTime properties and knows.

For AI search, the honest framing is that schema is plumbing, not a magic switch. Google states plainly that there’s “no special schema.org structured data that you need to add” to appear in AI Overviews or AI Mode, and the most rigorous test to date — Ahrefs’ May 2026 study of 1,885 pages — found that adding schema produced no statistically significant change in citations on Google AIO, AI Mode, or ChatGPT. The correlation people point to (AI-cited pages are ~3× more likely to have schema) reflects that technically strong sites tend to use both schema and produce good content, not that schema causes citations.

Where schema earns its place is entity disambiguation. Organization and Person markup with the sameAs property — links to your Wikidata, Wikipedia, and LinkedIn identities — helps anchor your entity in Google’s Knowledge Graph, which Google documents as an input to AI Overviews. That’s the most plausible mechanism for schema mattering to AI search — it’s documented at the entity-resolution step, but the Knowledge-Graph-to-AI-citation link itself hasn’t been isolated by any study, so treat it as a hypothesis, not a guarantee. Microsoft’s Fabrice Canel is the one AI-platform rep to explicitly confirm (at SMX Munich, March 2025) that schema helps Bing’s LLMs understand content. One practical catch: AI-crawler JavaScript support is provider- and version-specific rather than uniform, so schema injected client-side (e.g. via Tag Manager) risks being invisible to crawlers that only fetch raw HTML — server-rendering it is the safer default.

Related: AI Search Optimization, AI Search, Entity SEO, Structured Data

Changelog