What Schema Markup Is (and Isn't)
Schema markup is a short note you leave for machines, describing what your page is about in a format they can't misread. No jargon, no magic, just labels.
The one-sentence version
Schema markup is a block of structured labels that tells machines exactly what the things on your page are. Your page says "Double Atari, Minneapolis, SEO consulting." A person reads that and understands it. A machine sees three strings of text and has to guess.
Schema removes the guesswork. It says: this is an Organization, its name is Double Atari, its address is in Minneapolis, and it offers this Service.
Where the word "schema" comes from
The labels come from Schema.org, a shared vocabulary that Google, Microsoft, Yahoo, and Yandex started in 2011. It's a big dictionary of types (things like Person, Event, Recipe) and properties (details about those things, like name, startDate, cookTime).
You don't need to memorize the dictionary. Most websites use the same dozen or so types, and this course covers them one at a time.
Why it's worth your time
Search results
Google uses schema to understand pages and, for some types, to show rich results: star ratings, event dates, recipe cook times, breadcrumbs.
AI answers
AI search tools read pages to build answers. Clear, consistent structured data makes your facts (who you are, where, what you offer) easier to pull out correctly.
Your entity
Schema connects your site, your business, and your people into one consistent picture across pages. Search engines call this an entity.
Your own clarity
Writing schema forces you to decide what a page is actually about. That's a useful exercise even before a robot reads it.
What schema can't do
This part matters, especially if you build sites for clients.
- It doesn't guarantee rich results. Valid markup makes a page eligible. Google decides whether to show anything.
- It isn't a ranking shortcut. It helps machines understand good content. It doesn't make thin content good.
- It can't describe things that aren't on the page. If the schema says five-star reviews and the page shows none, that's a problem, not a trick.
The golden ruleSchema should describe what a visitor can actually see on the page. If you wouldn't say it in the visible content, don't say it in the markup.
Three formats, one winner
There are three ways to write schema: Microdata and RDFa (attributes sprinkled through your HTML) and JSON-LD (one tidy block of code). Google recommends JSON-LD, and so do we. It lives in a single <script> tag, it doesn't touch your design, and you can read it top to bottom.
Here's a complete, valid example. Don't worry about the details yet. Lesson 2 takes it apart line by line.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Double Atari",
"url": "https://www.double-atari.com/",
"description": "SEO, GEO/AEO, and CMS consulting based in Minneapolis."
}
</script>
That's it. Six lines of labels, wrapped in a script tag. Read it out loud and it almost makes sense already: the type is Organization, the name is Double Atari, the URL is…
Check yourself
- I can explain schema markup to a client in one sentence.
- I know it makes pages eligible for rich results, not guaranteed.
- I know the markup has to match what's visible on the page.
- I know we'll be writing JSON-LD.
The original write-up for marketers: Schema Markup, Explained for Marketers.