Has JSON-LD Review reports whether RankGear finds an @type value of Review in a page’s raw HTML source. It returns 1 when that marker is present and 0 when it is not — and because it pattern-matches source text rather than parsing a graph, a 1 confirms the string exists, not that the surrounding structured data is valid.
| Factor ID | RG-SCJ-229 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value for Review in the raw source of the page. It is a presence check for the Review schema type, expressed as a simple yes/no reading of the delivered HTML.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration with flexible whitespace around "@type": "Review", optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Review"
}
</script>
// also matches, case-insensitive, with a schema: prefix:
"@type": "schema:review"| Value | Meaning |
|---|---|
| 1 | A Review value for @type was found in the raw HTML. |
| 0 | No matching Review type marker was found in the raw HTML. |
How to optimize it
Use Review only for a genuine review, with an accurate item reviewed, author, date, review text, rating, and publisher, and back every property with supporting content users can see on the page. Ensure each property reflects information a reader can verify — the goal is honest, complete markup, not merely a string the detector can match. Treat the reading as a presence observation, not a target to game with an unsupported marker.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms the marker is present but not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — for example in a comment or an unrelated script — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor is not a substitute for that check.
- This is a prioritization signal that relates to position within a measured result set, not a guarantee — correlation is not causation, and the presence of Review markup does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.