What Is Schema Markup?

How Schema Markup Works

Schema markup solves a problem plain HTML can’t: HTML tags describe how content should look, but not what it means. Schema.org, in its own words, is “a collection of shared vocabularies webmasters can use to mark up their pages in ways that can be understood by the major search engines.” That shared vocabulary is the whole point. Because Google, Microsoft, Yahoo, and Yandex agreed on it together in 2011, a Product or Recipe you mark up once is interpreted the same way across their engines — you don’t tag your pages differently for each one.

The vocabulary is organized as a hierarchy of types and properties. A type is the kind of thing an entity is — Article, Product, Event, LocalBusiness, FAQPage. Each type has properties that describe it: a Product has name, image, offers, aggregateRating; an Event has startDate, location, performer. Marking up a page means choosing the type that matches its primary entity and mapping each visible piece of content to the right property.

That mapping is what turns text into meaning. Wrapping “$29.99” in a price property tells the engine this string is a price in a specific currency, not a random number. Once the engine can classify the page’s entities with confidence, it can qualify the page for a rich result — the enhanced listing with stars, images, or prices that stands out in the results.

Format vs Vocabulary

A recurring source of confusion is that schema markup involves two separable choices, and people collapse them:

• The vocabulary — schema.org. This decides which words you use: the type names and property names. This is the “schema” in schema markup.
• The format — JSON-LD, Microdata, or RDFa. This decides how those words are physically placed on the page.

You always pick both. Modern SEO almost universally pairs the schema.org vocabulary with the JSON-LD format, because JSON-LD keeps the markup in a single script block instead of tangling it through your visible HTML. Google recommends exactly this combination for most sites, while noting that the same schema.org types expressed in Microdata or RDFa are equally valid.

Example of Schema Markup

The most authoritative worked example is schema.org’s own founding case. The project’s getting-started documentation gives the canonical illustration of why a shared vocabulary is needed: the word “Avatar” on a page could refer to the James Cameron film or to a user’s profile picture, and standard HTML gives a search engine no way to tell them apart. Schema markup resolves the ambiguity — tagging the entity as a Movie with a director property named “James Cameron” tells the engine unmistakably which “Avatar” the page is about.

This example is instructive because it shows schema markup doing its core job before any rich result enters the picture: disambiguating entities. The engine’s first task is comprehension — knowing that a page about “Avatar” the movie is a different thing from a page about avatars the profile images. Only once that comprehension is in place can the engine confidently promote the page to a movie rich result with a poster, cast, and ratings.

The mechanism is fully documented and testable, which is what keeps it out of guesswork. The schema.org site publishes every type and its valid properties, and Google’s Rich Results Test reports exactly which required properties a given markup is missing. The lesson generalizes directly: schema markup is a precise description written in an agreed language. Choose the type that genuinely names the page’s main entity, fill the properties that correspond to what’s actually visible, and the engine gains the clarity it needs to both understand and showcase the page. Describe the page truthfully, and schema markup does the rest.

Schema Markup vs Structured Data

In practice SEOs use the two phrases interchangeably, and that’s usually fine — when someone says “add structured data” for search, they mean schema.org markup. The precise relationship is that structured data is the wider category, and schema markup is the specific, dominant vocabulary used inside it.

Frequently Asked Questions

The Bottom Line

Schema markup is the vocabulary layer of structured data — the agreed-upon set of types and properties that lets you describe a product, an article, or an event in words every major search engine reads the same way. It won’t lift a page up the rankings on its own, but it removes ambiguity about what the page is about and opens the door to a richer listing. Mark up only what’s truly on the page, validate it, and let the description be accurate rather than aspirational.