Has JSON-LD IndividualProduct is a binary check that returns 1 when RankGear finds an @type of IndividualProduct in a page’s raw HTML, and 0 when it does not. It is a text pattern match on source, not a validation of your structured-data graph — a matching string can register even when it sits outside valid JSON-LD.
| Factor ID | RG-SCJ-123 |
|---|---|
| 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 IndividualProduct in the page’s raw source. IndividualProduct is the schema.org type used for a specific, individually identifiable product — a single unit with its own identifiers rather than a generic product model. The factor records only presence within a measured result set; it is a prioritization signal, not something that drives a page’s position.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "IndividualProduct" with flexible whitespace around the colon and value, and it optionally allows a schema: prefix (schema:IndividualProduct). Matching is case-insensitive, so capitalization differences do not affect the result.
What RankGear looks for
"@type": "IndividualProduct"
"@type":"schema:IndividualProduct" (optional prefix, flexible whitespace, case-insensitive)| Value | Meaning |
|---|---|
| 1 | An IndividualProduct @type string was found in the raw HTML. |
| 0 | No IndividualProduct @type string was present in the source. |
How to optimize it
Use IndividualProduct only for a specific, individually identifiable product with accurate identifiers, condition, offer details, and other properties the page genuinely supports. Ensure every property reflects content a user can verify on the page. Treat this factor as an observation of what your markup declares, not a target to force — adding the type where the page is not an individual product misrepresents your content and helps no one.
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.
- Validate the complete structured data independently with a schema validator — presence of the string is not proof of a well-formed graph.
- Correlation is not causation: this factor tracks whether the markup is present across a measured result set; it does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.