Help Center

Menu

Microdata

Microdata refers to information that is embedded within a HTML document that is used to add semantic meaning to items within the content.

For example a document might mention a person, John Smith, in the text. Microdata allows the author of the content to identify that 'John Smith' is an entity of type person, with various attributes such as a first name, last name, email address, in a machine-readable format.

Funnelback does not include native support for handling microdata. However, if you have microdata within your web content, you can use the microdata plugin to index some of your microdata as additional metadata for your page.

Microdata plugin

The microdata plugin provides basic support for HTMl microdata that is defined as embedded microdata (via microdata element attributes), or as embedded JSON-LD.

When enabled, the microdata plugin will detect embedded microdata and JSON-LD in HTML web content and convert this to additional in-page metadata. This metadata will then become available after indexing to be mapped along with any other in-page <meta> tags.

The plugin only supports embedded microdata and JSON-LD. <script> tags that source JSON-LD from an external file are not processed. The plugin also does not support microdata in other formats such as RDFa.

Microdata example

All detected microdata will be added as metadata prefixed with microdata.

Consider the following HTML that includes JSON-LD microdata:

<div itemscope itemtype="http://schema.org/Product">
 <span itemprop="name">Panasonic White 60L Refrigerator</span>
 <img src="panasonic-fridge-60l-white.jpg" alt="">
  <div itemprop="aggregateRating"
       itemscope itemtype="http://schema.org/AggregateRating">
   <meter itemprop="ratingValue" min=0 value=3.5 max=5>Rated 3.5/5</meter>
   (based on <span itemprop="reviewCount">11</span> customer reviews)
  </div>
</div>

When the microdata filter is enabled, it will add the following meta tags into the HTMl:

<meta name="microdata.schema-org.AggregateRating.aggregateRating.ratingValue" content="Rated 3.5/5">
<meta name="microdata.schema-org.Product.aggregateRating.ratingValue.value" content="3.5">
<meta name="microdata.schema-org.AggregateRating.aggregateRating.ratingValue.value" content="3.5">
<meta name="microdata.schema-org.AggregateRating.aggregateRating.reviewCount" content="11">
<meta name="microdata.schema-org.Product.name" content="Panasonic White 60L Refrigerator">
<meta name="microdata.schema-org.Product.aggregateRating.reviewCount" content="11">
<meta name="microdata.schema-org.Product.aggregateRating.ratingValue" content="Rated 3.5/5">

JSON-LD example

All detected JSON-LD will be added as metadata prefixed with jsonld.

Consider the following HTML that is annotated with microdata properties:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PostalAddress",
  "addressCountry": "United States",
  "addressLocality": "Mountain View",
  "addressRegion": "CA",
  "name": "Google Inc.",
  "postOfficeBoxNumber": "1234",
  "postalCode": "94043"
}
</script>

When the microdata filter is enabled, it will add the following meta tags into the HTMl:

<meta name="jsonld.schema-org.PostalAddress.postalCode" content="94043">
<meta name="jsonld.schema-org.PostalAddress.addressRegion" content="CA">
<meta name="jsonld.schema-org.PostalAddress.postOfficeBoxNumber" content="1234">
<meta name="jsonld.schema-org.PostalAddress.addressLocality" content="Mountain View">
<meta name="jsonld.schema-org.PostalAddress.addressCountry" content="United States">
<meta name="jsonld.schema-org.PostalAddress.name" content="Google Inc.">

See also