How do product snippets differ from merchant listings?

Definition: Product snippets are Google Search results for product pages where people cannot directly purchase the product. Merchant listings are for pages where customers can purchase products from the seller. The two features use different required properties in Product structured data.

Key facts

• Google's Product structured data introduction describes product snippets as suitable for pages where people cannot directly purchase the product.
• The same introduction describes merchant listings as suitable for pages where customers can purchase products from the seller.
• Google's product snippet documentation requires name and one of review, aggregateRating, or offers for product snippets.
• Google's merchant listing documentation requires name, image, and offers for the Product type.
• Product snippets accept Offer or AggregateOffer; merchant listings require Offer because the merchant must be the seller of the product.

What does each feature describe?

Google describes a product snippet as a text result with extra product information such as ratings, review information, price, and availability. Its product structured data introduction places this feature on pages where people cannot directly purchase the product. An editorial review can therefore describe a product and mark up a review without being the seller's purchase page.

Google describes a merchant listing as a purchase-page feature for customers buying from the merchant. It can highlight more specific product data, including price, availability, shipping information, and return information. The same introduction says that both features have their own enhancements, so the page's purchase context determines which requirements to inspect.

What does a product snippet require?

The product snippet documentation requires the Product name and one of three properties: review, aggregateRating, or offers. A page needs only one of those three for the product snippet type. Its offers property may contain an Offer or an AggregateOffer, depending on the content.

For an Offer, the price is required. availability and priceCurrency are recommended for product snippets, and Google states that priceCurrency is required for merchant listing experiences. This is a useful boundary when the same Product data is being evaluated for both features.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Executive Anvil",
  "offers": {
    "@type": "Offer",
    "price": 119.99,
    "priceCurrency": "USD"
  }
}

What changes on a purchase page?

Merchant listing markup requires the Product name, image, and offers. The offers value must be an Offer, because Google's requirement connects the listing to the merchant selling the product. This differs from product snippets, where an AggregateOffer can represent an aggregation of offers from multiple merchants.

The merchant listing documentation also requires an offer price, either through price or priceSpecification.price. It lists priceCurrency as required for merchant listing experiences. Shipping and return information are supported product details that merchant listings can highlight, while the page's eligibility still depends on the required properties and Google's guidelines.

How should a site check the markup?

Google recommends validating the structured data with the Rich Results Test and fixing critical errors. The merchant listing guide also says to use URL Inspection on deployed pages and to make sure Google can access the page without a robots.txt block, a noindex tag, or login requirements. The product introduction says that a site can provide product data through page markup, a Merchant Center feed, or both; using both helps Google understand and verify the data.

Google controls which enhancement appears. Its product introduction says result enhancements are shown at the discretion of each experience and may change over time.

Related terms

• Product structured data
• ProductGroup structured data
• Offer structured data
• Google Merchant Center

FAQ

Can one purchase page qualify for both features?

Yes. Google's introduction says that adding the required product information properties for merchant listings means a product page can also be eligible for product snippets. Each feature has its own enhancements.

Does merchant listing markup accept AggregateOffer?

No. Google allows Offer or AggregateOffer for product snippets, while merchant listings require Offer because the merchant must be the seller.

Is shipping markup required for every merchant listing?

Google describes shipping and return information as detailed product information that merchant listings can highlight. The required Product properties remain name, image, and offers; shipping is documented separately from that core list.

Sources

1. Google Search Central, "Introduction to Product structured data", 10 December 2025
2. Google Search Central, "Product snippet structured data", 8 September 2026
3. Google Search Central, "Merchant listing structured data", 8 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer