This factor is a yes/no check for whether the page’s raw HTML contains a JSON-LD @type of PeopleAudience. It returns 1 when the string is present and 0 when it is not — but it pattern-matches source text, so it does not confirm the markup sits inside valid JSON-LD.
| Factor ID | RG-SCJ-197 |
|---|---|
| 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 PeopleAudience in the page’s raw source. PeopleAudience is the schema.org type used to describe an intended human audience — the age range, gender, or geography a piece of content is meant for. The check is binary: either the type appears in the markup or it does not.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "PeopleAudience", allowing flexible whitespace around the colon and an optional schema: prefix on the type name. Matching is case-insensitive, so differences in capitalization do not affect the result. Any single match anywhere in the source sets the value to 1.
What RankGear looks for
"@type": "PeopleAudience"
"@type":"schema:PeopleAudience" ← optional schema: prefix, whitespace-tolerant| Value | Meaning |
|---|---|
| 1 | A PeopleAudience type string was found in the raw HTML. |
| 0 | No PeopleAudience type string was found. |
How to optimize it
Add a PeopleAudience type only when the page genuinely targets a defined audience, and describe that audience with accurate age, gender, geography, or other relevant eligibility characteristics. Every property should reflect something users can verify on the page itself. Treat the 0/1 result as an observation of what your markup contains, not a target to chase — adding the type to a page with no real audience distinction adds noise, not signal.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 confirms the string is present, not that the surrounding structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or broken markup — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate your complete structured data independently with a schema validator; this factor does not.
- Presence of this type relates to how pages in a measured result set are structured; it is a prioritization signal, not a guarantee of ranking, and correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.