This factor reports whether a page’s raw HTML contains a JSON-LD @type of Physician. It returns a simple present-or-absent signal (1 or 0) — a text-pattern check on source, not a full validation that the structured data is well-formed or accurate.
| Factor ID | RG-SCJ-202 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
RankGear reports whether it finds an @type value of Physician in the raw source of the page. This is the Schema.org type used to describe an individual physician or medical practice, typically embedded as JSON-LD structured data. The factor answers one narrow question: is that type declared in the markup, yes or no.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Physician", allowing flexible whitespace around the colon and an optional schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. If the pattern appears anywhere in the source, the factor is 1; otherwise it is 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Physician",
"name": "Dr. Jane Okafor",
"medicalSpecialty": "Cardiology"
}
</script>| Value | Meaning |
|---|---|
| 1 | A Physician type string was found in the raw HTML. |
| 0 | No Physician type string was found. |
How to optimize it
Use the Physician type only for a genuine physician or medical practice, and describe it accurately: specialties, credentials, affiliations, location, hours, and contact information. Ensure every property reflects content a user can actually verify on the page. Treat this factor as an observation of what your markup declares, not a target to chase — adding the type is only worthwhile when the page really represents a physician.
Important considerations
- The detector pattern-matches source text rather than 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 — in a comment, an example, or plain body text — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated tool before relying on it.
- Presence of this type correlates with, and does not cause, position within a measured result set; it is a prioritization signal, not a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.