This factor reports whether RankGear finds a JSON-LD @type value of Geriatric in a page’s raw source. It returns 1 when the string is present and 0 when it is not. Because the check matches source text rather than validating a structured-data graph, a match confirms the string exists—not that the markup is valid or applies to the page.
| Factor ID | RG-SCJ-095 |
|---|---|
| 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 Geriatric in the raw source. Geriatric is a Schema.org medical-specialty value used to characterize a healthcare entity that focuses on the care of older adults. The result is a simple presence signal: the string was found (1) or it was not (0).
How RankGear measures it
RankGear searches the raw HTML for "@type": "Geriatric", allowing flexible whitespace around the colon and an optional schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection.
What RankGear looks for
"@type": "Geriatric"
"@type": "schema:Geriatric" (schema: prefix allowed)
Example in context:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Geriatric"
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of Geriatric (optionally schema:-prefixed) was found in the raw source. |
| 0 | No such string was found. |
How to optimize it
Use Geriatric only for the Geriatric medical-specialty value, and only where it accurately characterizes the marked healthcare entity, with properties that match the visible content. Do not add the type to a page that is not genuinely about geriatric care in order to trip the signal—this factor is best read as an observation of what a page already declares, not a target to chase. A page with no geriatric-specialty content should legitimately return 0.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid.
- A matching string that sits outside valid JSON-LD—in a comment, a code sample, or unrelated markup—can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to patterns within a measured result set. It does not, on its own, cause or guarantee a ranking—correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.