This factor reports whether the rendered page carries the Microdata attribute itemprop="reviewRating" — the property that binds a numeric rating to an individual review. It is a binary presence check (1 or 0) that pattern-matches the literal text, not a validation of the underlying review markup.
| Factor ID | RG-SCM-040 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether RankGear finds the Microdata attribute itemprop="reviewRating" in the rendered body after script elements are removed. That attribute is how a page’s Microdata declares the rating value belonging to a single review, so its presence signals that the page exposes review-rating structured data in the Microdata vocabulary rather than in JSON-LD or plain, unmarked text.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="reviewRating". It returns 1 when at least one match exists and 0 otherwise. The comparison runs against the rendered body with <script> elements stripped out, so the attribute must appear in the page’s actual markup to register.
What RankGear looks for
<div itemprop="reviewRating" itemscope itemtype="https://schema.org/Rating">
<span itemprop="ratingValue">4.5</span> out of
<span itemprop="bestRating">5</span>
</div>| Value | Meaning |
|---|---|
| 1 | The exact string itemprop="reviewRating" was found at least once in the script-stripped body. |
| 0 | The string was not present — no Microdata review-rating attribute in that literal form. |
How to optimize it
Use reviewRating only as part of a genuine rating attached to an individual review. Keep the value aligned with the rating shown to visitors, and match the vocabulary expected by its parent item type so the property nests inside a real review item rather than floating on its own. Treat this factor as an observation of what your markup exposes, not a target to hit for its own sake — adding the attribute without a legitimate review behind it serves no reader and risks structured-data ineligibility.
Important considerations
- The detector pattern-matches HTML text instead of parsing or validating a Microdata item graph, so a 1 confirms the string is present but not that the surrounding markup is well-formed.
- 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 before relying on the rating for rich results.
- This is a prioritization signal that tracks how review markup relates to position within a measured result set — presence of the attribute correlates with structured-data practice, it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.