This factor reports whether the Microdata property itemprop="priceRange" appears in a page’s rendered body (with scripts removed). It returns 1 when at least one literal match is found and 0 when none is. It is a presence signal that relates to how business and price information is marked up — it does not validate the surrounding Microdata graph, and it does not make a page rank.
| Factor ID | RG-SCM-033 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
The factor detects whether RankGear finds the Microdata attribute itemprop="priceRange" in the rendered body after script elements are removed. The priceRange property is a Microdata signal typically attached to a local business or service item to express an approximate price band (for example, a symbol like $$ or a short textual range). This factor only asks whether that specific attribute is present in the markup text — it does not read, interpret, or score the price value itself.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="priceRange". It returns 1 when at least one match exists and 0 otherwise. The match is against raw HTML text, so the attribute name, equals sign, double quotes, and property value must be contiguous exactly as written; single quotes or extra spacing do not match. Script elements are stripped before the search runs.
What RankGear looks for
<div itemscope itemtype="https://schema.org/Restaurant">
<span itemprop="priceRange">$$</span>
</div>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="priceRange" appears at least once in the rendered body. |
| 0 | No match — the attribute is absent, single-quoted, spaced differently, or lived only inside a removed script. |
How to optimize it
Use priceRange only as part of a truthful price range for a real local business or service. Keep the value aligned with the price information visible on the page, and use the vocabulary expected by the parent item type that carries it. Treat this factor as an observation of whether that markup exists, not a target to chase: adding the attribute where it does not honestly apply serves no one, and a bare 1 says nothing about whether the surrounding structured data is valid or eligible.
Important considerations
- The detector pattern-matches HTML text rather than parsing or validating a Microdata item graph, so a 1 confirms presence of the attribute string, not a correct or eligible structured-data item.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing do not match.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently — this factor does not check any of them.
- Correlation is not causation: this is a prioritization signal that tracks with position inside a measured result set, not a guarantee of any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.