Has JSON-LD Otolaryngologic is a yes/no check: RankGear returns 1 when a page’s raw HTML contains an @type of Otolaryngologic — the schema.org subtype for an ear, nose, and throat medical practice — and 0 when it does not. It is a text pattern match on the source, not a validation of the surrounding JSON-LD graph, so a stray matching string can still register as present.
| Factor ID | RG-SCJ-192 |
|---|---|
| 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 Otolaryngologic in the page’s raw source. It is a single presence signal for the ear, nose, and throat medical-business schema type — it says the type string is there, not that the structured data around it is complete or valid.
How RankGear measures it
RankGear scans the raw HTML for "@type": "Otolaryngologic", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not change the result. Any single match sets the value to 1; no match leaves it at 0.
What RankGear looks for
"@type": "Otolaryngologic"
"@type":"schema:Otolaryngologic" (whitespace-flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | The Otolaryngologic @type string was found in the raw HTML. |
| 0 | No matching @type string was found in the raw HTML. |
How to optimize it
Use Otolaryngologic only for a genuine ear, nose, and throat medical service, with accurate practitioners, credentials, services, location, and contact details. Every property should reflect content a user can verify on the page. Because the detector only confirms the type string is present, treat a 1 as a starting point rather than proof of correct markup — the value being set does not mean the JSON-LD is well-formed or complete.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 is not a guarantee of valid structured data.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a correlation-based prioritization signal within a measured result set — its presence relates to position among compared pages and does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.