Which minimum fields make Product markup eligible for a product snippet?

Definition: For a Google product snippet, Product markup needs a product name and at least one of review, aggregateRating, or offers. The selected nested property must also follow the requirements for its own type.

Key facts

• Google's product snippet documentation lists name as a required Product property.
• Google requires one of review, aggregateRating, or offers for product snippets. One of the three is enough at the Product level.
• An offers branch uses Offer or AggregateOffer; Google's Offer requirements include price or priceSpecification.price.
• Schema.org describes review as a review of the item and aggregateRating as an overall rating based on a collection of reviews or ratings.
• Google supports product rich results for pages focused on a single product or multiple variants of the same product.

What is the minimum Product object?

Google's required-property table separates the product identity from the qualifying product information. name supplies the name of the product. A product snippet then needs review, aggregateRating, or offers. The three properties are alternatives at this level, so a page can meet this part of the table with a name plus one qualifying branch.

The documentation also says that a product snippet implementation with offers alone may receive a warning in the product snippets section of the Rich Results Test when it has neither review nor aggregateRating. Google still states that only one of the three properties is needed. That warning is therefore a testing signal about the combination of fields, rather than a fourth Product-level requirement.

What does each qualifying field describe?

Schema.org provides the vocabulary behind these fields. name is the name of the item. review points to a Review, which Schema.org defines as a review of the item. aggregateRating points to an AggregateRating, described as the overall rating based on a collection of reviews or ratings. offers describes an offer to provide the item and can use an Offer or a Demand in the Schema.org vocabulary.

Google's product snippet page narrows the offers branch for this feature to a nested Offer or AggregateOffer. If the branch uses Offer, Google lists price or priceSpecification.price as the required price field. A minimal shape for the product branch is:

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

The Product, Offer, name, and offer field names follow Google's product snippet example. Replace the placeholder values with the actual offer data. A review or aggregateRating branch follows the corresponding type requirements instead.

What page and testing conditions still apply?

The fields are only one part of eligibility. Google says product markup must follow its general structured data guidelines, Search Essentials, technical guidelines, and content guidelines. Its technical guidance currently limits product rich results to pages focused on a single product or multiple variants of the same product. A page such as “shoes in our shop” is not a specific product page.

Google's implementation workflow says to validate the markup with the Rich Results Test, deploy pages, and use URL Inspection to check how Google sees them. The page must be accessible to Google and must not be blocked by robots.txt, a noindex tag, or login requirements. Google also documents separate Search Console reports for merchant listings and product snippets because their associated experiences have different requirements.

Related terms

• Product structured data
• Offer structured data
• Review structured data
• AggregateRating structured data

FAQ

Do Product snippets require all three of review, aggregateRating, and offers?

No. Google says to provide one of the three, alongside name. A page can include more than one when the markup describes the product accurately.

Does offers alone satisfy the minimum?

Yes, at the Product level. Google's documentation says the Rich Results Test may show a warning for offers without review or aggregateRating, while still stating that one of the three is enough.

What additional field does an Offer need?

Google lists price or priceSpecification.price as the required price property for an Offer. The nested offer also needs to follow the applicable Offer requirements documented on the same page.

Sources

1. Google Search Central, "Product snippet (Product, Review, Offer) structured data", 8 September 2026
2. Schema.org, "Product", 16 September 2026

---

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