Menu
I am trying to determine what are the acceptable values for the priceRange parameter. On Google I see "$$$" and that's it.
Can someone explain if I should be using $$$ literally or a decimal amount.
583
$ = Inexpensive, usually $10 and under. $$ = Moderately expensive, usually between $10-$25. $$$ = Expensive, usually between $25-$45. $$$$ = Very Expensive, usually $50 and up.
Definition of dollar sign : a mark $ placed before a number to indicate that it stands for dollars.
In short, a price range is the spread of numbers between the lowest and the highest value of a product or service at a given time and in a given place.
They indicate whether the items on a particular restaurant's menu are inexpensive ($), moderately priced ($$), or expensive ($$$).
It seems there is no "standard" for this, and probably is born out of the rating system for Restaurants.
It seems the convention is:
- $ = Inexpensive, usually $10 and under
- $$ = Moderately expensive, usually between $10-$25
- $$$ = Expensive, usually between $25-$45
- $$$$ = Very Expensive, usually $50 and up
Source
It seems TripAdvisor use the local currency symbol as the indicator:
As a reviewer in Korean, you will fill in according to Won ₩, in Greek it will be according to Euros €. Aussies, on the .com.au version of the website get just $ signs, so rather subtle there. The understanding would be AUD$.
Source
But a user has quite rightly pointed out on the official schema.org Github that priceRange is ambiguous.
The property schema.org/priceRange is ambiguous because it specifies text for a currency range...
Source
Use the
priceproperty with a range modeled as aPriceSpecificationhttp://schema.org/priceSource - Github Issue
196
The priceRange property seems pretty meaningless, as Shannon points out.
But Google has (within the last few days, as far as I'm aware) started recommending it for all localBusiness structured data, triggering warnings in the structured data testing tool. So, I expect many businesses to suddenly start expressing their pricing in arbitrary strings of $$$, especially those for whom an explicit price list isn't appropriate, e.g. where prices can only be quoted upon request.
It seems that the issue is creating some confusion on the Google product forum, with new image errors and address warnings have started appearing alongside the priceRange warnings. It's possible that Google has unintentionally started treating all businesses as restaurants and will backtrack, but I'm only speculating.
(The question is about reviews, rather than localBusiness data, so this may not be directly relevant to the OP. It's hopefully of interest to others finding this thread first—as I did—after seeing priceRange warnings in the structured data testing tool. I considered entering this as a comment under Shannon's answer, but didn't have enough reputation points...)
43
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
