Microdata are a set of HTML attributes defined in the HTML specifications for embedding structured metadata directly into a web page’s markup. Unlike other annotation techniques, they don’t require separate files or additional languages: information is attached to existing HTML elements through attributes such as itemscope, itemtype and itemprop. This approach lets search engines unambiguously understand the meaning of content, for example distinguishing a product’s name from its price or an article’s publication date.
In SEO, microdata are one of the most widely used syntaxes for implementing structured data, alongside JSON-LD and RDFa; Google recommends JSON-LD but also reads microdata. Adopting them allows search engines to generate enriched results, known as rich results, which show additional information directly on the results page. Understanding how they work is therefore essential for anyone who wants to improve a site’s organic visibility and the semantic clarity of its pages.
What sets microdata apart
Microdata are an HTML language specification that lets you label portions of content with property-value pairs. The mechanism relies on three main attributes: itemscope defines an element’s scope, itemtype specifies the reference vocabulary via a URL, and itemprop assigns a name to the property. In this way, a block of HTML code can describe entities such as people, events, products, reviews or recipes.
The most widespread vocabulary is Schema.org, created through collaboration among major search engines. It provides a shared set of types and properties that search engines recognize and interpret. Microdata, therefore, are not a language in themselves but a way to apply a standard vocabulary to a page’s content.
How the main attributes work
To understand microdata, you need to become familiar with their constituent attributes. They nest within the markup and create a hierarchy of information that crawlers can read and interpret without ambiguity.
Itemscope and itemtype
The itemscope attribute indicates that the HTML element it’s applied to encloses a set of properties related to a single entity. The itemtype attribute, which always accompanies itemscope, specifies the type of entity being described via a vocabulary URL. For example, an element with an itemtype equal to a product indicates that the inner properties describe a product.
Itemprop and itemid
The itemprop attribute assigns a name to each property within an element that has itemscope. It can be applied to elements such as headings, images, links or paragraphs. The itemid attribute, less common, provides a globally unique identifier for the described entity, useful when the same entity appears on multiple pages.
Microdata, JSON-LD and RDFa compared
There are several syntaxes for implementing structured data. The choice depends on the site’s technical requirements, ease of maintenance and search engine preferences. The following table compares the three main ones.
| Syntax | Location in code | Ease of maintenance | Google support |
|---|---|---|---|
| Microdata | Embedded in HTML markup | Medium | Supported |
| JSON-LD | Separate block in the page | High | Supported; recommended format |
| RDFa | Embedded in HTML markup | Low | Supported |
| Microformats | CSS classes in markup | Medium | Declining |
Why microdata help visibility
Correct use of microdata can make a page eligible for rich results, when the content type is supported by Google, and helps search engines understand the context of the content. However, it doesn’t guarantee rich results or change ranking.
Another advantage concerns semantic consistency: annotating information in a structured way also helps other automated systems, such as voice assistants and data aggregators, to extract and reuse content correctly. This expands visibility opportunities beyond traditional search.
Rich results and visibility
Rich results are enriched presentations that include elements such as star ratings, prices, preparation times or availability. Not all content types generate them, and Google has reduced them over time (for example, FAQ and HowTo in 2023): with correct microdata a page can become eligible, but there’s no guarantee.
How to implement microdata step by step
Implementation requires attention to markup structure and consistency with the chosen vocabulary. The following steps outline an orderly, verifiable workflow.
- Choose the entity type to describe by consulting the Schema.org vocabulary.
- Locate the HTML element that encloses the entity and apply itemscope and itemtype.
- Assign the itemprop attribute with the correct name to each relevant property.
- Check that property values match the page’s visible content.
- Check the hierarchy of nested elements to avoid ambiguity.
- Validate the code with the Schema.org Validator and Google’s Rich Results Test.
- Monitor error reports in Search Console.
- Update annotations when the page content changes.
Frequently asked questions about microdata
Are microdata required for ranking?
No, microdata are not a mandatory requirement for ranking. However, they can improve how results are presented and how search engines understand the content, offering indirect visibility benefits.
What’s the difference between microdata and structured data?
Structured data is a general concept that refers to any format for describing content in a machine-readable way. Microdata are one of the specific syntaxes through which structured data can be implemented in HTML.
Can I use microdata together with JSON-LD?
It’s technically possible, but to avoid conflicts and duplication it’s better to choose a single syntax for the same information. Google recommends JSON-LD.
Do microdata work on all search engines?
Major search engines recognize microdata based on the Schema.org vocabulary. The level of support can vary depending on the content type and each engine’s specific guidelines.
How do I check if my microdata are correct?
You use validation tools provided by search engines, which analyze the markup and flag errors or missing properties. It’s good practice to repeat the check after every significant change.
Do microdata directly influence ranking?
There’s no direct, guaranteed correlation between microdata and ranking. Their main impact concerns the quality of presentation in search results and the semantic clarity of pages.
From glossary to projectDo search engines understand what your site is about?Implementing structured data and Schema markup helps search engines and AI systems interpret content.Discover structured data
Related entries:
Schema.org Rich snippets Schema markup Product structured data