Has Schema Aggregate Rating reports whether the page’s body HTML contains the legacy Schema.org AggregateRating type URI — specifically the literal http://schema.org/AggregateRating. 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 validate the markup or confirm the ratings are eligible for any rich result.
| Factor ID | RG-SCH-002 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
Has Schema Aggregate Rating detects a legacy Schema.org AggregateRating type URI in the page body. An AggregateRating represents a summary rating drawn from multiple individual ratings or reviews — for example an average star value and the count of ratings behind it. This factor observes whether the older type-URI form of that markup appears in the rendered body HTML. It does not read the rating values, count the reviews, or judge whether the markup is correct.
How RankGear measures it
RankGear searches the body HTML, with scripts excluded, for the literal string http://schema.org/AggregateRating, matched case-insensitively. 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/… variant and bare JSON-LD @type values such as "@type": "AggregateRating" 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/AggregateRating">
<span itemprop="ratingValue">4.7</span>
<span itemprop="reviewCount">128</span>
</div>| Value | Meaning |
|---|---|
| 1 | The literal http://schema.org/AggregateRating 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
Mark up genuine aggregate ratings with accurate counts and values that match the ratings visible on the page. Only add AggregateRating markup where a real summary rating exists and is shown to users. 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 aggregate rating.
Important considerations
https://schema.org/…URIs and bare JSON-LD@typevalues do not satisfy this detector; it matches only the legacyhttp://form.- Presence is not validation — finding the string does not confirm the markup is well-formed, complete, or correct.
- Ratings must be authentic and reflect real user feedback, not fabricated numbers.
- Follow current rich-result policies; search engines decide eligibility and how, or whether, ratings are displayed.
- 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.