Has JSON-LD Game reports whether RankGear finds a JSON-LD @type of Game in a page’s raw source. It returns 1 when the pattern is present and 0 when it is not — but it text-matches the source string rather than validating a JSON-LD graph, so a 1 is not proof of correct structured data.
| Factor ID | RG-SCJ-092 |
|---|---|
| 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 Game in the raw source of the page. It is a simple presence signal: either the Game type is declared in the markup or it is not. It describes what the page announces about itself, not whether that declaration is valid or accurate.
How RankGear measures it
RankGear searches the raw HTML for the "@type": "Game" declaration, allowing flexible whitespace around the colon and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result. Because it works against source text rather than a parsed graph, a matching string that sits outside valid JSON-LD can still return 1.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Game",
"name": "...",
"author": { "@type": "Organization", "name": "..." }
}
</script>| Value | Meaning |
|---|---|
| 1 | The Game @type string is present in the raw source (whitespace-flexible, optional schema: prefix, case-insensitive). |
| 0 | No matching Game @type string was found in the raw source. |
How to optimize it
Use the Game type only for a page about a genuine game, with an accurate name, creator, platform, genre, and access or offer information, and only where those properties match the content a visitor actually sees. Treat this factor as an observation about your markup rather than a target to force: adding the string to satisfy the detector without a real game behind it does not represent your page honestly. Presence relates to how well-marked-up game pages tend to look; it does not by itself move a page’s position.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph.
- A matching string that appears outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently, with a schema validator, rather than relying on this presence check.
- Correlation is not causation: this factor tracks whether the markup is present within a measured result set and is a prioritization signal, not a guarantee that declaring
Gamewill change a page’s ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.