Microdata

Microdata is an HTML markup format used to add machine-readable information directly to existing webpage content. It adds special attributes to ordinary HTML elements so search engines and other systems can better identify what the content represents, such as a person, organization, product, event, recipe, or place.

A visitor can usually understand from context that a particular name refers to a business or that a number represents a product price. A search engine, however, can benefit from more explicit information. Microdata provides that additional context by labeling the meaning and relationships of information already present on the page.

For SEO, Microdata can be used to implement structured data that helps search engines understand page content. It can make eligible pages available for certain enhanced search-result features. Google currently supports Microdata, JSON-LD, and RDFa for structured data and generally recommends JSON-LD because it is easier to implement and maintain.

Structured Data, Microdata, and Schema.org

Structured data, Schema.org, and Microdata are closely related, but they are not the same thing.

Structured data is the broader concept of organizing information into clearly defined fields and relationships so machines can interpret it more easily. A paragraph describing a restaurant’s name, address, opening hours, and price range contains useful information, but those facts are presented primarily for human readers. Structured data can explicitly identify each fact as a separate property.

Schema.org provides a shared vocabulary of types and properties that can be used to describe entities and their characteristics. Examples include Person, Organization, Product, Recipe, and Event, along with properties such as name, address, price, and startDate.

Microdata is one of the markup formats that can apply this vocabulary directly within HTML.

A simple way to remember the relationship is:

• Goal: Structured Data (The organized machine-readable information)
• Vocabulary: Schema.org (The vocabulary of types and properties)
• Markup Format: Microdata, JSON-LD, or RDFa (Formats used to express structured data)

How Microdata Works: The Core Attributes

Microdata works by adding special attributes to normal HTML elements without changing how the visible content ordinarily appears to visitors.

itemscope

The itemscope attribute marks the beginning of an item. It tells a machine that the content contained within that HTML element describes one particular object or entity.

For example, a block of HTML could represent one person, product, business, or event.

itemtype

The itemtype attribute identifies what type of item is being described. When specified, itemtype uses one or more absolute URLs identifying the item type, such as https://schema.org/Person.

For example:

itemtype="https://schema.org/Person"

Using only https://schema.org would not identify a specific type. The HTML standard requires itemtype values to identify the relevant item type using an absolute URL. The technical behavior of these attributes is defined in the HTML Microdata specification.

itemprop

The itemprop attribute identifies a specific property belonging to the item. Depending on the type of item, examples might include name, telephone, address, author, price, and startDate.

Microdata also supports attributes such as itemid and itemref for more advanced implementations, but itemscope, itemtype, and itemprop are the core attributes most beginners are likely to encounter.

<div itemscope
     itemtype="https://schema.org/Dentist">
  <h2 itemprop="name">
    Example Dental
  </h2>

  <p itemprop="description">
    Dental clinic in Buffalo, New York
  </p>

  <p>
    Address:
    <span itemprop="streetAddress">
      210 Elmwood Ave
    </span>,
    <span itemprop="addressLocality">
      Buffalo
    </span>,
    <span itemprop="addressRegion">
      NY
    </span>
  </p>

  <p>
    Phone:
    <span itemprop="telephone">
      (716) 555-0102
    </span>
  </p>

  <a itemprop="url"
     href="https://exampledental.com/locations/new-york/buffalo/">
    Visit website
  </a>
</div>

Example of Microdata

Consider a simple business listing written in ordinary HTML:

<div>
  <h2>Riverside Café</h2>
  <p>Phone: 555-0123</p>
</div>

A visitor can easily understand that “Riverside Café” is a business name and that the number is a telephone number. The HTML itself, however, does not explicitly label those meanings.

The same visible content can be enhanced with Microdata:

<div itemscope itemtype="https://schema.org/LocalBusiness">
  <h2 itemprop="name">Riverside Café</h2>
  <p>Phone: <span itemprop="telephone">555-0123</span></p>
</div>

The visible page does not need to look different. The additional attributes identify the overall item as a LocalBusiness, the business name as its name, and the phone number as its telephone property.

This is the central idea behind Microdata: machine-readable meaning is added to content that already exists in the page’s HTML.

Microdata vs. JSON-LD vs. RDFa

Microdata is not the only way to add structured data. Google supports three major formats for its structured-data features.

Microdata is useful when structured information needs to be attached directly to visible HTML elements. Its main drawback is that large implementations can become harder to maintain because the structured-data attributes are distributed throughout the page markup.

JSON-LD places structured data in a separate script block, which can appear in the <head> or <body>. Google generally recommends this format because it is easier to organize and maintain without modifying many visible HTML elements.

RDFa also extends HTML with machine-readable attributes designed to support linked data and relationships between entities. It remains a supported structured-data format, although Microdata and JSON-LD are often more familiar in everyday SEO implementations.

Microdata allows nested groups of name-value pairs to be added to documents. It remains a supported way to provide structured data when implemented correctly.

Why Microdata Matters for SEO

Search results have evolved far beyond simple blue links. Depending on the query and content type, search engines may display ratings, images, prices, event details, product availability, carousels, and other enhanced features.

Structured data gives search engines explicit clues about the meaning of page content and can make eligible pages available for certain rich-result experiences. Google documents supported markup for features such as products, recipes, events, organizations, and local businesses in its structured data gallery.

For example, supported product structured data can provide information such as product price, availability, ratings, and review information.

Event markup can provide details such as event dates and locations, while recipe markup can communicate cooking times, ratings, and other recipe information.

Structured data by itself is not a generic ranking factor. Structured data can help Google understand content and determine eligibility for certain search appearances, but valid markup does not guarantee that a rich result will be shown.

Rich results can make listings more informative or visually distinctive and may influence user engagement. However, their effect on click-through rate varies by query, feature, website, and audience, so a universal CTR increase should not be assumed.

Microdata and Advanced AI Systems

Structured data can provide machine-readable context that may be useful to systems capable of processing it, but there is no established evidence that Microdata specifically improves visibility in ChatGPT, Claude, or voice-search results.

Google also states that no special Schema.org markup is required to appear in AI Overviews or AI Mode beyond following normal Search requirements. Structured data should therefore be implemented for accurate machine-readable meaning and supported search features rather than treated as a guaranteed AI-visibility technique.

Adding and Testing Microdata

Microdata can be written manually by adding attributes such as itemscope, itemtype, and itemprop to HTML. Manual implementation therefore requires some familiarity with HTML.

Coding knowledge is not always necessary, however. Content management systems, ecommerce platforms, themes, plugins, and SEO tools can generate structured data automatically. Many modern tools generate JSON-LD rather than Microdata because the separate format is easier to manage.

After implementation, structured data should be tested before publication.

Google’s Rich Results Test checks whether markup is eligible for structured-data features currently supported by Google. The Schema.org Validator can be used for broader validation of Schema.org markup. After deployment, Google Search Console can also be used to monitor structured-data problems through supported rich-result reports and the Unparsable Structured Data report.

Passing a validation test does not guarantee that a rich result will appear. Google considers additional factors and requires structured data to follow its quality guidelines, including accurately representing the content visible on the page.

Frequently Asked Questions

Can multiple structured data formats such as Microdata and JSON-LD be used together?

Yes. Different supported structured-data formats can exist on the same page, provided they describe the content accurately and do not contradict one another. Unnecessarily duplicating the same information in several formats can, however, make maintenance more difficult.

Does adding Microdata directly improve keyword rankings?

No. Microdata is not a generic Google ranking factor. It can help search engines understand page content and make eligible pages available for certain enhanced search features, but adding the markup alone does not guarantee higher rankings.

What happens if Microdata contains inaccurate information?

Search engines may ignore inaccurate markup or decline to show associated rich results. Misleading or manipulative structured data can also violate Google’s structured-data policies and may result in a structured-data manual action.

Why has JSON-LD become more popular than Microdata for SEO?

JSON-LD keeps structured data separate from the visible HTML, making it easier to add, modify, and maintain without inserting attributes throughout page markup. Google also generally recommends JSON-LD for structured-data implementations.

Is coding knowledge required to add Microdata?

Not always. Adding Microdata manually requires editing HTML, but CMS plugins, themes, and other tools can generate structured data automatically without requiring site owners to write the markup themselves.

Does Microdata help with voice search optimization?

Microdata can provide explicit machine-readable information about page content, but there is no general guarantee that it improves voice-search visibility. It should be used primarily to describe content accurately and support structured-data features rather than as a standalone voice-search optimization technique.