How is a business's price range expressed in LocalBusiness markup?

Definition: priceRange is a text property for describing a business's relative price range in LocalBusiness markup. Google documents two common forms: a numerical range such as $10-15 or a normalized sequence of currency signs such as $$$.

Key facts

• Google Search Central defines priceRange as Text and describes it as the relative price range of a business. Google's LocalBusiness documentation gives $10-15 and $$$ as common forms.
• Google says the field must be shorter than 100 characters. At 100 characters or longer, Google says it will not show a price range for the business.
• Schema.org defines priceRange as the price range of the business and gives $$$ as its example. The Schema.org property page lists Text as the expected value type and LocalBusiness as a type that uses the property.
• Schema.org's LocalBusiness type page lists priceRange with the value type Text and the same $$$ example.

Which formats does Google document?

Google's structured data table calls priceRange the relative price range of a business. It commonly accepts a numerical range, with $10-15 as the documentation's example, or a normalized number of currency signs, with $$$ as its example. The wording describes these as common forms, so the page does not define a separate required syntax for every business category.

The same documentation gives a length limit. The field must be shorter than 100 characters. If the value is 100 characters or longer, Google says it will not show a price range for the business. The limit applies to the value of this field, rather than to the surrounding JSON-LD document.

What does Schema.org define?

Schema.org's priceRange property defines the value as the price range of the business and gives $$$ as its example. Its property page lists Text as the expected type and LocalBusiness among the types on which the property is used. This matches Google's Text classification for the field.

The Schema.org LocalBusiness page also lists priceRange as Text, with the description “The price range of the business, for example $$$.” The two pages therefore describe a text value attached to a local business, while Google's page adds the display-oriented length guidance.

What does the markup look like?

The value is quoted as a string in JSON-LD. Google's LocalBusiness example uses the normalized currency-sign form:

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "priceRange": "$$$"
}

A numerical range follows the same text pattern, using the format shown in Google's table:

{
  "priceRange": "$10-15"
}

Google's page was last updated 8 September 2026. Its documented requirement is that the value remain below 100 characters if Google is to show a price range for the business.

Related terms

• LocalBusiness structured data
• Structured data
• JSON-LD
• Organization structured data

FAQ

Can priceRange be a numeric JSON value?

No. Google's LocalBusiness documentation classifies the field as Text, and Schema.org lists Text as the expected value type. Put the value in quotation marks, whether it contains a numerical range or currency signs.

Does Google document a fixed number of currency signs?

Google gives $$$ as an example of a normalized number of currency signs. The documentation also gives $10-15 as a numerical range, so both forms appear in its examples.

What happens when the value reaches 100 characters?

Google states that it will not show a price range when the field is 100 characters or longer. Keep the priceRange value shorter than that documented threshold.

Sources

1. Google Search Central, "Local Business (LocalBusiness) Structured Data", 8 September 2026
2. Schema.org, "priceRange", 16 September 2026
3. Schema.org, "LocalBusiness", 16 September 2026

---

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