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.
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
|
Type and Description | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following attributes are from the schema.org Product type |
|||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
| URL | |||||||||||||||||||||||||||||
|
Text A parent SKU, required to group all variant products belonging to the same product group together. |
|||||||||||||||||||||||||||||
|
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. |
|||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
|
Text Use the |
|||||||||||||||||||||||||||||
|
Text Use the
|
|||||||||||||||||||||||||||||
|
Number (in years) Use the Valid values are those defined by the
|
|||||||||||||||||||||||||||||
| Text | |||||||||||||||||||||||||||||
|
OR |
Text Use the |
||||||||||||||||||||||||||||
|
Text Use the Valid values are from the
|
|||||||||||||||||||||||||||||
|
Text Use the Valid values are from the WearableSizeSystemEnumeration type. They are mapped to feed values as follows:
|
|||||||||||||||||||||||||||||
|
Use the |
|||||||||||||||||||||||||||||
|
Use the |
|||||||||||||||||||||||||||||
|
Use the |
|||||||||||||||||||||||||||||
|
Use the |
|||||||||||||||||||||||||||||
The following schema.org properties are from the Offer type, which must be nested within a Product using the offers property (see examples below). |
|||||||||||||||||||||||||||||
| A valid URL to your product. | |||||||||||||||||||||||||||||
|
or: |
Note: |
||||||||||||||||||||||||||||
|
Valid values are from the
|
|||||||||||||||||||||||||||||
|
Valid values are from the
|
|||||||||||||||||||||||||||||
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
|
Type and Description |
|---|---|
The following attributes are from the schema.org OfferShippingDetails type. |
|
|
|
Text 2-digit ISO 3166-1 country code Use the |
|
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 |
|
|
Use the |
|
|
|
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 |
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
|
Type and Description |
|---|---|
The following schema.org properties are from the EnergyConsumptionDetails type. |
|
|
Valid values are from the schema.org |
|
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. |
|
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.
| Product data specification value | Schema.org enumeration value from theEUEnergyEfficiencyEnumeration type |
|---|---|
A+++ |
EUEnergyEfficiencyCategoryA3Plus |
A++ |
EUEnergyEfficiencyCategoryA2Plus |
A+ |
EUEnergyEfficiencyCategoryA1Plus |
A |
EUEnergyEfficiencyCategoryA |
B |
EUEnergyEfficiencyCategoryB |
C |
EUEnergyEfficiencyCategoryC |
D |
EUEnergyEfficiencyCategoryD |
E |
EUEnergyEfficiencyCategoryE |
F |
EUEnergyEfficiencyCategoryF |
G |
EUEnergyEfficiencyCategoryG |
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
|
Type and Description |
|---|---|
The following schema.org properties are from the UnitPriceSpecification type. |
|
|
Specify the unit pricing measure using a Use the |
|
|
Specify the unit pricing base measure using a Use the |
|
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.