RankGear’s Has JSON-LD Person factor reports whether a Person structured-data type appears in the page’s raw HTML: it returns 1 when the tool finds a "@type": "Person" string and 0 when it does not. Because it pattern-matches source text rather than validating the JSON-LD graph, a 1 confirms the string is present — not that the markup is valid.
| Factor ID | RG-SCJ-199 |
|---|---|
| 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 Person in the page’s raw source. It is a presence check for the Person entity in JSON-LD structured data, expressed as a simple yes/no signal for the measured page.
How RankGear measures it
RankGear searches the raw HTML for a "@type": "Person" string, allowing flexible whitespace around the colon and value and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not change the result. If a match is found the factor is 1; otherwise it is 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Doe"
}
</script>
<!-- also matches the prefixed form -->
"@type": "schema:Person"| Value | Meaning |
|---|---|
| 1 | A "@type": "Person" string was found in the raw HTML (prefix and case variations included). |
| 0 | No matching Person type string was found in the raw HTML. |
How to optimize it
Use Person only for a real person, with an accurate name, role, affiliations, credentials, image, contact points, and authoritative profile links. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of whether the markup is present — not a target to hit by inserting the string where no genuine Person entity exists.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 means the string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated markup — can still produce a 1.
- Capitalization differences do not affect detection, and a
schema:prefix is accepted. - Validate the complete structured data independently with a schema validator; this factor does not confirm correctness.
- Correlation is not causation: this signal relates to position within a measured result set and helps prioritize work — it does not on its own make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.