Has Schema Review checks whether a page’s visible HTML carries the legacy Schema.org Review type URI, http://schema.org/Review, returning 1 when that exact string is present and 0 when it is not. It scans the rendered body markup with scripts removed, so a review expressed only as a bare JSON-LD "@type": "Review" or with the modern https:// URI can read as absent even when the page is, in fact, marked up.
| Factor ID | RG-SCH-021 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
This factor detects the legacy Schema.org Review type URI within a page. It is a single presence check: either the identifier for the Review type appears in the measured markup or it does not. It does not grade the completeness or correctness of the structured data — only that the classic type reference is there to be found.
How RankGear measures it
RankGear takes the page’s body HTML with script blocks stripped out and performs a case-insensitive search for the literal string http://schema.org/Review. A match sets the factor to 1; no match sets it to 0. Because scripts are excluded from the measured zone, the type has to surface in the rendered body markup — for example as a microdata itemtype attribute — to be counted.
What RankGear looks for
<div itemscope itemtype="http://schema.org/Review">
<span itemprop="author">…</span>
<span itemprop="itemReviewed">…</span>
<span itemprop="reviewRating">…</span>
</div>| Value | Meaning |
|---|---|
| 1 | The string http://schema.org/Review was found in the body HTML (scripts excluded). |
| 0 | The string was not found — the page may use the https:// URI, a bare JSON-LD "@type": "Review", or no Review markup at all. |
How to optimize it
Use the Review type only for genuine, visible review content, with accurate author, reviewed item, and rating details. Treat the factor as an observation about which legacy identifier a page happens to expose rather than a target to chase: matching the exact http://schema.org/Review string is not itself the goal, and a page that uses the modern https:// URI or a valid JSON-LD equivalent can be correctly marked up while still registering 0 here.
Important considerations
- The modern
https://schema.org/ReviewURI and a bare JSON-LD"@type": "Review"do not satisfy this detector — both can return 0 even when the page carries valid Review structured data. - Presence does not validate required or recommended properties — the factor confirms the type reference is present, not that author, item reviewed, or rating are supplied.
- Structured data must match visible, truthful content; the review markup should describe the actual review the reader sees.
- Validate the complete markup with current platform tools rather than relying on this single presence check.
- This is a prioritization signal correlated with position within a measured result set — presence of the type is not a cause of ranking and does not guarantee one.
Related factors
Part of the Factors reference · how RankGear measures · glossary.