Schema.org

Schema.org is a reference website that publishes documentation and guidelines for using structured data mark-up on web-pages (in the form of microdata, RDFa or JSON-LD). Its main objective is to standardize HTML tags to be used by webmasters for creating rich results (displayed as visual data or infographic tables on search engine results) about a certain topic of interest.^[2] It is a part of the semantic web project, which aims to make document mark-up codes more readable and meaningful to both humans and machines.

Schema.org

Abbreviation	schema
Year started	2011; 14 years ago (2011)
Latest version	28.0 (2024-09-17)[1]
Organization	Google, Yahoo!, Microsoft, Yandex
Base standards	URI, HTML5, RDF, Microdata, ISO 8601
Related standards	RDFa, Microformat, RDFS, OWL, N-Triples, Turtle, JSON, JSON-LD, CSV
Domain	Semantic Web
License	CC-BY-SA 3.0
Website	schema.org

History

Schema.org is an initiative launched on June 2, 2011, by Bing, Google and Yahoo!^[3][4][5] (operators of the world's largest search engines at that time)^[6] to create and support a common set of schemas for structured data markup on web pages. In November 2011, Yandex (whose search engine is the largest in Russia) joined the initiative.^[7][8] They propose using the schema.org vocabulary along with the Microdata, RDFa, or JSON-LD formats^[9] to mark up website content with metadata about itself. Such markup can be recognized by search engine spiders and other parsers, thus granting access to the meaning of the sites (see Semantic Web). The initiative also describes an extension mechanism for adding additional properties.^[10] In 2012, the GoodRelations ontology was integrated into Schema.org.^[11] Public discussion of the initiative largely takes place on the W3C public vocabularies mailing list.^[12]

Much of the vocabulary on Schema.org was inspired by earlier formats, such as microformats, FOAF, and OpenCyc.^[13] Microformats, with its most dominant representative hCard, continue (as of 2015) to be published widely on the web, where the deployment of Schema.org has strongly increased between 2012 and 2014.^[14] In 2015,^[15] Google began supporting the JSON-LD format, and as of September, 2017 recommended using JSON-LD for structured data whenever possible.^[16][17]

Despite the advantages of using Schema.org, adoption remained limited as of 2016. A survey in 2016 of 300 US-based marketing agencies and B2C advertisers across industries showing only 17% uptake.^[18] As of 2024 over 45 million web domains have used schema markup on their web pages.^[19]

Validators, such as the deprecated^[20] Google Structured Data Testing Tool, or more recent^[21] Google Rich Results Test Tool,^[22] Schema.org Markup Validator,^[23] Yandex Microformat validator,^[24] and Bing Markup Validator^[25] can be used to test the validity of the data marked up with the schemas and Microdata. More recently, Google Search Console (formerly webmaster tools) has provided a report section for unparsable structured data. If any Schema code on a website is incorrect, it will show in this report.^[26] Some schema markups such as Organization and Person are commonly used to influence search results returned by Google's Knowledge Graph.^[27]

Schema Types

Schema vocabulary includes sets of types, which each have related metadata properties that can be illustrated using pre defined enumerations and Datatypes. Types are managed by schema.org and are regularly updated as of February 2025, there are over 800 schema types.^[28] There are a number of subjects and elements that a web pages that can be marked up with using a Schema, with examples including:

• Article
• Breadcrumb
• Course
• Event
• FAQ
• LocalBusiness
• Logo
• Movie
• Product
• Recipe
• Review
• Video

Examples

Microdata

The following is an example^[29] of how to mark up information about a movie and its director using the Schema.org schemas and microdata. In order to mark up the data, the attribute itemtype along with the URL of the schema is used. The attribute itemscope defines the scope of the itemtype. The kind of the current item can be defined by using the attribute itemprop.

<div itemscope itemtype="http://schema.org/Movie">
  <h1 itemprop="name">Avatar</h1>
  <div itemprop="director" itemscope itemtype="http://schema.org/Person">
  Director: <span itemprop="name">James Cameron</span> 
(born <time itemprop="birthDate" datetime="1954-08-16">August 16, 1954</time>)
  </div>
  <span itemprop="genre">Science fiction</span>
  <a href="../movies/avatar-theatrical-trailer.html" itemprop="trailer">Trailer</a>
</div>

RDFa 1.1 Lite

<div vocab="http://schema.org/" typeof="Movie">
  <h1 property="name">Avatar</h1>
  <div property="director" typeof="Person">
  Director: <span property="name">James Cameron</span>
(born <time property="birthDate" datetime="1954-08-16">August 16, 1954</time>)
  </div>
  <span property="genre">Science fiction</span>
  <a href="../movies/avatar-theatrical-trailer.html" property="trailer">Trailer</a>
</div>

JSON-LD

<script type="application/ld+json">
{ 
  "@context": "http://schema.org/",
  "@type": "Movie",
  "name": "Avatar",
  "director": 
    { 
       "@type": "Person",
       "name": "James Cameron",
       "birthDate": "1954-08-16"
    },
  "genre": "Science fiction",
  "trailer": "../movies/avatar-theatrical-trailer.html" 
}
</script>