This factor reports whether a Podiatric @type appears in the page’s structured data. It returns 1 when RankGear finds the type in the raw HTML and 0 when it does not — a presence signal, not a validation of the JSON-LD graph itself.
| Factor ID | RG-SCJ-208 |
|---|---|
| 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 Podiatric in the raw source of the page. It is a single yes/no observation about the presence of that schema type — nothing more. It does not grade the quality, completeness, or accuracy of the structured data, only that the type string is there to be found.
How RankGear measures it
RankGear searches the raw HTML for "@type": "Podiatric", allowing flexible whitespace around the colon and value and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. If a match is found anywhere in the source, the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "Podiatric"
"@type":"schema:Podiatric" (prefix and whitespace variants also match, case-insensitive)| Value | Meaning |
|---|---|
| 1 | A Podiatric @type string was found in the raw HTML. |
| 0 | No matching Podiatric type string was present in the source. |
How to optimize it
Use the Podiatric type only for a genuine podiatric medical service, with accurate practitioners, credentials, treatments, location, and contact information. Ensure every property reflects content that users can verify on the page. Because the detector only confirms the type string is present, treat a 1 as an observation that the markup exists — not as proof the structured data is correct or complete.
Important considerations
- The detector pattern-matches source text rather than validating a full JSON-LD graph, so a 1 confirms presence of the string, not a well-formed schema.
- A matching string that sits outside valid JSON-LD — for example in a comment or a script that never parses — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently with a dedicated schema tool.
- This is a prioritization signal that relates to position within a measured result set; it does not by itself make a page rank, and correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.