This factor reports whether RankGear finds a Casino @type value in a page’s raw source. It returns 1 when the pattern is present and 0 when it is absent — but it pattern-matches text, so a match is not proof of valid, well-formed structured data.
| Factor ID | RG-SCJ-046 |
|---|---|
| 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 Casino in the raw source of the page. It is a presence check: the field answers the yes-or-no question of whether the Casino schema type appears in the markup RankGear retrieved, not whether that schema is complete, valid, or correctly scoped.
How RankGear measures it
RankGear performs a case-insensitive raw-HTML search with flexible whitespace around "@type": "Casino" and permits an optional schema: prefix. The search runs against the raw rendered HTML rather than a parsed structured-data graph, so it looks for the literal string wherever it appears in source. Capitalization differences do not affect detection.
What RankGear looks for
"@type": "Casino"
"@type": "schema:Casino"| Value | Meaning |
|---|---|
| 1 | The Casino @type pattern was found in the raw HTML. |
| 0 | The pattern was not found. |
How to optimize it
Use Casino only for a genuine casino, with accurate location, hours, contact, amenities, and visitor information, and supply accurate properties that match the visible content of the page. Treat the 1 as a byproduct of publishing correct structured data for a real entity, not as a target to chase — adding the type to a page that is not a casino, or that lacks the supporting properties, produces a matching string without producing trustworthy structured data.
Important considerations
- RankGear pattern-matches text rather than parsing or validating the JSON-LD graph, so a 1 confirms the string is present, not that the schema is valid.
- A matching string outside valid JSON-LD — for example in a comment, a code sample, or unrelated markup — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently before relying on it.
- Presence of this type correlates with, and does not cause, ranking. It is a prioritization signal within a measured result set, not a guarantee of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.