Product
Add markup to your product pages so Google can provide detailed product information as a rich result in Google Search — including Google Images. Users can see price, availability, and review ratings right in search results.
Using markup to be eligible for product rich results lets you attract potential buyers while they are searching for items to buy on Google Search or images that include products you sell. Maintain the accuracy and freshness of your product information, so your customers find the relevant, current items they're looking for.
This page explains how to mark up your product information so that Google Search can display rich
results in Google Search. Product
markup also makes your products eligible to display with a
badge in Google Images, which can encourage more users to click your content.

There are two types of pages where you would typically use this markup:
- Product page that describes a single product
- Shopping aggregator page that lists a single product, along with information about different sellers offering that product
Based on how you mark up your content, your products may also be eligible for the following enhancements:
Product enhancements | |
---|---|
Shipping details: Help people see shipping costs and estimated delivery timeframes based on their location and your company's shipping policies. Shipping details can appear in the Overview and Stores tabs for a specific product result. This enhancement is only available in the US, in English, and on mobile devices.
To be eligible for this enhancement, add
|
![]() ![]() |
Price drop: Help people understand the lowest price for your product. Based on the running historical average of your product's pricing, Google automatically calculates the price drop. The price drop appearance is available in English in the US, on both desktop and mobile.
To be eligible for the price drop appearance, add an |
![]() ![]() |
Pros and cons: Help people see a high-level summary of the pros and cons of an editorial product review. The pros and cons appearance is available in Dutch, English, French, German, Italian, Japanese, Polish, Portuguese, Spanish, and Turkish in all countries where Google Search is available.
While Google tries to automatically understand the pros and cons of an editorial product
review, you can explicitly provide this information by adding the |
![]() ![]() |
How to add structured data
Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about how structured data works.
Here's an overview of how to build, test, and release structured data. For a step-by-step guide on how to add structured data to a web page, check out the structured data codelab.
- Add the required properties. Based on the format you're using, learn where to insert structured data on the page.
- Follow the guidelines.
- Validate your code using the Rich Results Test.
- Deploy a few pages that include your structured data and use the URL Inspection tool to test how Google sees the page. Be sure that your page is
accessible to Google and not blocked by a robots.txt file, the
noindex
tag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs. - To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.
Try it out
Single product page
Here's an example of a single product page.
JSON-LD
<html> <head> <title>Executive Anvil</title> <script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Product", "name": "Executive Anvil", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "description": "Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height.", "sku": "0446310786", "mpn": "925872", "brand": { "@type": "Brand", "name": "ACME" }, "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Fred Benson" } }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.4", "reviewCount": "89" }, "offers": { "@type": "Offer", "url": "https://example.com/anvil", "priceCurrency": "USD", "price": "119.99", "priceValidUntil": "2020-11-20", "itemCondition": "https://schema.org/UsedCondition", "availability": "https://schema.org/InStock" } } </script> </head> <body> </body> </html>
RDFa
<html> <head> <title>Executive Anvil</title> </head> <body> <div typeof="schema:Product"> <div rel="schema:review"> <div typeof="schema:Review"> <div rel="schema:reviewRating"> <div typeof="schema:Rating"> <div property="schema:ratingValue" content="4"></div> <div property="schema:bestRating" content="5"></div> </div> </div> <div rel="schema:author"> <div typeof="schema:Person"> <div property="schema:name" content="Fred Benson"></div> </div> </div> </div> </div> <div rel="schema:image" resource="https://example.com/photos/4x3/photo.jpg"></div> <div property="schema:mpn" content="925872"></div> <div property="schema:name" content="Executive Anvil"></div> <div property="schema:description" content="Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height."></div> <div rel="schema:image" resource="https://example.com/photos/1x1/photo.jpg"></div> <div rel="schema:brand"> <div typeof="schema:Brand"> <div property="schema:name" content="ACME"></div> </div> </div> <div rel="schema:aggregateRating"> <div typeof="schema:AggregateRating"> <div property="schema:reviewCount" content="89"></div> <div property="schema:ratingValue" content="4.4"></div> </div> </div> <div rel="schema:offers"> <div typeof="schema:Offer"> <div property="schema:price" content="119.99"></div> <div property="schema:availability" content="https://schema.org/InStock"></div> <div property="schema:priceCurrency" content="USD"></div> <div property="schema:priceValidUntil" datatype="xsd:date" content="2020-11-20"></div> <div rel="schema:url" resource="https://example.com/anvil"></div> <div property="schema:itemCondition" content="https://schema.org/UsedCondition"></div> </div> </div> <div rel="schema:image" resource="https://example.com/photos/16x9/photo.jpg"></div> <div property="schema:sku" content="0446310786"></div> </div> </body> </html>
Microdata
<html> <head> <title>Executive Anvil</title> </head> <body> <div> <div itemtype="https://schema.org/Product" itemscope> <meta itemprop="mpn" content="925872" /> <meta itemprop="name" content="Executive Anvil" /> <link itemprop="image" href="https://example.com/photos/16x9/photo.jpg" /> <link itemprop="image" href="https://example.com/photos/4x3/photo.jpg" /> <link itemprop="image" href="https://example.com/photos/1x1/photo.jpg" /> <meta itemprop="description" content="Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height." /> <div itemprop="offers" itemtype="https://schema.org/Offer" itemscope> <link itemprop="url" href="https://example.com/anvil" /> <meta itemprop="availability" content="https://schema.org/InStock" /> <meta itemprop="priceCurrency" content="USD" /> <meta itemprop="itemCondition" content="https://schema.org/UsedCondition" /> <meta itemprop="price" content="119.99" /> <meta itemprop="priceValidUntil" content="2020-11-20" /> </div> <div itemprop="aggregateRating" itemtype="https://schema.org/AggregateRating" itemscope> <meta itemprop="reviewCount" content="89" /> <meta itemprop="ratingValue" content="4.4" /> </div> <div itemprop="review" itemtype="https://schema.org/Review" itemscope> <div itemprop="author" itemtype="https://schema.org/Person" itemscope> <meta itemprop="name" content="Fred Benson" /> </div> <div itemprop="reviewRating" itemtype="https://schema.org/Rating" itemscope> <meta itemprop="ratingValue" content="4" /> <meta itemprop="bestRating" content="5" /> </div> </div> <meta itemprop="sku" content="0446310786" /> <div itemprop="brand" itemtype="https://schema.org/Brand" itemscope> <meta itemprop="name" content="ACME" /> </div> </div> </div> </body> </html>
Single product with shipping details
Here's an example of a single product page with shipping details. This example would result in a shipping rate of $3.49 for all users that live in zip codes between 98100 and 98199. For more examples, review the Shipping details best practices.
JSON-LD
<html> <head> <title>Nice trinket</title> <script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Product", "sku": "trinket-12345", "gtin14": "12345678901234", "image": [ "https://example.com/photos/16x9/trinket.jpg", "https://example.com/photos/4x3/trinket.jpg", "https://example.com/photos/1x1/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": "https://schema.org/NewCondition", "availability": "https://schema.org/InStock", "price": "39.99", "priceCurrency": "USD", "priceValidUntil": "2020-11-20", "shippingDetails": { "@type": "OfferShippingDetails", "shippingRate": { "@type": "MonetaryAmount", "value": "3.49", "currency": "USD" }, "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US", "postalCodeRange": { "postalCodeBegin": "98100", "postalCodeEnd": "98199" } }, "deliveryTime": { "@type": "ShippingDeliveryTime", "handlingTime": { "@type": "QuantitativeValue", "minValue": "0", "maxValue": "1" }, "transitTime": { "@type": "QuantitativeValue", "minValue": "1", "maxValue": "5" }, "cutOffTime": "19:30-08:00", "businessDays": { "@type": "OpeningHoursSpecification", "dayOfWeek": [ "https://schema.org/Monday", "https://schema.org/Tuesday", "https://schema.org/Wednesday", "https://schema.org/Thursday" ] } } } }, "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Fred Benson" } }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.4", "reviewCount": "89" } } </script> </head> <body> </body> </html>
RDFa
<html> <head> <title>Nice trinket</title> </head> <body> <div typeof="schema:Product"> <div property="schema:sku" content="trinket-12345"></div> <div property="schema:gtin14" content="12345678901234"></div> <div property="schema:name" content="Nice trinket"></div> <div rel="schema:image" resource="https://example.com/photos/16x9/trinket.jpg"></div> <div rel="schema:image" resource="https://example.com/photos/4x3/trinket.jpg"></div> <div rel="schema:image" resource="https://example.com/photos/1x1/trinket.jpg"></div> <div property="schema:description" content="Trinket with clean lines"></div> <div rel="schema:brand"> <div typeof="schema:Brand"> <div property="schema:name" content="MyBrand"></div> </div> </div> <div rel="schema:offers"> <div typeof="schema:Offer"> <div rel="schema:url" resource="https://example.com/trinket_offer"></div> <div property="schema:itemCondition" content="https://schema.org/NewCondition"></div> <div property="schema:availability" content="https://schema.org/InStock"></div> <div property="schema:price" content="39.99"></div> <div property="schema:priceCurrency" content="USD"></div> <div property="schema:priceValidUntil" datatype="xsd:date" content="2020-11-20"></div> <div rel="schema:shippingDetails"> <div typeof="schema:OfferShippingDetails"> <div rel="schema:shippingRate"> <div typeof="schema:MonetaryAmount"> <div property="schema:value" content="3.49"></div> <div property="schema:currency" content="USD"></div> </div> </div> <div rel="schema:shippingDestination"> <div typeof="schema:DefinedRegion"> <div property="schema:addressCountry" content="US"></div> <div rel="schema:postalCodeRange"> <div typeof="schema:PostalCodeRangeSpecification"> <div property="schema:postalCodeBegin" content="98100"></div> <div property="schema:postalCodeEnd" content="98199"></div> </div> </div> </div> </div> <div rel="schema:deliveryTime"> <div typeof="schema:ShippingDeliveryTime"> <div rel="schema:handlingTime"> <div typeof="schema:QuantitativeValue"> <div property="schema:minValue" content="0"></div> <div property="schema:maxValue" content="1"></div> </div> </div> <div rel="schema:transitTime"> <div typeof="schema:QuantitativeValue"> <div property="schema:minValue" content="1"></div> <div property="schema:maxValue" content="5"></div> </div> </div> <div property="schema:cutOffTime" content="19:30-08:00"></div> <div rel="schema:businessDays"> <div typeof="schema:OpeningHoursSpecification"> <div property="schema:dayOfWeek" content="https://schema.org/Monday"></div> <div property="schema:dayOfWeek" content="https://schema.org/Tuesday"></div> <div property="schema:dayOfWeek" content="https://schema.org/Wednesday"></div> <div property="schema:dayOfWeek" content="https://schema.org/Thursday"></div> </div> </div> </div> </div> </div> </div> </div> </div> <div rel="schema:review"> <div typeof="schema:Review"> <div rel="schema:reviewRating"> <div typeof="schema:Rating"> <div property="schema:ratingValue" content="4"></div> <div property="schema:bestRating" content="5"></div> </div> </div> <div rel="schema:author"> <div typeof="schema:Person"> <div property="schema:name" content="Fred Benson"></div> </div> </div> </div> </div> <div rel="schema:aggregateRating"> <div typeof="schema:AggregateRating"> <div property="schema:reviewCount" content="89"></div> <div property="schema:ratingValue" content="4.4"></div> </div> </div> </div> </body> </html>
Microdata
<html> <head> <title>Nice trinket</title> </head> <body> <div> <div itemtype="https://schema.org/Product" itemscope> <meta itemprop="sku" content="trinket-12345" /> <meta itemprop="gtin14" content="12345678901234" /> <meta itemprop="name" content="Nice trinket" /> <link itemprop="image" href="https://example.com/photos/16x9/trinket.jpg" /> <link itemprop="image" href="https://example.com/photos/4x3/trinket.jpg" /> <link itemprop="image" href="https://example.com/photos/1x1/trinket.jpg" /> <meta itemprop="description" content="Trinket with clean lines" /> <div itemprop="brand" itemtype="https://schema.org/Brand" itemscope> <meta itemprop="name" content="MyBrand" /> </div> <div itemprop="offers" itemtype="https://schema.org/Offer" itemscope> <link itemprop="url" href="http://www.example.com/trinket_offer" /> <meta itemprop="itemCondition" content="https://schema.org/NewCondition" /> <meta itemprop="availability" content="https://schema.org/InStock" /> <meta itemprop="price" content="39.99" /> <meta itemprop="priceCurrency" content="USD" /> <meta itemprop="priceValidUntil" content="2020-11-20" /> <div itemprop="shippingDetails" itemtype="https://schema.org/OfferShippingDetails" itemscope> <div itemprop="shippingRate" itemtype="https://schema.org/MonetaryAmount" itemscope> <meta itemprop="value" content="3.49" /> <meta itemprop="currency" content="USD" /> </div> <div itemprop="shippingDestination" itemtype="https://schema.org/DefinedRegion" itemscope> <meta itemprop="addressCountry" content="US" /> <div itemprop="postalCodeRange" itemtype="https://schema.org/PostalCodeRangeSpecification" itemscope> <meta itemprop="postalCodeBegin" content="98100" /> <meta itemprop="postalCodeEnd" content="98199" /> </div> </div> <div itemprop="deliveryTime" itemtype="https://schema.org/ShippingDeliveryTime" itemscope> <div itemprop="handlingTime" itemtype="https://schema.org/QuantitativeValue" itemscope> <meta itemprop="minValue" content="0" /> <meta itemprop="maxValue" content="1" /> </div> <div itemprop="transitTime" itemtype="https://schema.org/QuantitativeValue" itemscope> <meta itemprop="minValue" content="1" /> <meta itemprop="maxValue" content="5" /> </div> <meta itemprop="cutOffTime" content="19:30-08:00" /> <div itemprop="businessDays" itemtype="https://schema.org/OpeningHoursSpecification" itemscope> <meta itemprop="dayOfWeek" content="https://schema.org/Monday" /> <meta itemprop="dayOfWeek" content="https://schema.org/Tuesday" /> <meta itemprop="dayOfWeek" content="https://schema.org/Wednesday" /> <meta itemprop="dayOfWeek" content="https://schema.org/Thursday" /> </div> </div> </div> </div> <div itemprop="review" itemtype="https://schema.org/Review" itemscope> <div itemprop="author" itemtype="https://schema.org/Person" itemscope> <meta itemprop="name" content="Fred Benson" /> </div> <div itemprop="reviewRating" itemtype="https://schema.org/Rating" itemscope> <meta itemprop="ratingValue" content="4" /> <meta itemprop="bestRating" content="5" /> </div> </div> <div itemprop="aggregateRating" itemtype="https://schema.org/AggregateRating" itemscope> <meta itemprop="reviewCount" content="89" /> <meta itemprop="ratingValue" content="4.4" /> </div> </div> </div> </body> </html>
Shopping aggregator page
Here's an example of a shopping aggregator page.
JSON-LD
<html> <head> <title>Executive Anvil</title> <script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Product", "name": "Executive Anvil", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "description": "Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height.", "sku": "0446310786", "mpn": "925872", "brand": { "@type": "Brand", "name": "ACME" }, "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Fred Benson" } }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.4", "reviewCount": "89" }, "offers": { "@type": "AggregateOffer", "offerCount": "5", "lowPrice": "119.99", "highPrice": "199.99", "priceCurrency": "USD" } } </script> </head> <body> </body> </html>
RDFa
<html> <head> <title>Executive Anvil</title> </head> <body> <div typeof="schema:Product"> <div rel="schema:review"> <div typeof="schema:Review"> <div rel="schema:reviewRating"> <div typeof="schema:Rating"> <div property="schema:ratingValue" content="4"></div> <div property="schema:bestRating" content="5"></div> </div> </div> <div rel="schema:author"> <div typeof="schema:Person"> <div property="schema:name" content="Fred Benson"></div> </div> </div> </div> </div> <div rel="schema:aggregateRating"> <div typeof="schema:AggregateRating"> <div property="schema:reviewCount" content="89"></div> <div property="schema:ratingValue" content="4.4"></div> </div> </div> <div rel="schema:image" resource="https://example.com/photos/4x3/photo.jpg"></div> <div property="schema:mpn" content="925872"></div> <div property="schema:name" content="Executive Anvil"></div> <div property="schema:description" content="Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height."></div> <div rel="schema:image" resource="https://example.com/photos/1x1/photo.jpg"> </div> <div rel="schema:brand"> <div typeof="schema:Brand"> <div property="schema:name" content="ACME"></div> </div> </div> <div rel="schema:offers"> <div typeof="schema:AggregateOffer"> <div property="schema:offerCount" content="5"></div> <div property="schema:lowPrice" content="119.99"></div> <div property="schema:highPrice" content="199.99"></div> <div property="schema:priceCurrency" content="USD"></div> <div rel="schema:url" resource="https://example.com/anvil"></div> </div> </div> <div rel="schema:image" resource="https://example.com/photos/16x9/photo.jpg"></div> <div property="schema:sku" content="0446310786"></div> </div> </body> </html>
Microdata
<html> <head> <title>Executive Anvil</title> </head> <body> <div> <div itemtype="https://schema.org/Product" itemscope> <meta itemprop="mpn" content="925872" /> <meta itemprop="name" content="Executive Anvil" /> <link itemprop="image" href="https://example.com/photos/16x9/photo.jpg" /> <link itemprop="image" href="https://example.com/photos/4x3/photo.jpg" /> <link itemprop="image" href="https://example.com/photos/1x1/photo.jpg" /> <meta itemprop="description" content="Sleeker than ACME's Classic Anvil, the Executive Anvil is perfect for the business traveler looking for something to drop from a height." /> <div itemprop="offers" itemtype="https://schema.org/AggregateOffer" itemscope> <meta itemprop="lowPrice" content="119.99" /> <meta itemprop="highPrice" content="199.99" /> <meta itemprop="offerCount" content="6" /> <meta itemprop="priceCurrency" content="USD" /> </div> <div itemprop="aggregateRating" itemtype="https://schema.org/AggregateRating" itemscope> <meta itemprop="reviewCount" content="89" /> <meta itemprop="ratingValue" content="4.4" /> </div> <div itemprop="review" itemtype="https://schema.org/Review" itemscope> <div itemprop="author" itemtype="https://schema.org/Person" itemscope> <meta itemprop="name" content="Fred Benson" /> </div> <div itemprop="reviewRating" itemtype="https://schema.org/Rating" itemscope> <meta itemprop="ratingValue" content="4" /> <meta itemprop="bestRating" content="5" /> </div> </div> <meta itemprop="sku" content="0446310786" /> <div itemprop="brand" itemtype="https://schema.org/Brand" itemscope> <meta itemprop="name" content="ACME" /> </div> </div> </div> </body> </html>
Pros and cons
Here's an example of an editorial product review page with pros and cons.
JSON-LD
<html> <head> <title>Cheese Knife Pro review</title> <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "Product", "name": "Cheese Grater Pro", "review": { "@type": "Review", "name": "Cheese Knife Pro review", "author": { "@type": "Person", "name": "Pascal Van Cleeff" }, "positiveNotes": { "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Consistent results" }, { "@type": "ListItem", "position": 2, "name": "Still sharp after many uses" } ] }, "negativeNotes": { "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "No child protection" }, { "@type": "ListItem", "position": 2, "name": "Lacking advanced features" } ] } } } </script> </head> <body> </body> </html>
RDFa
<html> <head> <title>Cheese Knife Pro review</title> </head> <body> <div typeof="schema:Product"> <div property="schema:name" content="Cheese Knife Pro review"></div> <div rel="schema:review"> <div typeof="schema:Review"> <div rel="schema:positiveNotes"> <div typeof="schema:ItemList"> <div rel="schema:itemListElement"> <div typeof="schema:ListItem"> <div property="schema:position" content="1"></div> <div property="schema:name" content="Consistent results"></div> </div> <div typeof="schema:ListItem"> <div property="schema:position" content="2"></div> <div property="schema:name" content="Still sharp after many uses"></div> </div> </div> </div> </div> <div rel="schema:negativeNotes"> <div typeof="schema:ItemList"> <div rel="schema:itemListElement"> <div typeof="schema:ListItem"> <div property="schema:position" content="1"></div> <div property="schema:name" content="No child protection"></div> </div> <div typeof="schema:ListItem"> <div property="schema:position" content="2"></div> <div property="schema:name" content="Lacking advanced features"></div> </div> </div> </div> </div> <div rel="schema:author"> <div typeof="schema:Person"> <div property="schema:name" content="Pascal Van Cleeff"></div> </div> </div> </div> </div> </div> </body> </html>
Microdata
<html> <head> <title>Cheese Knife Pro review</title> </head> <body> <div itemtype="https://schema.org/Product" itemscope> <meta itemprop="name" content="Cheese Knife Pro" /> <div itemprop="review" itemtype="https://schema.org/Review" itemscope> <div itemprop="author" itemtype="https://schema.org/Person" itemscope> <meta itemprop="name" content="Pascal Van Cleeff" /> </div> <div itemprop="positiveNotes" itemtype="https://schema.org/ItemList" itemscope> <div itemprop="itemListElement" itemtype="https://schema.org/ListItem" itemscope> <meta itemprop="position" content="1" /> <meta itemprop="name" content="Consistent results" /> </div> <div itemprop="itemListElement" itemtype="https://schema.org/ListItem" itemscope> <meta itemprop="position" content="2" /> <meta itemprop="name" content="Still sharp after many uses" /> </div> </div> <div itemprop="negativeNotes" itemtype="https://schema.org/ItemList" itemscope> <div itemprop="itemListElement" itemtype="https://schema.org/ListItem" itemscope> <meta itemprop="position" content="1" /> <meta itemprop="name" content="No child protection" /> </div> <div itemprop="itemListElement" itemtype="https://schema.org/ListItem" itemscope> <meta itemprop="position" content="2" /> <meta itemprop="name" content="Lacking advanced features" /> </div> </div> </div> </div> </body> </html>
Guidelines
Product rich results provide users with information about a specific
product, such as its price, availability, and reviewer ratings. For your Product
markup to be eligible for this rich treatment, you must follow these guidelines:
Technical guidelines
- Use markup for a specific product, not a category or list of products. For example, "shoes in our shop" is not a specific product. Currently, product rich results only support pages that focus on a single product. This includes product variants where each product variant has a distinct URL. We recommend focusing on adding markup to product pages instead of pages that list products or a category of products.
- If you add a review for the product, the reviewer's name must be a valid name for a
Person
orTeam
.Not recommended: 50% off on Black Friday
Recommended: "James Smith" or "CNET Reviewers"
- If you add pros and cons structured data, you must follow these guidelines:
- Currently, only editorial product review pages are eligible for the pros and cons appearance in Search, not merchant product pages or customer product reviews.
- There must be at least two statements about the product. It can be any combination of
positive and/or negative statements (for example,
ItemList
markup with two positive statements is valid). - The pros and cons must be visible to users on the page.
To include product information in Google Images, you must add additional properties:
- To show your product information in the rich image viewer: Include the
name
,image
,price
, andpriceCurrency
properties. - To show your product information in the Related Items feature: Include the
name
,image
,price
,priceCurrency
, andavailability
properties.
Content guidelines
- We don't allow content that promotes widely prohibited or regulated goods, services, or information that may facilitate serious, immediate, or long term harm to people. This includes content related to firearms and weapons, recreational drugs, tobacco and vaping products, and gambling-related products.
Shipping details best practices
Indicating free shipping
If you offer free shipping for specific products, set the shippingRate
to zero for all regions where you ship those products on your product pages. For example, if
you offer free shipping to the state of New York, you could implement the following for your
products that ship to New York:
"shippingDetails": { "@type": "OfferShippingDetails", "shippingRate": { "@type": "MonetaryAmount", "value": "0", "currency": "USD" }, "shippingDestination": [{ "@type": "DefinedRegion", "addressCountry": "US", "addressRegion": ["NY"] }] }
Indicating regions that you don't ship to
To set regions where you don't ship your products to, add the doesNotShip
property. This property supersedes your other shipping settings. For example, if you ship
products to the US, but don't ship products to Alaska or Hawaii, you could implement the
following for your products that don't ship to those states:
"shippingDetails": { "@type": "OfferShippingDetails", "doesNotShip": true, "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US", "addressRegion": ["AK", "HI"] } }
Indicating multiple shipping services for the same delivery region
Sometimes merchants might have multiple options for users to select when shipping a product to
a destination (for example, Express Overnight, Rushed 2-day, and Standard). You can indicate
each of these by using multiple shippingDetails
properties, each
with different combinations of the shippingRate
and
deliveryTime
properties.
If you have multiple shippingRate
properties for the same delivery
destination, Google will display data based on your cheapest shipping option.
Structured data type definitions
You must include the required properties for your content to be eligible for display as a rich result. You can also include the recommended properties to add more information about your content, which could provide a better user experience.
Product
The full definition of Product
is available at
schema.org/Product. When you mark up
your content for product information, use the following properties of the
schema.org Product
type:
Required properties | |
---|---|
name |
The name of the product. |
Either review or aggregateRating or offers |
You must include one of the following properties: |
Recommended properties | |
---|---|
aggregateRating |
A nested |
brand |
The brand of the product. |
description |
The product description. |
image |
Repeated The URL of a product photo. Pictures clearly showing the product (for example, against a white background) are preferred. Additional image guidelines:
For example: "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ] |
offers
|
A nested
To be eligible for the price drop appearance, add |
review
|
A nested
To manually tell Google about the pros and cons of an editorial product review page,
add the |
gtin | gtin8 | gtin13 | gtin14 | mpn | isbn |
Include all applicable global identifiers; these are described at schema.org/Product. |
sku |
Merchant-specific identifier for product. |
Offer
The full definition of Offer
is available at
schema.org/Offer. When marking up
offers within a product, use the following properties of the schema.org
Offer
type:
Required properties | |
---|---|
price |
The offer price of a product. Follow schema.org usage guidelines.
Here's an example of the "offers": { "@type": "Offer", "price": "39.99" } Here's an example of how to specify that a product is available without payment: "offers": { "@type": "Offer", "price": "0" } |
Recommended properties | |
---|---|
availability |
The possible product availability options. Use one of the following values and express
it with a URL link in the markup. Google also understands their short names (for
example
|
itemOffered |
The item being sold. Typically, this includes a nested product, but it can also contain other item types or text. |
priceCurrency |
The currency used to describe the product price, in three-letter ISO 4217 format. |
priceValidUntil |
The date (in ISO 8601
date format) after which the price will no longer be available, if applicable. Your product snippet
may not display if the |
shippingDetails |
Nested information about the shipping policies and options associated with an
|
url |
A URL to the product web page (that includes the |
OfferShippingDetails
OfferShippingDetails
enables people to see shipping costs and
estimated delivery timeframes based on their location and your company's shipping policies.
To make your products eligible for the shipping details
enhancement, add the following OfferShippingDetails
properties to your product pages in addition to Product
structured data. While OfferShippingDetails
isn't required, you
must add the following properties if you want your shipping details to be eligible for
the shipping details enhancement.
The full definition of OfferShippingDetails
is available at
schema.org/OfferShippingDetails.
Required properties | |
---|---|
shippingDestination |
Indicates shipping destinations. Specify
the |
shippingDestination.addressCountry |
The 2-digit country code, in ISO 3166-1 format. |
Recommended properties | |||||||
---|---|---|---|---|---|---|---|
deliveryTime |
The total delay between the receipt of the order and the goods reaching the final customer. Nest the following properties: |
||||||
deliveryTime.businessDays |
The days that orders are processed. Specify the specific days with the
|
||||||
deliveryTime.businessDays.dayOfWeek |
The name of the days when orders are processed. For orders that are received outside of business days, processing starts on the next business day. The non-business days in between are added to the handling time. Use the following enumerations: |
||||||
deliveryTime.cutOffTime |
The time after which new orders are no longer processed on that same day, in ISO 8601 format. One day gets added to the handling time. |
||||||
deliveryTime.handlingTime |
The typical delay between the receipt of the order and the goods either leaving the
warehouse or being prepared for pickup, in case the delivery method is on site pickup. Specify
the |
||||||
deliveryTime.handlingTime.minValue |
The minimum number of days that a product is in transit between the receipt of the order and the goods either leaving the warehouse or being prepared for pickup, in case the delivery method is on site pickup. The value must be a non-negative, whole number. |
||||||
deliveryTime.handlingTime.maxValue |
The maximum number of days that a product is in transit between the receipt of the order and the goods either leaving the warehouse or being prepared for pickup, in case the delivery method is on site pickup. The value must be a non-negative, whole number. |
||||||
deliveryTime.transitTime |
The typical delay the order has been sent for delivery and the goods reach the final customer. |
||||||
deliveryTime.transitTime.maxValue |
The maximum number of days that a product is in transit between being sent out for delivery and reception by the final customer. The value must be a non-negative, whole number. |
||||||
deliveryTime.transitTime.minValue |
The minimum number of days that a product is in transit between being sent out for delivery and reception by the final customer. The value must be a non-negative, whole number. |
||||||
doesNotShip |
Indicates when shipping to a particular |
||||||
Either shippingDestination.addressRegion or a postal code |
A region or postal code information, if applicable. Don't provide both a region and postal code information.
If you include If you include a postal code, it must be one of these properties:
|
||||||
shippingRate |
Information about the cost of shipping to the specified destination. Specify the You can only specify one
|
||||||
shippingRate.currency |
The currency of the shipping cost, in 3-letter
ISO 4217 format.
The currency must be the same as the currency specified in the
|
||||||
shippingRate.value |
The cost of shipping to the To specify free shipping, set the value to 0. |
The following properties are in beta (and not required), and aren't currently surfaced as shipping details in product rich results. However, providing this information helps Google understand the relationship between a product and other related shipping pages on your site. Google may use this information to develop other rich results.
Beta: recommended properties | |
---|---|
shippingSettingsLink |
The URL to a page on your site that outlines your company's shipping policies. This page must contain one or more policies that are applicable to this product. |
Alternative approach to configuring shipping settings with Google
Retailer shipping policies can get complicated and may change frequently. If you're having trouble indicating and keeping your shipping details up-to-date with markup, consider configuring your shipping settings in Google Merchant Center.
AggregateOffer
The full definition of AggregateOffer
is available at
schema.org/AggregateOffer. An
AggregateOffer
is a kind of Offer
representing an aggregation of
other offers. When marking up aggregate offers within a product, use the following properties
of the schema.org AggregateOffer
type:
Required properties | |
---|---|
lowPrice |
The lowest price of all offers available. Use a floating point number. |
priceCurrency |
The currency used to describe the product price, in three-letter ISO 4217 format. |
Recommended properties | |
---|---|
highPrice |
The highest price of all offers available. Use a floating point number. |
offerCount |
The number of offers for the product. |
positiveNotes
and/or negativeNotes
The positiveNotes
and/or negativeNotes
properties enable people to
see a high-level summary of the pros and cons of an editorial
product review. To manually tell Google about the pros and cons of
an editorial product review, add the positiveNotes
and/or negativeNotes
properties to your nested product review
.
Required properties | |
---|---|
negativeNotes
|
A nested negative statement of the product.
To list multiple negative statements, specify multiple "review": { "@type": "Review", "negativeNotes": { "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "No child protection" }, { "@type": "ListItem", "position": 2, "name": "Lacking advanced features" } ] } } |
negativeNotes.itemListElement
|
An array of negative statements about the product, listed in a specific order. Specify each negative statement with a |
negativeNotes.itemListElement.name
|
The key statement of the negative review. |
positiveNotes
|
A nested positive statement of the product.
To list multiple positive statements, specify multiple "review": { "@type": "Review", "positiveNotes": { "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Consistent results" }, { "@type": "ListItem", "position": 2, "name": "Still sharp after many uses" } ] } } |
positiveNotes.itemListElement
|
An array of positive statements about the product, listed in a specific order. Specify each positive statement with a |
positiveNotes.itemListElement.name
|
The key statement of the positive review. |
Recommended properties | |
---|---|
negativeNotes.itemListElement.position
|
The position of the negative review. Position 1 signifies the first statement in the list of negative statements. |
positiveNotes.itemListElement.position
|
The position of the positive review. Position 1 signifies the first statement in the list of positive statements. |
Monitor rich results with Search Console
Search Console is a tool that helps you monitor how your pages perform in Google Search. You don't have to sign up for Search Console to be included in Google Search results, but it can help you understand and improve how Google sees your site. We recommend checking Search Console in the following cases:
- After deploying structured data for the first time
- After releasing new templates or updating your code
- Analyzing traffic periodically
After deploying structured data for the first time
After Google has indexed your pages, look for issues using the relevant Rich result status report. Ideally, there will be an increase of valid pages, and no increase in errors or warnings. If you find issues in your structured data:
- Fix the errors.
- Inspect a live URL to check if the issue persists.
- Request validation using the status report.
After releasing new templates or updating your code
When you make significant changes to your website, monitor for increases in structured data errors and warnings.- If you see an increase in errors, perhaps you rolled out a new template that doesn't work, or your site interacts with the existing template in a new and bad way.
- If you see a decrease in valid items (not matched by an increase in errors), perhaps you are no longer embedding structured data in your pages. Use the URL Inspection tool to learn what is causing the issue.
Analyzing traffic periodically
Analyze your Google Search traffic using the Performance Report. The data will show you how often your page appears as a rich result in Search, how often users click on it and what is the average position you appear on search results. You can also automatically pull these results with the Search Console API.Troubleshooting
If you're having trouble implementing or debugging structured data, here are some resources that may help you.
- If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.
- Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the General Structured Data Guidelines.
- You might have an error in your structured data. Check the list of structured data errors.
- If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix structured data issues, use the Manual Actions report.
- Review the guidelines again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues.
- Troubleshoot missing rich results / drop in total rich results.
- Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the Google Search crawling and indexing FAQ.
- Ask a question in the Google Search Central office hours.
- Post a question in the Google Search Central forum.