What Is Schema Markup? A Practical Guide

What structured data actually does

A normal web page tells a browser how to display text. It does not tell a machine that “4.6” is a rating, that “45 minutes” is a cooking time, or that “$29” is a price. To software, those are just characters on a page. Structured data closes that gap. Using an agreed vocabulary, you label parts of the page so search engines can interpret them precisely rather than guessing from context.

That shared vocabulary is schema.org, a collaborative project supported by Google, Microsoft, Yahoo and Yandex. When people say “schema markup” they usually mean adding schema.org types to a page. It is a core part of modern technical SEO, sitting alongside crawling, indexing and speed — the difference being that schema is about meaning rather than access.

JSON-LD, microdata and RDFa

There are three ways to write structured data. JSON-LD is a self-contained block of code, usually placed in the page head or body; microdata and RDFa weave attributes through your visible HTML. Google recommends JSON-LD because it is cleaner to add and maintain — your markup lives in one place instead of being tangled into every element, which means you can update it without touching your page templates.

The types that matter most

Schema.org defines hundreds of types, but a handful cover most real-world needs. Choose based on what the page actually is, not on which feature looks appealing.

Note that Google periodically changes which markup earns a visible feature — FAQ and How-to rich results, for example, have been narrowed over time so they no longer appear as widely as they once did. Always confirm current eligibility in the Search Central structured data documentation rather than assuming a feature still appears the way an older article describes.

Rich results are eligibility, not a promise

This is the single most misunderstood point about schema. Valid markup makes a page eligible for a rich result; it does not force one to appear. Google chooses whether to show enhanced results based on relevance, quality and its own current feature set, and it can remove or redesign any feature without notice. So markup is worth doing — a richer, more informative listing can lift click-through, which is a real benefit — but treat any specific rich result as a bonus you can lose, not a fixed asset you own.

How schema helps beyond rich results

Even where it earns no visible feature, structured data has quieter value. It helps search engines understand entities — the people, products, organisations and places on your pages — and how they relate. As search shifts toward answering questions directly and surfacing sources in AI-generated summaries, being clearly and accurately described in machine-readable terms is a sensible investment. It will not manufacture authority you do not have, but it removes ambiguity about what your content is and who you are, which is exactly the kind of clarity that helps a search engine cite you confidently. This ties into how the modern SERP assembles answers from structured, well-understood sources.

What JSON-LD looks like in practice

You do not need to memorise the syntax, but seeing the shape helps. A JSON-LD block names a @context (schema.org), a @type (say, Article), and then a set of properties describing the page — headline, author, date published, publisher, image. Each property maps to something a reader can already see. The markup sits in a script tag in the HTML and is invisible to visitors; it exists purely so machines can read the same facts your human readers do, without having to infer them from layout.

On more complex pages you can combine types. A single article page might carry Article markup, BreadcrumbList markup for its position in the hierarchy, and Organization markup identifying the publisher. Rather than scattering separate blocks, many sites nest these together in one graph so the relationships between entities — this article, by this author, published by this organisation — are explicit. Your plugin usually handles this; the thing to verify is that the pieces describe the real page and do not contradict each other.

How to add and test schema

1. Pick the right type. Match the page: a product page gets Product, an article gets Article. Do not add Recipe markup to a page that is not a recipe.
2. Generate the JSON-LD. Use your CMS or plugin, or write it by hand following schema.org and Google’s documentation for the specific type.
3. Mark up only visible content. Every value in the markup should correspond to something a user can actually see on the page.
4. Validate. Run the URL through Google’s Rich Results Test and the schema.org validator to catch errors and warnings before you rely on it.
5. Monitor. Watch the Enhancements and Rich Results reports in Search Console for errors after deployment, especially after a site change.

The honesty rules Google enforces

Google’s structured data guidelines are strict about one thing: markup must describe content that is genuinely on the page and visible to users. Marking up prices, reviews or FAQs that a visitor cannot see — or inventing review scores to earn star ratings — violates the guidelines and can trigger a manual action that strips your rich results entirely. This mirrors SerpInsight’s wider stance: don’t fake signals to manipulate search. The same principle runs through how we assess link quality and everything in the on-page SEO service — earn the feature honestly or skip it, because the downside of getting caught outweighs a few stars in the results.

Common schema mistakes

• Marking up invisible content. Every value must correspond to something on the page; do not describe reviews, prices or FAQs a visitor cannot see.
• Using the wrong type. Article markup on a category page, or Product markup on a blog post, confuses rather than helps.
• Self-serving review markup. Adding aggregate ratings you assigned to your own business is against Google’s guidelines and a common cause of lost rich results.
• Set and forget. A redesign or plugin update can silently break markup; the Search Console enhancement reports exist so you catch this.
• Chasing retired features. Some rich results no longer appear widely, so markup for them may validate but never show. Check current eligibility first.

Where schema fits in your strategy

Structured data is a finishing touch, not a foundation. Get crawling, indexing and content right first; schema then helps search engines interpret good pages and can improve how they appear. If you are auditing a site, treat schema as one line item among many — our SEO audit guide shows where it fits in the order of priorities. For the broader plan that ties technical work to content and authority, see the SEO strategy guide.

The bottom line

Schema markup is a translator between your content and search engines. It won’t rescue thin pages or replace real authority, and it won’t hand you rankings. What it can do — done accurately and matched to visible content — is help search engines understand your pages and, sometimes, present them more attractively in the results. Think of it as reducing ambiguity rather than gaining an advantage: you are making sure machines read your page the way a person would, no more and no less, which is exactly why accuracy matters more than volume of markup. That is a worthwhile edge for modest effort, as long as you keep it honest and matched to what is really on the page.