Has Schema Rating reports whether the page’s body HTML contains the legacy Schema.org Rating type URI — specifically the literal http://schema.org/Rating. It returns 1 when that exact string is present and 0 when it is not. This is a string-level detection of one legacy form; it does not read the rating value or confirm the markup is complete or correct.
| Factor ID | RG-SCH-020 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
Has Schema Rating detects the legacy Schema.org Rating type URI in the page body. A Rating represents an evaluation of an item on a defined scale — a value paired with the scale it is measured against. This factor observes whether the older type-URI form of that markup appears in the rendered body HTML. It does not read the rating value, check the scale, or judge whether the markup is well-formed.
How RankGear measures it
RankGear performs a case-insensitive search of the body HTML, with scripts excluded, for the literal string http://schema.org/Rating. If that URI is found, the factor returns 1; otherwise it returns 0. Only this legacy http:// type-URI form is recognized. The https://schema.org/Rating variant and a bare JSON-LD @type value such as "@type": "Rating" do not satisfy this detector — they are different string forms and fall outside this specific pattern.
What RankGear looks for
<div itemscope itemtype="http://schema.org/Rating">
<span itemprop="ratingValue">4</span>
<span itemprop="bestRating">5</span>
</div>| Value | Meaning |
|---|---|
| 1 | The literal http://schema.org/Rating URI was found in the body HTML (scripts excluded). |
| 0 | The legacy URI was not found. An https:// URI or a JSON-LD @type declaration does not count here. |
How to optimize it
Use Rating only for an authentic rating, with an accurate value and scale tied to the item being rated. Mark up a rating where a genuine evaluation exists, and keep the value and scale consistent with what the page actually shows. Note that this factor recognizes only the legacy http:// type-URI form; modern implementations commonly use the https:// URI or JSON-LD, which are the right choice for most sites today and are measured by their own factors. Read this factor as an observation of whether that specific legacy form is present — not as a target to retrofit onto pages that have no genuine rating.
Important considerations
https://schema.org/Ratingand a bare JSON-LD"@type": "Rating"do not satisfy this detector; it matches only the legacyhttp://form.- Presence is not validation — finding the string does not confirm the required or recommended properties are present or correct.
- Structured data must match the visible, truthful content on the page.
- Validate the complete markup with current platform tools before relying on it.
- This factor relates to position within a measured result set — it is a prioritization signal, not a cause of ranking, and adding it does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.