Schema markup is the structured-data vocabulary that tells Google and AI systems what your content is — not just what it says. These 21 references cover the types that actually earn rich results and feed AI answers: the core entities (Organization, Person, Article), the content and media types (FAQ, Review, Event, Video), the commerce and local types (Product, LocalBusiness), and the foundations — JSON-LD syntax, validation, and what large language models genuinely read. Every reference is practical: required properties, the common mistakes, and whether the type still earns anything in search.
- 21Reference guides
- Jul 17, 2026Last updated
- 5 minAvg. read time
- FreeNo paywall, ever
Featured references
Every schema reference
No references match — try another term or pick a different topic chip.
Schema Markup: The Complete Guide
Schema markup is structured data — a standardized vocabulary from Schema.org that you add to a page so machines understand what its content represents: a product, a person, an FAQ, an organization. It does not change what visitors see; it changes what Google, Bing, and AI systems understand, which is what makes a page eligible for rich results and easier for large language models to parse and cite.
This pillar is the working reference for it. The 21 guides below each take one schema type and go deep — required properties, the mistakes that invalidate it, and whether it still earns anything today. This page gives you the map: what schema is, which format to use, who owns what, and how to tell a valuable type from a dead one.
Quick Navigation
- What Is Schema Markup?
- Why JSON-LD Is the Standard
- The Types That Matter
- Schema and Rich Results
- Schema and AI Search
- Who Should Own Your Schema
- Common Misconceptions
- Frequently Asked Questions
- All 21 References
What Is Schema Markup?
Schema.org is a shared vocabulary — maintained by Google, Microsoft, Yahoo, and Yandex — of “types” (Product, Person, Event) and “properties” (name, price, startDate). You add this vocabulary to a page as machine-readable data, and search engines use it to render richer results and to build their understanding of entities. It is descriptive, not persuasive: schema states facts about the page that are already true, in a form machines can trust.
Two things follow from that. First, schema must match the visible content — marking up a price or rating that is not on the page is a policy violation. Second, schema is an eligibility signal, not a ranking boost: it can make you eligible for a rich result, but it does not directly raise your position, a distinction the structured data guide covers in the wider technical context.
Why JSON-LD Is the Standard
There are three ways to write structured data — JSON-LD, Microdata, and RDFa — and Google explicitly recommends JSON-LD. It lives in a single script block in the page head or body, separate from your HTML, which makes it far easier to add, template, and maintain than the inline attributes Microdata and RDFa scatter through your markup. The full comparison, and how to migrate off inline formats, is in JSON-LD vs Microdata vs RDFa. For everything below, assume JSON-LD.
The Types That Matter
Schema.org lists hundreds of types, but a small set does almost all the real work. The core entities anchor your site and its people: Organization, Person, Article, WebSite, and BreadcrumbList. The content and media types earn or once earned rich results: FAQ, HowTo, Review, Event, VideoObject, and more. The commerce and local types drive listings: Product, LocalBusiness, and SoftwareApplication.
Each reference in this cluster tells you the required properties and — just as importantly — whether the type still earns a visible result, because Google has quietly retired several rich results while leaving the markup valid.
Schema and Rich Results
A rich result is any search listing enhanced beyond a plain blue link — star ratings, product prices, event dates, breadcrumbs. Schema is what makes a page eligible, but eligibility is not a guarantee: Google decides per query whether to show the enhancement. Two rich results were cut back sharply — FAQ is now limited to a narrow set of authoritative sites, and the HowTo result was retired entirely — so a working reference has to tell you not just how to write a type but whether it still pays off. Validate every type before you ship it with the tools in how to test and validate schema markup, and generate common types quickly with our free FAQ schema generator.
Schema and AI Search
As AI Overviews and assistants like ChatGPT and Perplexity reshape search, a fair question is whether schema helps you get cited. The honest answer is nuanced: LLMs read rendered text first, and there is no confirmed “schema ranking factor” for AI answers — but structured data still disambiguates entities, reinforces the facts on the page, and powers the knowledge graphs these systems draw on. Schema for AI Search lays out what the evidence supports and what it does not, and connects to the broader strategy in the GEO & AEO pillar.
Who Should Own Your Schema
On most sites, an SEO plugin or the CMS generates the foundational schema — Organization, WebPage, Article, BreadcrumbList — automatically. That is a feature, not a gap to fill: adding a second copy of Article or Organization markup by hand creates duplicate entities, one of the most common structured-data errors. The rule of thumb: let your platform own the site-wide entities, and add only the page-specific types it does not — FAQ, Product, Event, and the like. Every reference here flags whether a type is usually plugin-owned so you do not double up.
Common Misconceptions
Myth 1: “Schema boosts rankings.” It creates rich-result eligibility and aids understanding; it is not a direct ranking factor.
Myth 2: “More schema is better.” Marking up types you cannot support, or data not visible on the page, risks errors and manual actions. Add only what is true and relevant.
Myth 3: “Valid schema guarantees a rich result.” Validity is necessary but not sufficient — Google chooses whether to display the enhancement, and some results were retired despite valid markup.
Myth 4: “FAQ schema still gets me those dropdowns.” For most sites, no — Google restricted FAQ rich results to authoritative government and health sites. The markup can still help AI and internal understanding.
Myth 5: “Schema must match a hidden keyword strategy.” Schema describes what is genuinely on the page. Mismatched or invisible markup is a violation, not a tactic.
Frequently Asked Questions
Does schema markup improve rankings?
Not directly. Schema makes pages eligible for rich results and helps search engines and AI understand your content, which can improve click-through and visibility — but it is not a ranking factor in the way content quality or links are.
Which schema format should I use?
JSON-LD. Google recommends it, it is the easiest to add and maintain, and it keeps structured data separate from your HTML. Microdata and RDFa still work but are harder to manage — migrate when you can.
Do I need to add schema by hand?
Often not for the basics — most SEO plugins generate Organization, Article, and BreadcrumbList automatically. Add page-specific types (FAQ, Product, Event) yourself, and avoid duplicating what your platform already outputs.
Does schema help with AI search and ChatGPT?
It can help indirectly by disambiguating entities and reinforcing facts, but LLMs read rendered text first and there is no confirmed schema ranking factor for AI answers. Treat it as supporting infrastructure, not a shortcut to citations.
Explore This Cluster: The Complete Schema Reference
The 21 references below cover the core entities, the content and media types, the commerce and local types, and the foundations of structured data. Start with the type you are marking up, or with Schema for AI Search if you are here for citations.
| Reference | What it covers |
|---|---|
| Organization Schema | The entity that anchors your site — required properties, sameAs, logo, and duplicate-entity pitfalls. |
| Person Schema | Author and people entities for E-E-A-T, and how they link to Organization. |
| Article Schema | Headline, author, and dates — what it does and how to avoid duplicating it. |
| WebSite + SearchAction | Naming your site as an entity and declaring its search box. |
| BreadcrumbList Schema | SERP breadcrumbs — the ItemList structure and ordering rules. |
| CollectionPage + ItemList | Describing hubs and category pages as ordered lists. |
| FAQ Schema | The restricted rich result — who still qualifies and why it still helps AI. |
| HowTo Schema | The retired rich result — what to do with the markup now. |
| Review Schema | Star ratings, the self-serve policy, and avoiding manual actions. |
| AggregateRating Schema | The averaged rating and how it nests inside other types. |
| Event Schema | Dates, venues, tickets, and online-event handling. |
| VideoObject Schema | Video results and key moments — required properties and thumbnails. |
| ImageObject Schema | License and creator metadata for image-license badges. |
| Speakable Schema | Voice/TTS markup — beta status and whether it is worth adding. |
| Product Schema | Price, availability, and reviews — required fields and merchant rules. |
| LocalBusiness Schema | Address, hours, geo, and NAP consistency for local pages. |
| SoftwareApplication Schema | Apps and SaaS as entities — category, OS, price, and rating rules. |
| JSON-LD vs Microdata vs RDFa | The three syntaxes compared and why Google recommends JSON-LD. |
| Validate Schema Markup | The Rich Results Test vs the Schema.org validator, and reading errors. |
| Schema for AI Search | What LLMs actually read and whether schema earns citations. |
| Dataset Schema | Making research data discoverable in Dataset Search. |
Schema Markup — Frequently Asked Questions
What is schema markup in simple terms?
It is a standardized vocabulary (from Schema.org) you add to a page so machines understand what the content is — a product, a recipe, an organization. It does not change what visitors see, but it makes pages eligible for enhanced search results and easier for AI to parse.
Is JSON-LD better than Microdata?
For almost everyone, yes. Google recommends JSON-LD, and it keeps structured data in one script block instead of scattering attributes through your HTML, which makes it far easier to add, template, and maintain. Microdata and RDFa remain valid but harder to manage.
Why did my FAQ rich results disappear?
Google restricted FAQ rich results in 2023 to authoritative government and health sites. The markup is still valid and can help AI systems and internal understanding, but most sites no longer see the FAQ dropdowns in search. Full detail here.
Can too much schema hurt me?
Yes, if it is inaccurate. Marking up data that is not visible on the page, or types you cannot legitimately support, risks structured-data errors and even manual actions. Add only schema that reflects what is genuinely on the page.
Does schema help with AI Overviews and ChatGPT?
Indirectly. It disambiguates entities and reinforces facts, and feeds the knowledge graphs these systems use — but LLMs read rendered text first and there is no confirmed schema ranking factor for AI answers. The evidence is here.
Keep exploring
Related pillars: Technical SEO — where structured data fits the wider stack · GEO & AEO — the strategy behind AI citations · Search Console — validating enhancements live.
Put it into practice: FAQ schema generator · schema validator · glossary.
Want an expert to build your schema? Get in touch.
Never miss a breakdown. One email when something genuinely changes in AI search or SEO — plus new guides and free templates. Subscribe to the newsletter →