This factor reports whether RankGear finds a JSON-LD @type of PublicHealth in a page’s raw source. It returns a simple yes/no signal (1 or 0), and it pattern-matches the source text rather than validating the underlying structured-data graph, so a match is evidence of the markup being present, not proof that it is well-formed.
| Factor ID | RG-SCJ-216 |
|---|---|
| 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 PublicHealth in the raw source of the page. It is a presence check for a specific schema.org type, not a measure of how completely or correctly that type is described.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "PublicHealth", allowing flexible whitespace around the colon and optionally permitting a schema: prefix. Matching is case-insensitive, so differences in capitalization do not affect the result.
What RankGear looks for
"@type": "PublicHealth"
"@type" : "schema:PublicHealth"
"@TYPE":"publichealth"| Value | Meaning |
|---|---|
| 1 | A @type of PublicHealth was found in the raw source. |
| 0 | No matching PublicHealth type string was found. |
How to optimize it
Use PublicHealth only for a genuine public-health service, and make sure the surrounding markup carries an accurate provider, programs, eligibility, service area, location, and contact information. Every property should reflect content a user can verify on the page. Because the detector only checks for the type string, treat a positive result as confirmation the markup exists rather than as a target to game — adding the string without real, matching content offers no benefit and risks misrepresenting the page.
Important considerations
- The detector pattern-matches source text instead of validating a full JSON-LD graph, so a positive result does not confirm the structured data is valid.
- A matching string that appears outside of valid JSON-LD — in a comment, a code sample, or unrelated text — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema tester.
- This is a correlation-based prioritization signal observed within a measured result set; its presence relates to position but does not by itself cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.