This factor reports whether RankGear finds a JSON-LD @type of ReviewNewsArticle in a page’s raw source. It returns 1 when the string is present and 0 when it is not. Because the check pattern-matches source text rather than parsing a JSON-LD graph, a match confirms the markup string exists — not that the structured data is valid.
| Factor ID | RG-SCJ-230 |
|---|---|
| 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 of ReviewNewsArticle in the page’s raw source. ReviewNewsArticle is the schema.org type for a news-style article whose primary purpose is to review a subject — a film, product, event, or similar — combining editorial reporting with a critic’s assessment. The factor is a simple binary observation: the string is either found (1) or not found (0).
How RankGear measures it
RankGear searches the raw HTML for "@type": "ReviewNewsArticle", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. The check operates on source text and does not parse or validate the surrounding JSON-LD graph.
What RankGear looks for
"@type": "ReviewNewsArticle"
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ReviewNewsArticle",
"headline": "...",
"itemReviewed": { "@type": "Movie", "name": "..." },
"reviewRating": { "@type": "Rating", "ratingValue": "4" }
}
</script>| Value | Meaning |
|---|---|
| 1 | The ReviewNewsArticle type string was found in the raw HTML. |
| 0 | The string was not found in the raw HTML. |
How to optimize it
Use ReviewNewsArticle only for a genuine news-style review article — one with an accurate subject, critic, publisher, dates, rating, and article body. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of markup presence, not a target to hit for its own sake: adding the type string to a page that is not genuinely a news review misrepresents the content and helps no one. If the page truly is a news review, the correct type belongs there regardless of this signal.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a returned 1 confirms only that the string exists.
- A matching string that appears outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor is not a substitute for that.
- This is a correlation-based observation within a measured result set. Presence of the markup relates to how pages are prioritized; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.