← Research Lab·Research Lab · Technical guide

Structured data for AEO: what markup does and does not do

Markup makes entities explicit to a machine and grants Search eligibility — it is not a direct boost in AI answers. Here is the line between real value and overclaim.

May 2026·6 min read

"Add Schema and you will land in AI Overviews" is a common but inaccurate message. Without markup, entities reach the search engine less explicitly — which is not a condition of AI visibility. And some schemas, FAQ rich results among them, no longer produce a Google rich-result effect at all.

What structure actually gives you

Markup does not push a page forward — it provides explicit clues. Google's structured data documentation explains that markup helps the system understand a page's content and can grant eligibility for rich results [68]. That is technical clarity and Search eligibility, not a lever that guarantees citation in an AI answer.

There is no special schema for AI Overviews or AI Mode

This is the most frequent overclaim. Google Search Central documents plainly that AI Overviews and AI Mode have no special schema.org markup and no technical requirements beyond baseline SEO [65]. Do not sell an "AI schema" — there is none; the same technical base that serves ordinary Search is what works.

FAQPage is no longer a Google rich-result lever

An FAQ content block is still useful, but JSON-LD FAQPage has changed status. Per Google's documentation, FAQ rich results stopped appearing in Google Search on 7 May 2026, and the reporting and support are being withdrawn [68]. Keep the visible FAQ content; treat FAQPage as optional semantics — useful for non-Google consumers — rather than a Google rich-result lever.

Machine readability is its own goal

A site is read by more than people. Salemi et al. examine search not only for humans but for machine consumers, RAG systems included [17]. Clear entities, definitions and structured facts make content fit for machine use, whatever the status of any particular rich result.

A public site as a source for assistants

Structured public content feeds corporate assistants. Microsoft Copilot Studio documents how Copilot can use public websites for generative answers [73]. Clearly structured public content becomes a source not only for search but for custom AI assistants.

Summary: value without overclaim

Helps Google understand the page

Yes [68].

Grants eligibility for rich results

Yes, for the applicable types [68].

A special schema exists for AI Overviews / AI Mode

No [65].

FAQPage produces a Google rich result

Not any more, since 7 May 2026 [68].

Markup is a direct boost in AI answers

Unsupported [65, 68].

Sources (E-E-A-T)

68 · Google Search Central

Structured data: explicit clues, rich-result eligibility; FAQ rich results removed 7 May 2026.

65 · Google Search Central

No special schema and no requirements beyond baseline SEO for AI Overviews / AI Mode.

17 · Salemi et al., 2024, arXiv

Search for machine consumers and RAG. arxiv.org/abs/2405.00175

73 · Microsoft Copilot Studio

Public websites as a source for generative answers.

Frequently asked questions

Will structured data help me into an AI answer?

Markup gives explicit clues and Search eligibility, but it is not a direct AI boost: there is no special schema for AI Overviews or AI Mode, and no requirements beyond baseline SEO [65, 68].

Should I add JSON-LD FAQPage?

Visible FAQ content, yes. JSON-LD FAQPage only optionally: FAQ rich results were removed on 7 May 2026, so it is no longer a Google rich-result lever [68].

Is there a separate "schema for AI"?

No. Google documents it directly: AI Overviews and AI Mode have no special schema.org markup and no technical requirements beyond baseline SEO [65].

Then why bother with structured data for GEO?

It makes entities and facts explicit for machine use, including RAG systems and custom assistants — clarity, not a guarantee of citation [17, 73].