Why does Google reject price ranges in product structured data?

What exactly does Google mean by a "specific value"?

Google firmly blocks any attempt to use a price range (e.g., "49.99€ - 99.99€") in the price property of the Offer object. You need a single, precise value, expressed numerically (e.g., "79.99").

This change directly affects sites that display customizable products or those with variable options. Price drop display becomes impossible if you don't provide a fixed price in your structured data.

Why this restriction on price drops now?

Google's goal is to avoid vague promises in rich results. A price drop displayed in SERPs must be immediately verifiable — impossible if the price varies depending on chosen options.

Google also wants to reduce misleading click-through rates. A user who sees "-20%" in a snippet expects a precise price, not to discover "starting from X" on the product page.

What's the difference with other rich product displays?

Other enhancements — ratings, availability, image — still tolerate certain flexibilities. But price drop display is subject to this strict criterion: offer present plus single price value.

Without an offer or with a price range, you may keep the current price display, but no discount mention will appear in the snippet.

• The price in Offer must be a single numeric value
• Price ranges (minPrice / maxPrice) do not qualify for price drop display
• The Offer object is mandatory — no alternative via AggregateOffer alone
• Price drops only display if Google can compare two fixed values (current price vs. old price)

Does this requirement align with e-commerce reality?

Let's be honest: many catalogs operate on dynamic pricing models. Product variants, personalized pricing, B2B pricing grids… Google imposes here a constraint that doesn't always match the actual business structure.

The problem is that for certain sectors — online printing, custom furniture, configurable services — a single price makes no sense. You face a choice: sacrifice data accuracy or forgo price drop display.

What are the risks if we bypass this rule?

Some sites attempt to simulate a fixed price by taking the median price or the most-sold variant's price. Technically, this passes schema.org validation, but Google can penalize inconsistency if the user lands on a page where the actual price differs. [To verify] — Google hasn't published an official tolerance threshold.

Another gray area: sites using AggregateOffer with multiple child Offer objects, each with a specific price. Google's documentation remains vague on handling these cases — difficult to know which offer will be retained for display.

Is this statement consistent with observed practices?

In the field, we observe that Google already ignores price ranges for several months — Alan Kent's statement simply formalizes an already-existing practice. Nothing revolutionary, then.

However, the lack of clear guidelines on edge cases — products with mandatory options, prices varying by geolocation — remains frustrating. Google prefers to impose a strict rule rather than document exceptions.

What must be done concretely to stay eligible?

First step: audit your product structured data with Search Console or a schema.org validation tool. Verify that each Product has an Offer object with a price property containing a single numeric value.

If you have variant products, two options — either create a dedicated page per variant (each with its own schema), or choose to markup only the default variant with its specific price. The second solution is simpler but limits coverage.

What errors must be avoided at all costs?

Never markup a range with "price": "50-100" — Google simply ignores this syntax. If you want to express min/max prices, use AggregateOffer, but know that it does not qualify for price drop display.

Another common pitfall: forgetting to specify priceCurrency. Without this attribute, even a specific price can be invalidated. Always use ISO 4217 code (EUR, USD, GBP…).

How can I verify my implementation is compliant?

Use Google's Rich Results Test on a representative product URL. If you see a warning or error on Offer, your structure isn't compliant.

Then check Search Console (Enhancements > Products) for the rate of eligible pages. A sudden drop in the number of pages with valid markup often signals a price range problem not detected in dev.

• Verify that each Product has an Offer object with price as a single numeric value
• Remove any price ranges from product structured data
• Add priceCurrency systematically (e.g., "EUR")
• Test with Rich Results Test and validate in Search Console
• For variant products, decide on a strategy: page per variant or markup default variant only
• Monitor error reports in Search Console after deployment