This factor reports whether RankGear finds a ProductModel @type value in the raw page source, returned as a simple 1 (present) or 0 (absent). It is a case-insensitive string match on raw HTML, not a validation of the JSON-LD graph, so a match only confirms the text appears — not that the markup is correct or that it will influence position.
| Factor ID | RG-SCJ-211 |
|---|---|
| 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 ProductModel in the raw source. ProductModel is the JSON-LD type used to describe a specific model of a product — the version that carries a manufacturer, a model number, technical specifications, variants, identifiers, and links to related products. The factor is a single yes/no observation: it confirms the type string was detected, and nothing more about its accuracy or completeness.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "ProductModel" with flexible whitespace around the colon, optionally allowing a schema: prefix. Matching is case-insensitive, so differences in capitalization do not affect detection, and the detector returns 1 on any match. Because it pattern-matches the raw source rather than parsing the document, a match confirms only that the string is present in the page text.
What RankGear looks for
"@type": "ProductModel"
"@type":"ProductModel"
"@type": "schema:ProductModel"| Value | Meaning |
|---|---|
| 1 | A ProductModel @type string was found in the raw HTML (any capitalization). |
| 0 | No matching string was found in the raw source. |
How to optimize it
Use ProductModel only for a genuine product model, and populate it with an accurate manufacturer, model number, specifications, variants, identifiers, and related products. Ensure every property reflects content users can verify on the page. Treat the 1/0 as an observation of what is in your source, not a target to chase: adding the string without a real product model behind it does not improve the underlying page, and RankGear does not check that the data is valid — only that the type string is present.
Important considerations
- The detector pattern-matches source text; it does not parse or validate the JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection — matching is case-insensitive.
- Validate the complete structured data independently before relying on it.
- Presence of this markup correlates with, and does not cause, ranking position — it is a prioritization signal RankGear observes within a measured result set, not a guarantee of where a page ranks.
Related factors
Part of the Factors reference · how RankGear measures · glossary.