Supported structured data attributes and values

Use structured data markup on your product landing pages to help Google retrieve up-to-date information about your products and offers directly from your website. Any structured data markup that is supported by Merchant Center will have corresponding attributes and accepted values, as listed in the product data specification. Your structured data must be matched to the corresponding values and attributes.

Not all attributes are supported by schema.org at this time.

Attributes and schema.org annotations

Attributes are one of the ways in which the product data you submit to Merchant Center is organized. Each attribute contains a single piece of information about a product, such as the product's title or description. Accurately matching the schema.org value to the corresponding product data specification attributes will lead to fewer errors when validating your feed.

Note: If you’re using automatic item updates, make sure to specify the schema.org properties price, priceCurrency, availability, and condition to increase its accuracy. Learn more about automatic item updates

Product Data Attribute

  • Schema.org Property
Type and Description
The following attributes are from the schema.org Product type

title

Text

description

Text

image_link

URL

item_group_id

Text

A parent SKU, required to group all variant products belonging to the same product group together.

gtin

Text

The GTIN that uniquely identifies your product.

Specify only one of these schema.org properties.

If you use GTIN values, they must be the correct length and contain the correct check digit.

material

Text

pattern

Text

mpn

Text

brand

Text

Use the brand property to specify a Brand object which specifies the brand through its name property.

gender

Text

Use the audience property to specify a PeopleAudience object which specifies the gender using its suggestedGender property. Valid values are those defined by the gender attribute:

male

female

unisex

age_group

Number (in years)

Use the audience property to specify a PeopleAudience object which specifies the age group using its suggestedMinAge and suggestedMaxAge properties.

Valid values are those defined by the age_group attribute:

Data spec Schema.org value
  suggestedMinAge
newborn 0
infant 0.25
toddler 1.0
kids 5.0
adult 13
Data spec Schema.org value
  suggestedMaxAge
newborn 0.25
infant 1.0
toddler 5.0
kids 13.0
adult Not specified

color

Text

size

OR

Text

Use the size property to specify a Text value or a SizeSpecification object, which specifies the size through its name property. The SizeSpecification object should be used when specifying sizeGroup and/or sizeSystem

size_type

Text

Use the size property to specify a SizeSpecification object which specifies the size type through its sizeGroup property.

Valid values are from the WearableSizeGroupEnumeration type. At most two values can be specified. They are mapped to feed values as follows:

Data spec schema value
big

WearableSizeGroupBig

maternity

WearableSizeGroupMaternity

petite

WearableSizeGroupPetite

plus

WearableSizeGroupPlus

regular

WearableSizeGroupRegular

tall

WearableSizeGroupTall

size_system

Text

Use the size property to specify a SizeSpecification object which specifies the size system through its sizeSystem property.

Valid values are from the WearableSizeSystemEnumeration type. They are mapped to feed values as follows:

Data spec schema value
AU

WearableSizeSystemAU

BR

WearableSizeSystemBR

CN

WearableSizeSystemCN

DE

WearableSizeSystemDE

EU

WearableSizeSystemEurope

FR

WearableSizeSystemFR

IT

WearableSizeSystemIT

JP

WearableSizeSystemJP

MEX

WearableSizeSystemMX

UK

WearableSizeSystemUK

US

WearableSizeSystemUS

product_length

value: Number
unitCode / unitText: Text

Use the depth property to specify a QuantitativeValue object which specifies the length of the product using the value property and the dimension using the unitCode (UN/CEFACT code "CMT' or "INH") or unitText ("cm" or "in") properties.

product_width

value: Number
unitCode / unitText: Text

Use the width property to specify a QuantitativeValue object which specifies the width of the product using the value property and the dimension using the unitCode (UN/CEFACT code "CMT' or "INH") or unitText ("cm" or "in") properties.

product_height

value: Number
unitCode / unitText: Text

Use the height property to specify a QuantitativeValue object which specifies the length of the product using the value property and the dimension using the unitCode (UN/CEFACT code "CMT' or "INH") or unitText (feed unit "cm" or "in") properties.

product_weight

value: Number
unitCode / unitText: Text

Use the weight property to specify a QuantitativeValue object which specifies the weight of the product using the value property and the dimension using the unitCode (UN/CEFACT code "LBR", "ONZ", "KGM", or "GRM") or unitText ("lb", "oz", "kg", or "g") properties.

The following schema.org properties are from the Offer type, which must be nested within a Product using the offers property (see examples below).

link

A valid URL to your product.

price

or:

price: Number. Submitted without currency symbols, thousands separators, or spaces (for example, '1498.99').

priceCurrency: Text. Submitted in a 3-letter ISO 4217 format (for example, USD, GBP, EUR), the currency should meet the language and currency requirements for your target country.

Note: price and priceCurrency can be provided directly under the Offer instance or indirectly via a priceSpecification property of type UnitPriceSpecification

availability

Valid values are from the ItemAvailability type. They’re mapped to feed values as follows:

Data spec Schema.org value
in_stock

InStock

LimitedAvailability

OnlineOnly

out_of_stock

Discontinued

InStoreOnly

OutOfStock

SoldOut

preorder

PreOrder

PreSale

backorder

BackOrder

condition

Valid values are from the OfferItemCondition type. They’re mapped to feed values as follows:

Data spec Schema.org value
new

NewCondition

refurbished

RefurbishedCondition

used

DamagedCondition

UsedCondition

Examples using JSON-LD

Single Product

The following example illustrates a basic product with a minimum set of properties. 

{
"@context": "https://schema.org/",
  "@type": "Product",
  "sku": "trinket-12345",
  "image": "https://www.example.com/trinket.jpg",
  "name": "Nice trinket",
  "description": "Trinket with clean lines",
  "gtin": "12345678901234",
  "brand": {
    "@type": "Brand",
    "name": "MyBrand"
  },
  "offers": {
    "@type": "Offer",
    "url": "http://www.example.com/trinket_offer",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock",
    "price": "39.99",
    "priceCurrency": "USD"

  }
}

The following example illustrates how to specify size type and size system using schema.org. The example specifies US size "XL" for a blue t-shirt intended for adults (13+ age group) in the male "Big&Tall" fashion department.

{
    "@context": "https://schema.org/",
    "@type": "Product",
    "sku": "12345",
    "image": "https://www.example.com/tshirt.jpg",
    "name": "Classic T-Shirt",
    "description": "All-cotton t-shirt in classic cut",
    "gtin": "12345678901234",
    "brand": {
      "@type": "Brand",
      "name": "MyBrand"
    },
    "material": "cotton",
    "color": "blue",
    "size": {
      "@type": "SizeSpecification",
      "name": "XL",
      "sizeSystem": "https://schema.org/WearableSizeSystemUS",
      "sizeGroup": [ 
         "https://schema.org/WearableSizeGroupBig",
         "https://schema.org/WearableSizeGroupTall" 
      ]
    },
    "audience": {
      "@type": "PeopleAudience",
      "suggestedGender": "male",
      "suggestedMinAge": 13
    },
    "offers": {
      "@type": "Offer",
      "url": "http://www.example.com/tshirt",
      "itemCondition": "https://schema.org/NewCondition",
      "availability": "https://schema.org/InStock",
      "price": "24.99",
      "priceCurrency": "USD"
    }
  }

 

Multiple unrelated products on one landing page

When your page contains multiple unrelated products and each product has its own structured data annotation, each annotation must contain information that identifies which product it is referring to.

For example, it’s recommended to provide the SKU (ID [id] attribute) or the GTIN ([gtin] attribute) in each annotation. If you don’t provide this information, the products on your landing page may not be matched to your structured product data. Learn more about setting up structured data on landing pages

Example

[
  {
    "@context": "https://schema.org/",
    "@type": "Product",
    "sku": "trinket-12345",
    "image": "https://www.example.com/trinket.jpg",
    "name": "Nice trinket",
    "description": "Trinket with clean lines",
    "gtin": "12345678901234",
    "brand": {
      "@type": "Brand",
      "name": "MyBrand"
    },
    "offers": {
      "@type": "Offer",
      "url": "http://www.example.com/trinket_offer",
      "itemCondition": "https://schema.org/NewCondition",
      "availability": "https://schema.org/InStock",
      "price": "39.99",
      "priceCurrency": "USD"
    }
  },
  {
    "@context": "https://schema.org/",
    "@type": "Product",
    "sku": "racket-12345",
    "image": "https://www.example.com/racket.jpg",
    "name": "Nice racket",
    "description": "Racket for Tennis",
    "gtin": "12345678901235",
    "brand": {
      "@type": "Brand",
      "name": "MyBrand"
    },
    "offers": {
      "@type": "Offer",
      "url": "http://www.example.com/racket_offer",
      "itemCondition": "https://schema.org/NewCondition",
      "availability": "https://schema.org/InStock",
      "price": "59.99",
      "priceCurrency": "USD"
    }
  }
]

Shipping

To specify shipping costs (recommended) for your product use the Schema.org OfferShippingDetails type, which must be nested within an Offer using the shippingDetails property and which maps on the shipping attribute in the Product Data Specification. Multiple shippingDetails properties can be provided.

Product Data Attribute

  • Schema.org Property
Type and Description
The following attributes are from the schema.org OfferShippingDetails type.

shipping.country

Text

2-digit ISO 3166-1 country code

Use the shippingDestination property to specify a DefinedRegion object which specifies the shipping country through its addressCountry property.

shipping.region

Text

2- or 3-digit ISO 3166-2 subdivision code, without country prefix. Supported for US, AU, or JP only. Examples: "NY", "NSW", or "03".

Use the shippingDestination property to specify a DefinedRegion object which specifies the shipping region through its addressRegion property. Use the same shippingDestination property to specify the addressRegion as is used to specify the addressCountry.

shipping.price

value: Number without currency symbols, thousands separators or spaces (e.g. '1498.99'). 

currency: Text. Submitted in 3-letter ISO 4217 format (e.g. 'USD', 'GBP', 'EUR'). The currency should be the same as submitted for the offer price.

Use the shippingRate property to specify a MonetaryAmount object which specifies value and currency.

shipping.min_handling_time

shipping.max_handling_time

shipping.min_transit_time

shipping.max_transit_time

 

Number (Non-negative, whole number)

Specifies the minimum and maximum number of business days for handling and transit of an order. Handling time specifies the time between when an order is placed and when it's handed off to a shipping carrier. Transit time specifies the time between when the product is handed off to a shipping carrier and when it's delivered to the customer.

Use the deliveryTime property to specify a ShippingDeliveryTime object which specifies handlingTime and transitTime of type QuantitativeValue. Use properties minValue and maxValue under QuantitativeValue to specify the minimum and maximum number of business days respectively.

Example

The following example illustrates how to specify shipping information using schema.org. The example specifies a shipping cost of USD 3.49 to the states of California, Nevada, and Arizona in the US. The handling time is between 0 and 1 business days and the transit time is between 1 and 5 business days. 

{
  "@context": "http://schema.org/",
  "@type": "Product",
  "sku": "trinket-12345",
  "gtin": "12345678901234",
  "image": "http://www.example.com/trinket.jpg",
  "name": "Nice trinket",
  "description": "Trinket with clean lines",
  "brand": {
    "@type": "Brand",
    "name": "MyBrand"
  },
  "offers": {
    "@type": "Offer",
    "url": "http://www.example.com/trinket_offer",
    "itemCondition": "http://schema.org/NewCondition",
    "availability": "http://schema.org/InStock",
    "priceSpecification": {
      "@type": "PriceSpecification",
      "price": 39.99,
      "priceCurrency": "USD"
    },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "US",
        "addressRegion": [ "CA", "NV", "AZ" ]
      },
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": 3.49,
        "currency": "USD"
      },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "handlingTime": {
          "@type": "QuantitativeValue",
          "minValue": 0,
          "maxValue": 1
        },
        "transitTime": {
          "@type": "QuantitativeValue",
          "minValue": 1,
          "maxValue": 5
        }
      }
    }
  }
}

 

Energy Efficiency

Schema.org supports energy efficiency labeling of products using the EnergyConsumptionDetails type, which can be specified for a Product that uses the EnergyConsumptionDetails property.

Product Data Attribute

  • Schema.org Property
Type and Description
The following schema.org properties are from the EnergyConsumptionDetails type.

energy_efficiency_class

Valid values are from the schema.org EUEnergyEfficiencyEnumeration type. Use the value mapping table below this table.

min_energy_efficiency_class

Add under the instance of EnergyConsumptionDetails that was used to specify the energy_efficiency_class attribute and use the same mapping table to select the value. If not provided and energy_efficiency_class is specified then then value EUEnergyEfficiencyCategoryG is assumed.

max_energy_efficiency_class

Add under the instance of EnergyConsumptionDetails that was used to specify the energy_efficiency_class attribute and use the same mapping table to select the value. If not provided and energy_efficiency_class is specified then value EUEnergyEfficiencyCategoryA3Plus is assumed.

Values for energyEfficiencyScale, energyEfficiencyScaleMin, and energyEfficiencyScaleMax are from the schema.org EUEnergyEfficiencyEnumeration enumeration type and are mapped to values for the 3 energy efficiency attributes in the product data specification as follows.

Example

The following example illustrates how to specify energy efficiency information using schema.org. The example specifies the EU energy efficiency class "C" with scale "A+" to "F" for a water heater.

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "sku": "1234-5678",
  "image": "https://www.example.com/waterheater.jpg",
  "name": "Water heater",
  "description": "Large capacity water heater",
  "gtin": "12345678901231",
  "mpn": "WH1234",
  "brand": {
    "@type": "Brand",
    "name": "ExampleWaterHeaterBrand"
  }, 
  "hasEnergyConsumptionDetails": {
    "energyEffiencyScale": "https://schema.org/EUEnergyEfficiencyCategoryC",
    "energyEffiencyScaleMax":
"https://schema.org/EUEnergyEfficiencyCategoryA1Plus",
    "energyEffiencyScaleMin": "https://schema.org/EUEnergyEfficiencyCategoryF"
  },

  "offers": {
    "@type": "Offer",
    "url": "http://www.example.com/hotwaterheater",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock",
    "price": 1799.00,
    "priceCurrency": "EUR"
  }
}

Unit pricing

Schema.org supports unit pricing of products using the referenceQuantity property under the UnitPriceSpecification type, provided using the priceSpecification property on Offer. When specifying unit pricing, also specify the price and currency of the product using the priceSpecification property (instead of directly using the price and priceCurrency properties on Offer).

Product Data Attribute

  • Schema.org Property
Type and Description
The following schema.org properties are from the UnitPriceSpecification type.

unit_pricing_measure

value: Number
unitCode / unitText: Text

Specify the unit pricing measure using a referenceQuantity property of type QuantitativeValue under the UnitPriceSpecification object used to specify the price of the offer. 

Use the value property and the unitCode (UN/CEFACT code) or unitText properties to specify the value and unit of the unit pricing measure. Refer to the unit_pricing_measure article for the supported values and units.

unit_pricing_base_measure

value: Number
unitCode / unitText: Text

Specify the unit pricing base measure using a valueReference property of type QuantitativeValue under the QuantitativeValue object that is used to specify the unit pricing measure.

Use the value property and the unitCode (UN/CEFACT code) or unitText properties to specify the value and unit of the unit pricing measure. Refer to the unit_pricing_base_measure article for the supported values and units.

Example

The following example illustrates a price of 3.99 Euro for a 5 KG bag of rice with a preferred standardized price per 1 KG. This means the product may show up to consumers with a unit price of .80 EUR / kilo.

 {
  "@context": "https://schema.org/",
  "@type": "Product",
  "sku": "basrice12345",
  "image": "https://www.example.com/rice.jpg",
  "name": "Basmati rice",
  "description": "Large bag of Organic Basmati white rice, 5 Kilogram",
  "gtin": "12345678901231",
  "brand": {
    "@type": "Brand",
    "name": "ExampleRiceBrand"
  },
  "offers": {
    "@type": "Offer",
    "url": "http://www.example.com/basrice1kg",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "3.99",
      "priceCurrency": "EUR",
      "referenceQuantity": {
        "@type": "QuantitativeValue",
        "value": 5,
        "unitCode": "KGM",
        "valueReference": {
          "value": "1",
          "unitCode": "KGM"
        }
      }
    }
  }
}

Test your markup

Test your schema.org implementation with the Rich Results tool (by reviewing the reporting for "Merchant Listings" structured data). Visit the Google Search Console Help Center to learn more about using the tool, debugging any issues, and interpreting your results in the tool. Also refer to the Product structured data article on Google Search for further documentation.

Requirements for structured data markup

  • Structured data markup must be present in the HTML returned from the web server. The structured data markup can’t be generated with JavaScript after the page has loaded.
  • Your landing page cannot change based on information about the customer, such as if you adapt prices based on a customer’s IP address or browser type.
  • Structured data must match the values that are shown to the customer. Providing incorrect data on your product landing pages is a violation of our web developer guidelines.
  • Google recommends the use of JSON-LD for your structured data.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

Search
Clear search
Close search
Google apps
Main menu
Search Help Center
false
false
true
71525
false
false