Has JSON-LD Hospital

Abstract illustration of a hospital wrapped in a JSON-LD schema tag, in RankGear indigo and coral.

Has JSON-LD Hospital reports whether the raw HTML of a page contains a JSON-LD @type of Hospital, returning 1 when that string is present and 0 when it is not. It is a text pattern match on source, not a validation of the structured-data graph, so a match can appear even outside valid JSON-LD.

Factor IDRG-SCJ-107
FamilyStructured Data – JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of Hospital in the raw source of the page. It is a binary observation of a single structured-data type declaration: the value is 1 when the pattern is found anywhere in the rendered HTML, and 0 when it is absent. It says nothing about whether the surrounding JSON-LD is well formed or complete.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "Hospital", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. Because the match runs against source text rather than a parsed graph, the same string appearing outside valid JSON-LD still returns 1.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Hospital",
  "name": "Riverside General Hospital",
  "department": ["Emergency", "Cardiology"]
}
</script>
ValueMeaning
1A Hospital @type string (optionally schema:Hospital) was found in the raw HTML, in any letter case.
0No such string was found in the source.
Back to Top

How to optimize it

Use the Hospital type only for a page that genuinely represents a hospital, and describe it accurately: real departments, services, location, contact details, and emergency information, with every property matching the content a visitor can see. Treat this factor as an observation that the declaration is present, not a target to chase – declaring the type without truthful, matching data adds no real structured-data value and risks a mismatch between markup and page.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph.
  • A matching string that sits outside valid JSON-LD can still produce a value of 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently rather than relying on this presence check.
  • 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.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top