SEO

Microdata

Also called HTML microdata

A structured data format that labels information using attributes added directly to the visible HTML of a page.

Quick facts: Microdata

Category
SEO
Also called
HTML microdata
Level
Intermediate
Affects
Rich result eligibility, how crawlers read a template, developer maintenance
Where to see it
Rich Results Test, Schema Markup Validator, browser view-source, Screaming Frog
In this article4
  1. How microdata works
  2. Why microdata matters
  3. Where microdata goes wrong
  4. What to do about it

How microdata works

Search engines accept structured data in three writing formats, and microdata is the one that lives inside the page’s own HTML. Instead of adding a separate block of code, you attach attributes to the tags that are already there. itemscope opens an item, itemtype names the type it is — a product, a recipe, a business — using a vocabulary address from the Schema.org vocabulary, and itemprop labels each individual detail inside it.

Because the labels sit on the elements a visitor can see, the marked-up value and the displayed value are the same piece of text. A price wrapped in an itemprop is the price on the screen. There is no second copy to keep in step.

Why microdata matters

Mostly because it is already on the web. Older themes, ecommerce templates and content management systems shipped with microdata built into their markup, so if you inherit a site of any age you will meet it in an audit long before you decide whether you want it. Knowing how to read it tells you what a template is claiming about the page.

It also has one genuine advantage over a separate code block: markup and content cannot drift apart, because they are the same thing. A mismatch between what the markup says and what the page shows is one of the more reliable ways to attract a manual action, and microdata makes that mismatch harder to create by accident.

Where microdata goes wrong

Nesting is the usual failure. An item ends where its element closes, so a designer who moves a closing tag, splits a template into partials or wraps a section in a new container can orphan half the properties without touching a word of the markup. Nothing looks broken on screen and nothing reports an error until you test the rendered page.

The second problem is duplication. A site that adds a JSON-LD block on top of legacy microdata ends up describing the same thing twice, often with different values, and leaves the search engine to guess which one is true. The third is marking up content that is hidden from visitors, which the guidelines treat as markup that does not reflect the page.

What to do about it

Test the rendered page rather than the template, using the Rich Results Test or the Schema Markup Validator, and retest after every redesign — that is when microdata quietly breaks. If markup already exists, validates and matches the page, leave it alone; rewriting it in another format buys no ranking advantage on its own.

When you are building something new, or the template is being rebuilt anyway, write it as JSON-LD instead. It sits in one place, survives design changes and is far easier for a developer to maintain. If you are migrating, replace the microdata rather than layering over it, and treat the change as part of the technical SEO work on the site rather than a content job.

Do and do not

Do

  • Test the rendered page, not the template file
  • Revalidate structured data after every design change
  • Keep marked-up values identical to what visitors see

Do not

  • Mark up content that is hidden from visitors
  • Describe the same entity in two formats at once
  • Choose microdata for a brand new build

Questions people ask about this

Is microdata still supported by search engines?

Yes. Google reads microdata, JSON-LD and RDFa, and treats valid markup in any of them the same way. JSON-LD is the format it recommends, but that is a maintenance preference rather than a ranking one. Existing microdata that validates and matches the visible page is not a problem and does not need rewriting for its own sake.

Should I convert my microdata to JSON-LD?

Convert it when you are already rebuilding the template, and leave it when you are not. The benefit is maintenance: one block of code that a developer can read, change and test without touching the design. Converting a working, validated set of markup purely to change format costs developer time and gains nothing you can measure.

Can microdata and JSON-LD run on the same page?

They can, and a search engine will read both, but describing the same entity twice invites contradictions. If the microdata says one price and the JSON-LD says another, you have handed the crawler a conflict to resolve. Keep one description per entity per page, and remove the older format rather than stacking a new one on top.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.