This factor reports whether RankGear finds a "@type": "DiagnosticLab" value in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — a text match on the source, not a validation that the surrounding JSON-LD graph is complete or correct.
| Factor ID | RG-SCJ-072 |
|---|---|
| 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 DiagnosticLab in the raw source. DiagnosticLab is the schema.org type used to describe a diagnostic laboratory — a facility that runs medical tests — and pages that describe such a lab may declare it in their structured data so search engines can classify the entity. RankGear records a single yes/no observation: the type string is either present in the source or it is not.
How RankGear measures it
RankGear searches the raw HTML for the pattern "@type": "DiagnosticLab", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "DiagnosticLab"
"@type":"schema:DiagnosticLab" (optional schema: prefix, flexible whitespace, case-insensitive)| Value | Meaning |
|---|---|
| 1 | The DiagnosticLab type string was found in the raw HTML source. |
| 0 | No DiagnosticLab type string was found in the raw HTML source. |
How to optimize it
Use DiagnosticLab only for a page that represents a real diagnostic laboratory, and only when the structured data accurately reflects the facility’s services, location, hours, contact details, and appointment information. The declared properties should match the content a visitor actually sees on the page. Treat this factor as a description of your markup rather than a target to chase: adding the type string to a page that is not a diagnostic lab misrepresents the entity and does nothing useful.
Important considerations
- The detector pattern-matches source text rather than parsing and validating a JSON-LD graph, so it confirms the string is present, not that the structured data is valid.
- A matching string that sits outside valid JSON-LD — for example inside a comment, a code sample, or a script that never renders as structured data — can still return 1.
- Capitalization differences do not affect detection, because matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor alone does not tell you whether the markup is well-formed.
- This is an observed signal that relates to how a page is described within a measured result set. It is not a guarantee of ranking, and its presence does not by itself cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.