This factor reports whether RankGear finds an @type of Collection in a page’s raw HTML, returning 1 when the string is present and 0 when it is not. It is a text match, not a validation of the structured-data graph, so a match can appear even where the JSON-LD is malformed.
| Factor ID | RG-SCJ-052 |
|---|---|
| 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 Collection in the raw source of the page. It is a binary presence signal: the tool is asking only whether the markup declaring a Collection item type is there, not whether that markup is complete, valid, or accurately describes the page.
How RankGear measures it
RankGear performs a case-insensitive raw-HTML search with flexible whitespace around "@type": "Collection" and permits an optional schema: prefix. Capitalization differences do not affect detection. Because the check is a pattern match over text rather than a parse of the JSON-LD graph, any matching string in the source can satisfy it.
What RankGear looks for
"@type": "Collection"
"@type":"schema:Collection" (optional schema: prefix, flexible whitespace, case-insensitive)| Value | Meaning |
|---|---|
| 1 | A Collection @type string was found in the raw HTML. |
| 0 | No matching Collection @type string was found. |
How to optimize it
Use Collection only for a page that is genuinely a collection, with an accurate name, creator, contents, and the relationships between them. Supply properties that match the visible content of the page rather than adding the type to earn the signal. Because RankGear matches text rather than validating the graph, a passing 1 is not evidence that the markup is correct; treat it as a presence observation and confirm the structured data with an independent validator.
Important considerations
- RankGear pattern-matches text rather than parsing or validating the 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 before relying on it.
- This is a prioritization signal that relates to position within a measured result set; presence of the markup correlates with, but does not cause or guarantee, a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.