This factor reports whether RankGear finds a MedicalClinic @type value in a page’s raw HTML — a simple 1 (present) or 0 (absent). It is a text pattern match, not a validation that the JSON-LD graph is well-formed, so a 1 confirms the string is present, not that the schema is correct.
| Factor ID | RG-SCJ-143 |
|---|---|
| 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 MedicalClinic in the page’s raw source. It is a presence check for one specific schema type used to describe a medical clinic — the type that carries a clinic’s specialties, services, practitioners, location, hours, and contact details in machine-readable form.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "MedicalClinic", allowing flexible whitespace around it and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MedicalClinic",
"name": "Riverside Family Health",
"medicalSpecialty": "PrimaryCare"
}
</script>| Value | Meaning |
|---|---|
| 1 | A MedicalClinic @type string was found in the raw HTML. |
| 0 | No MedicalClinic @type string was found. |
How to optimize it
Use MedicalClinic only for a page that genuinely represents a medical clinic, and make every property accurate — specialties, services, practitioners, location, hours, and contact information. Ensure each value reflects content a user can verify on the page itself. Because this factor only checks for the type string, treat a 1 as confirmation that the markup is present, not as proof it is complete or valid; the goal is honest, accurate structured data, not merely satisfying the detector.
Important considerations
- The detector pattern-matches source text rather than validating a full JSON-LD graph.
- 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 schema validator — rather than relying on this presence check.
- This is a prioritization signal that relates to position within a measured result set; it does not on its own cause a page to rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.