- The error means a Product item has none of offers, review or aggregateRating, so Google cannot treat it as a product and the page cannot earn a product rich result.
- The fastest fix is an Offer with price, priceCurrency and availability that matches the price a visitor sees on the page.
- Never invent reviews or ratings. Only mark up real, visible reviews, or Google's guidelines treat the markup as spam.
- If the page is not a product page, remove the Product markup. Category, tag and home pages usually should not carry it.
- Test the URL in the Rich Results Test, then press Validate fix in Search Console. Validation asks Google to recheck the page; it does not guarantee a rich result.
What does the error mean?
Google shows this critical error in the Product snippets report in Search Console and in the Rich Results Test when a Product item has none of the three properties offers, review or aggregateRating. Without at least one of them the page cannot get a product rich result, because Google has no price, rating or review to show.
The full message is "Either 'offers', 'review', or 'aggregateRating' should be specified". It is reported against the Product item, not against the page as a whole. A page can still be indexed normally while the Product markup is invalid; the error only removes the chance of a product rich result.
Google's Product structured data documentation lists offers, review and aggregateRating as the properties that make a Product eligible (checked November 2026). At least one is required, and more complete markup can show more in the result.
Why does it happen?
The usual cause is Product markup on a page that has no product data to mark up, or a template that outputs Product markup without an Offer. These are the cases we see most often.
- A theme or plugin adds Product schema to category pages. The template wraps every page in Product markup, but a category page has no single price, review or rating. The result is a Product with no offers on hundreds of URLs.
- Products with no price. A quote-only, "call for price" or configurable product has no price to put in an Offer, so the Offer is left empty or omitted.
- Out-of-stock items with offers removed. A plugin deletes the Offer when stock reaches zero instead of setting availability to OutOfStock. The Product is then left with no offers at all.
- Review apps that load after render. A review widget injects the rating with JavaScript after the initial HTML, so Google sees a Product with no review or aggregateRating when it parses the markup.
- Product markup on pages that are not product pages. A blog post, landing page or home page carries Product markup copied from a template, but there is no real product on it.
Open the Product snippets report, pick a sample URL and read the item Google parsed. The page source usually shows which template or plugin emitted the markup, so you can fix it once at the template level instead of page by page.
How do I fix it?
Add an Offer with price, priceCurrency and availability, using the same price and stock status a visitor sees on the page. If the page already has real reviews, a review or aggregateRating is an alternative, but an Offer is usually the simplest correct fix for a product page that has a price.
The three Offer sub-fields Google needs are price, priceCurrency and availability. The JSON-LD example below is a complete Product item with a valid Offer.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Blue Trail Running Shoe",
"offers": {
"@type": "Offer",
"price": "89.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://example.com/products/blue-trail-running-shoe"
}
}
</script>
Use https://schema.org/InStock, OutOfStock, PreOrder or BackOrder for availability, and keep the value in sync with what the page shows. If the price is displayed with tax or currency formatting, the markup still uses the plain number and the ISO 4217 currency code.
The table shows when each of the three properties fits and the sub-fields Google requires.
offers, review and aggregateRating compared
| Property | When to use | Required sub-fields |
|---|---|---|
| offers | The page sells or lists one product with a real price and stock status. This is the usual fix for a product page. | price, priceCurrency, availability |
| review | The page shows a real review of the product, written by a person or organisation, visible on the page. | reviewRating (with ratingValue), author |
| aggregateRating | The page shows a real average rating from real reviews, and the rating is visible to visitors. | ratingValue, ratingCount or reviewCount |
Make the change in the template or plugin that renders the product page, not only in one product. Most ecommerce platforms have a Product schema setting or a snippet file you can edit once. Our schema markup guide covers JSON-LD basics and the other types that still earn rich results.
Should I add fake reviews or ratings?
No. Only mark up real reviews and ratings that are visible on the page, because inventing them is against Google's guidelines and can lead to a structured data manual action. The error is not a reason to paste in a five-star rating you do not have.
Google's Product documentation and its structured data guidelines require the markup to match content a visitor can see. Self-serving reviews about your own business, fake ratings and hidden review text are called out as spam. A product with no reviews should simply use an Offer; review and aggregateRating are optional alternatives, not a requirement.
If the page shows genuine reviews, load them in the server-rendered HTML, not only in a widget that appears after the page runs, so Google sees the same data a visitor sees.
What if the page is not a product page?
Remove the Product markup from any page that does not sell or describe a single product. Category pages, tag archives, the home page and ordinary blog posts should not carry Product schema, even when they mention products.
The error is Google telling you the markup does not fit the page. Removing the Product block from that template clears the error and lets the correct type, such as CollectionPage, Article or ItemList, describe the page instead. Our technical SEO checklist covers template-level checks like this one.
How do I validate the fix?
Test the fixed URL in the Rich Results Test, then press Validate fix in the Product snippets report in Search Console. Validation asks Google to recheck the affected URLs; it does not guarantee a rich result or ranking.
-
Test the live URL in the Rich Results Test
Open the Rich Results Test, enter the URL and check that the Product item is detected with no critical errors. The test shows the exact properties Google parsed.
-
Check the page source
View the raw HTML and confirm the Product block now contains
offers, or a realrevieworaggregateRating. If a plugin injects markup with JavaScript, check that it appears in the rendered page, not only in the browser after a click. -
Press Validate fix in Search Console
Open Enhancements → Product snippets, click the error row and choose Validate fix. Google rechecks the sample URLs and reports progress in the same report.
-
Wait and recheck
Validation can take days to a few weeks. If the error returns, some URLs still have a Product with no offers, review or aggregateRating, so find the remaining template and validate again.
Questions and answers
Offers, review or aggregateRating questions
Does this error stop the page from being indexed?
No. The page can still be indexed and rank normally. The error only means the Product item is not eligible for a product rich result, so you lose the price, rating or review in search, not the page itself.
Can I use review instead of offers?
Yes. offers, review and aggregateRating are alternatives: Google needs at least one of the three. An Offer with price, priceCurrency and availability is the usual fix for a product page that has a price, while review or aggregateRating fits a page with real, visible reviews.
Why does the error come back after I fix it?
Usually because more than one template or plugin outputs Product markup. Search Console groups URLs, so fix the shared template and check the other sample URLs. A review widget that loads after render can also leave the markup empty for Google.
Should I add aggregateRating without reviews?
No. Only add aggregateRating when the page shows a real average rating built from real reviews. Inventing a rating or review is against Google's structured data guidelines and can lead to a manual action.
Sources
- Product structured data — Google Search Central on Product, Offer, review and aggregateRating, checked November 2026
- Structured data guidelines — Google's rules on real, visible content and spammy markup

