Has MicroData Rating Value checks whether the rendered HTML contains the Microdata attribute itemprop="ratingValue", returning 1 when at least one match is present and 0 when none is. It is a text pattern match on the markup, not a validation of the surrounding rating schema, so a detected attribute does not confirm that the structured data is valid or eligible for rich results.
| Factor ID | RG-SCM-037 |
|---|---|
| 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="ratingValue" in the rendered body after script elements are removed. The ratingValue property carries the numeric score of a rating inside a schema.org item — for example the value in a Review or an AggregateRating. The factor records only that the attribute string appears, not what the value is or which item type it belongs to.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="ratingValue". It returns 1 when at least one match exists and 0 otherwise. Because the search runs against raw HTML text rather than a parsed item graph, the attribute name, equals sign, double quotes, and property value must be contiguous for a match to register.
What RankGear looks for
<span itemprop="ratingValue">4.8</span>| Value | Meaning |
|---|---|
| 1 | The exact string itemprop="ratingValue" appears at least once in the script-stripped body HTML. |
| 0 | No such string is found — the attribute is absent, uses single quotes, or has extra spacing around the equals sign. |
How to optimize it
Use ratingValue only as part of an authentic rating within the stated best and worst rating scale, and keep the value aligned with the rating shown to visitors and with the vocabulary expected by its parent item type. Because RankGear matches the literal double-quoted attribute, write it as itemprop="ratingValue" with no added spacing if you want the detector to see it. Treat this factor as an observation of markup presence, not a target to chase: adding the attribute where no genuine rating exists misrepresents your content and does not create a real rating signal.
Important considerations
- The detector pattern-matches HTML text instead of parsing or validating a Microdata item graph, so it confirms only that the attribute string is present.
- 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 cannot tell you whether the rating markup is correct or rich-result eligible.
- Correlation is not causation: the presence of this attribute relates to how pages are prioritized within a measured result set and does not by itself guarantee or cause a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.