---
title: "Schema markup for AEO: which types matter"
description: "Which schema.org types help answer engine optimization, what Google says about AI and structured data, and the markup aeo.so uses on every page."
url: https://aeo.so/guides/schema-markup-for-aeo
author: "Paul Andre de Vera"
updated: 2026-11-15
---

# Schema markup for AEO: which types matter

By Paul Andre de Vera. Updated 2026-11-15.

Schema markup helps AEO by telling search engines and AI tools exactly what a page is, who wrote it and how it fits the site. No special AI schema exists; Google says standard markup that matches the visible page is enough. The types that matter most are Organization, Person, Article, BreadcrumbList and FAQPage.

## Does schema markup help with AI search?

Yes, as a support, not a shortcut. Structured data removes guesswork: it states the page type, the author, the publisher, the dates and how the page sits in the site. That helps search engines index the page correctly, which AI answers then draw on.

Markup is one of several ways machines read facts. In Google's Knowledge Vault research, schema.org annotations were one of four fact extractors, beside text, page structure and tables. Facts found by more than one of them earned higher confidence, which is why markup should repeat what the page already says.

Google's 2026 guide is clear on the limits. There is no special schema for AI features, and markup must match what people see on the page. Markup cannot make a weak page quotable.

## Which schema types matter most for AEO?

| Type | What it states | Where aeo.so uses it |
|---|---|---|
| **Organization** | Who publishes the site | Every page, in a site-wide graph |
| **Person** | Who wrote the content, with links to their profiles | Every page; the [author page](https://aeo.so/about/paul-andre-de-vera) |
| **WebSite** | The site itself | Every page |
| **Article** | Headline, author, dates, section | Every guide and tactic |
| **BreadcrumbList** | Where the page sits in the site | Every page except the homepage |
| **FAQPage** | Questions and answers on the page | Guides with a FAQ section |
| **HowTo** | Steps to complete a task | The [how to do AEO](https://aeo.so/learn) guide |
| **DefinedTermSet** | A set of defined terms | The [AEO glossary](https://aeo.so/glossary) |
| **CollectionPage + ItemList** | A list of items, in order | Checklist areas and the guides index |
| **SoftwareApplication** | A tool, its price and platform | The [tools page](https://aeo.so/tools) |
| **Dataset** | A published dataset | Original research |

Product, LocalBusiness, Event, Recipe and Review apply when your content is that kind of thing.

## What does good markup look like?

Good markup is complete, accurate and linked together. A shortened version of the Article markup on this page:

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema markup for AEO: which types matter",
  "author": {
    "@type": "Person",
    "name": "Paul Andre de Vera",
    "url": "https://aeo.so/about/paul-andre-de-vera"
  },
  "publisher": { "@id": "https://aeo.so/#organization" },
  "datePublished": "2026-11-15",
  "dateModified": "2026-11-15",
  "mainEntityOfPage": "https://aeo.so/guides/schema-markup-for-aeo"
}
```

The `@id` values tie each page's Article to one Organization and one Person, defined once. That gives search engines one consistent record of who publishes what.

## What are the common schema mistakes?

- **Markup that does not match the page**, such as FAQ answers that are not visible. Google treats this as a policy issue.
- **Missing author or dates**, which weakens trust signals.
- **Several conflicting Organization entries** across templates.
- **Marking up everything as FAQ** to chase rich results that no longer show.
- **Never testing** after a site change.

## How do you add schema markup?

Generate it from the same data that renders the page, not by hand. Most CMSs and SEO plugins output Organization, Article and BreadcrumbList; add FAQPage where you have a visible FAQ. Then test each template with Google's Rich Results Test, and recheck after redesigns. The checklist area [Structured Data & Schema](https://aeo.so/categories/structured-data) lists the related tactics.

## Frequently asked questions

### Does FAQ schema still help in 2026?

FAQ schema no longer earns a rich result for most sites; Google limited FAQ rich results to well-known government and health sites in 2023. The markup still states your questions and answers in a form machines read reliably, which supports AI retrieval. Use it where the page has a real FAQ, and nowhere else.

### Which format should I use for schema markup?

Use JSON-LD. Google recommends it, it sits in a script tag separate from your HTML, and it is easy to generate from your content. aeo.so builds its JSON-LD from the same data that renders each page, which keeps the markup and the visible text in step.

### How do I test my schema markup?

Use Google's Rich Results Test to check the types Google supports, and the Schema Markup Validator at validator.schema.org for everything else. Test one page of each template after every change. Fix errors first; warnings for optional properties can wait until later.

## Sources

- [Google Search Central: Introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)
- [Google Search Central: Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
- [Schema.org](https://schema.org/)
- [Dong et al., Knowledge Vault: A Web-Scale Approach to Probabilistic Knowledge Fusion (KDD 2014)](https://dl.acm.org/doi/epdf/10.1145/2623330.2623623)
