Has JSON-LD CommunityHealth

This factor reports whether the page’s raw HTML contains a JSON-LD @type of CommunityHealth. It returns a simple present-or-absent signal (1 or 0) — and because it pattern-matches source text rather than validating a structured-data graph, a match does not by itself prove the markup is valid or that the page will rank.

Factor IDRG-SCJ-055
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 CommunityHealth in the page’s raw source. CommunityHealth is a medical-specialty value in the schema.org vocabulary, so its presence signals that the page has marked up a healthcare entity as belonging to that specialty. The result is binary: the value is either present (1) or it is not (0).

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "CommunityHealth", allowing flexible whitespace around the punctuation and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. No JSON-LD graph is parsed or validated — the detector looks only for the pattern in the source text.

What RankGear looks for

"@type": "CommunityHealth"
"@type":"schema:CommunityHealth"
ValueMeaning
1A @type of CommunityHealth was found in the raw HTML.
0No such @type value was found in the raw HTML.

How to optimize it

Use CommunityHealth only where it accurately characterizes the healthcare entity you are marking up, and only for the CommunityHealth medical-specialty value — with properties that match the visible content on the page. Because the detector matches source text and not a validated graph, treat a positive result as confirmation that the string is present, not as proof that the structured data is correct. Do not add the value where it does not genuinely describe the entity.

Important considerations

  • The detector pattern-matches source text rather than validating a JSON-LD graph.
  • A matching string that sits outside valid JSON-LD can still produce a 1.
  • Capitalization differences do not affect detection, since matching is case-insensitive.
  • Validate the complete structured data independently — this factor confirms presence, not correctness.
  • This is a prioritization signal that relates to position within a measured result set; it is correlation, not causation, and does not guarantee a ranking.

Related factors

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