Microdata is a WHATWG HTML specification used to nest metadata within existing content on web pages.[1] Search engines, web crawlers, and browsers can extract and process Microdata from a web page and use it to provide a richer browsing experience for users. Search engines benefit greatly from direct access to Microdata because it allows them to understand the information on web pages and provide more relevant results to users.[2][3] Microdata uses a supporting vocabulary to describe an item and name-value pairs to assign values to its properties.[4] Microdata is an attempt to provide a simpler way of annotating HTML elements with machine-readable tags than the similar approaches of using RDFa and microformats.
In 2013, because the W3C HTML Working Group failed to find someone to serve as an editor for the Microdata HTML specification, its development was terminated with a 'Note'.[5][6] However, since that time, two new editors were selected, and five newer versions of the working draft have been published,[7][8][9][10] the most recent being Working Draft 26 April 2018.[10]
Microdata vocabularies do not provide the semantics, or meaning of an Item.[11] Web developers can design a custom vocabulary or use vocabularies available on the web. A collection of commonly used markup vocabularies are provided by Schema.org schemas which include: Person, "Place", Event, Organization, Product, Review, Review-aggregate, Breadcrumb, Offer, Offer-aggregate. The website schema.org was established by search engine operators like Google, Microsoft, Yahoo!, and Yandex, which use microdata markup to improve search results.[12]: 85
For some purposes, an ad-hoc vocabulary is adequate. For others, a vocabulary will need to be designed. Where possible, authors are encouraged to re-use existing vocabularies, as this makes content re-use easier.[1]
In some cases, search engines covering specific regions may provide locally-specific extensions of microdata. For example, Yandex, a major search engine in Russia, supports microformats such as hCard (company contact information), hRecipe (food recipe), hReview (market reviews) and hProduct (product data) and provides its own format for definition of the terms and encyclopedic articles. This extension was made in order to solve transliteration problems between the Cyrillic and Latin alphabets. After the implementation of additional parameters from Schema's vocabulary,[13] indexation of information in Russian-language web-pages became more successful.
itemscope – Creates the Item and indicates that descendants of this element contain information about it.[1]itemtype – A valid URL of a vocabulary that describes the item and its properties' context.itemid – Indicates a unique identifier of the item.itemprop – Indicates that its containing tag holds the value of the specified item property. The property's name and value context are described by the item's vocabulary. Properties values usually consist of string values, but can also use URLs using the a element and its href attribute, the img element and its src attribute, or other elements that link to or embed external resources.[1]itemref – Properties that are not descendants of the element with the itemscope attribute can be associated with the item using this attribute. Provides a list of element IDs (not itemids) with additional properties elsewhere in the document.[1]datetime – Indicates date or duration as specified by ISO 8601 standard.The following HTML5 markup may be found on a typical “About” page containing information about a person:
<section> Hello, my name is John Doe, I am a graduate research assistant at
the University of Dreams.
My friends call me Johnny.
You can visit my homepage at <a href="http://www.example.com/~JohnnyD">www.example.com/~JohnnyD</a>.
I live at 1234 Peach Drive, Warner Robins, Georgia.</section>
Here is the same markup with added Schema.org[14][15][16] Microdata:
<section itemscope itemtype="http://schema.org/Person">
Hello, my name is
<span itemprop="name">John Doe</span>,
I am a
<span itemprop="jobTitle">graduate research assistant</span>
at the
<span itemprop="affiliation">University of Dreams</span>.
My friends call me
<span itemprop="additionalName">Johnny</span>.
You can visit my homepage at
<a href="http://www.example.com/~JohnnyD" itemprop="url">www.example.com/~JohnnyD</a>.
<section itemprop="address" itemscope itemtype="http://schema.org/PostalAddress">
I live at
<span itemprop="streetAddress">1234 Peach Drive</span>,
<span itemprop="addressLocality">Warner Robins</span>,
<span itemprop="addressRegion">Georgia</span>.
</section>
</section>
As the above example shows, Microdata items can be nested. In this case, an item of type http://schema.org/PostalAddress is nested inside an item of type http://schema.org/Person.
The following text shows how Google parses the Microdata from the above example code. Developers can test pages containing Microdata using Google's Rich Snippet Testing Tool.[17]
Item Type: http://schema.org/Person name = John Doe jobTitle = graduate research assistant affiliation = University of Dreams additionalName = Johnny url = http://www.example.com/~JohnnyD address = Item(1) Item 1 Type: http://schema.org/PostalAddress streetAddress = 1234 Peach Drive addressLocality = Warner Robins addressRegion = Georgia
The same machine-readable terms can be used not only in HTML Microdata, but also in other annotations such as RDFaorJSON-LD in the markup, or in an external RDF file in a serialization such as RDF/XML, Notation3, or Turtle.
{{cite AV media}}: |author= has generic name (help)