Questions · Evaluate
Does a price range count as price data for agents?
A range is better than nothing, and for a product with genuinely varied variants an AggregateOffer is correct. A single price per purchasable variant is stronger, because it lets an agent answer about the specific thing the shopper asked for.
Why it happens
Price is the single field an agent cannot proceed without, because almost every shopping instruction contains a budget, a comparison or a total. When the field is absent from both the markup and the delivered text, the agent has nothing to reason with.
The common cause is a currency or pricing app that rewrites the visible price in the browser while the JSON-LD is emitted with a placeholder, a zero, or no offers object. The page looks correct to every human who checks it, which is why this survives so long.
This comes up at the Evaluate stage. The full treatment, including how to reproduce it and what to change, is on Price is not readable without running the page.
Related questions
Run a free scan and find out which of these your store actually hits.