AEO & GEO
Structured data that gets you cited by AI answers
AI Overviews and ChatGPT quote sources. Schema does not buy you a citation, but it makes your pages easy to read, trust, and reuse. Here is what to implement.
TL;DR
- Schema does not directly rank you or guarantee a citation. It makes your content machine-readable, so AI answer engines can extract a clean fact, attribute it, and reuse it with confidence.
- The schema types that matter most for AI answers: Article, FAQPage, HowTo, Organization, and BreadcrumbList. Get these right before anything exotic.
- AI Overviews and ChatGPT favour sources that answer the question directly, near the top, in plain language, with clear authorship and a consistent entity. Schema reinforces all of that.
- Mark up what is genuinely on the page, keep it accurate, and validate it. Schema that lies or drifts from the visible content gets ignored or penalised.
- See how we approach AEO and GEO, and our broader AEO, GEO and SEO guide for the content side.
How AI answers pick sources
Answer engines reward content that is easy to extract.
AI Overviews and assistants like ChatGPT do not read your page the way a person does. They look for a clear, self-contained answer to the question, prefer it near the top, and need to know who said it and whether the source is consistent and trustworthy. Pages that bury the answer under three paragraphs of preamble, or that need the whole article read to extract one fact, are harder to quote and get cited less.
Structured data is not a ranking trick. It is a translation layer: it tells the engine "this block is the question, this is the answer, this is the author, this is the organisation behind it". A page that is already clear to a human, then marked up accurately, is the one that gets reused in an answer. Schema on a vague page does nothing; clear writing plus schema is the combination that works.
This is why AEO and GEO sit on top of good SEO, not beside it. The same things that help a person (a direct answer, a clear heading, real authorship) help the machine. Schema makes those signals explicit.
Mark up what is genuinely on the page, keep it accurate, and validate it. Schema that lies or drifts from the visible content gets ignored.
The schema that matters
Five types to implement before anything else.
01
Article
Mark up guides and posts as Article (or its subtypes). Include headline, description, author, datePublished, dateModified, and image. This tells answer engines who wrote it and when it was last reviewed, which matters for time-sensitive topics. Keep dateModified honest: bump it when you genuinely update the content, not as a trick.
02
FAQPage
When a page genuinely answers a set of questions, FAQPage markup pairs each question with its answer in a structure the engine can lift directly. This is the most reusable format for AI answers because it maps one question to one clean answer. Only mark up questions that are actually visible and answered on the page.
03
HowTo
For step-by-step content, HowTo markup names each step in order. Answer engines use it to reconstruct a procedure, and it pairs naturally with the way assistants present instructions. Mark up the steps that appear on the page, in the order they appear, with clear names and text.
04
Organization
A single, consistent Organization entity (with name, logo, URL, and sameAs links to your verified profiles) is what lets engines connect every page back to one trustworthy source. Consistency is the point: the same @id and details across the site build the entity that AI answers attribute to.
05
BreadcrumbList
Breadcrumb markup gives the engine your site structure: where this page sits and how it relates to the rest. It helps both search and answer engines understand topical context, and it is cheap to add. Match the breadcrumb to the visible navigation path.
At a glance
- 5
- Schema types do most of the work: Article, FAQPage, HowTo, Organization, BreadcrumbList.
- 1
- One consistent Organization entity across the site is what AI answers attribute to. Keep it identical everywhere.
- 0
- Markup that does not match the visible page earns zero benefit and risks being ignored. Never fake it.
Implementation checklist
What to do, in order, on a real site.
✓
Lead each key page with a direct answer to the question it targets, near the top, in plain language.
✓
Add Article schema to guides and posts with author, datePublished, and an honest dateModified.
✓
Add FAQPage markup only where the questions and answers are visible on the page.
✓
Add HowTo markup to genuine step-by-step content, matching the on-page steps.
✓
Define one Organization entity with logo, URL, and sameAs, and reuse the same @id everywhere.
✓
Add BreadcrumbList that mirrors the visible navigation path.
✓
Validate every page with a schema testing tool and fix errors before you ship.
✓
Re-check after any redesign or CMS change, because markup breaks silently.
Common questions
What teams ask about schema and AI answers.
Does structured data directly get me cited by AI Overviews or ChatGPT?
Not directly. Schema does not buy a citation and is not a ranking factor on its own. What it does is make your content machine-readable: it labels the question, the answer, the author, and the organisation so an answer engine can extract and attribute a fact with confidence. Citations follow from clear, accurate, well-structured content that answers the question; schema reinforces that, it does not replace it.
Which schema type should I add first?
Article and Organization. Article tells engines who wrote the page and when it was reviewed; Organization ties every page back to one consistent, trustworthy entity. After those, add FAQPage and HowTo where the page genuinely contains questions or steps, and BreadcrumbList for structure. Resist the urge to add exotic types before these five are correct and validated.
Can I add FAQ schema to any page to get more visibility?
No. Mark up only questions and answers that are actually visible on the page. FAQPage markup on hidden or invented content violates the guidelines and can get the markup ignored or the page penalised. The reliable approach is to write a genuine FAQ section that helps the reader, then mark it up. If the content is not on the page, do not mark it up.
How is this different from normal SEO?
It builds on it. AEO and GEO are about being the source an answer engine quotes, not just a blue link. The foundations are the same as good SEO: a direct answer, clear structure, real authorship, and a trustworthy entity. The difference is emphasis: answer engines reward extractable, self-contained answers more heavily, and schema makes those easy to lift. See our AEO, GEO and SEO guide for the content side.
How do I measure whether my schema is helping?
Validate first: every targeted page should pass a schema testing tool with no errors. Then track presence in AI answers and featured snippets for your target questions, and watch referral patterns from AI tools where your analytics can see them. Citations are harder to measure than rankings, so treat improvements in snippet capture and direct-answer presence as the leading indicators.
Does schema slow my page down?
No, in practice. JSON-LD is a small block of text in the page head or body and has negligible performance cost. The thing to watch is not the schema itself but keeping it accurate as the page changes, because markup that drifts from the content is worse than none. Validate after every redesign or CMS change.
How we approach it
Clear answers first, then accurate markup, then validation.
We start with the page, not the schema. If the page does not answer the question directly and near the top, no markup will rescue it. Once the content is clear, we add the five core schema types, keep one consistent Organization entity across the site, and validate every targeted page. Markup that matches the visible content and passes validation is the only kind that earns a benefit.
Then we keep it honest over time, because schema breaks silently after a redesign or CMS change. See how we approach AEO and GEO for B2B teams, and the AEO, GEO and SEO guide for the content work that makes the markup worth having.
Concrete solution
Bring the operational risk.You get a clear diagnosis and a concrete next step.
We are the right fit if you want a team that pushes back when it matters. See outcomes and metrics →
Reviewing first?
Company evidenceon the site.
Engagements with commercial outcomes on Work. Team bios and operating model on About. Nothing to download. Review it before you commit to a call. Open to review. Commit when ready.