This factor reports whether RankGear finds an @type of Obstetric in the page’s raw HTML — a simple 1 (present) or 0 (absent). It is a text match on the source, not a validated JSON-LD graph, so a match confirms the string exists, not that the structured data is well-formed.
| Factor ID | RG-SCJ-181 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor records whether an @type value of Obstetric appears in the page’s raw source. Obstetric is the schema.org type used to mark up an obstetric medical service, so its presence indicates the page declares itself as offering that kind of care. The factor returns 1 when the type is found and 0 when it is not — a straightforward presence signal within the measured result set, not a judgment of markup quality.
How RankGear measures it
RankGear scans the raw HTML for the "@type": "Obstetric" declaration, 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. Because the check works on source text rather than a parsed JSON-LD graph, it confirms the string is present without inspecting the surrounding structure.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Obstetric",
"name": "Riverside Obstetric Care"
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of Obstetric was found in the raw source (any casing, optional schema: prefix). |
| 0 | No matching Obstetric type string was found. |
How to optimize it
Use the Obstetric type only for a genuine obstetric medical service, and make sure the markup carries accurate practitioners, credentials, services, location, and contact details. Every property should reflect content a visitor can verify on the page itself. Because this factor only detects the type string, treat a 1 as evidence the declaration exists, not as proof the structured data is complete or correct — validate the full JSON-LD separately.
Important considerations
- The detector pattern-matches source text; it does not validate a 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 before relying on it.
- Presence of this type relates to 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.