This factor reports whether RankGear finds an AggregateOffer @type value in the raw page source, returned as a simple 1 (present) or 0 (absent). It is a 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-007 |
|---|---|
| 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 AggregateOffer in the raw source. AggregateOffer is the JSON-LD type used to describe a collection of offers for a single product — typically the lowest and highest price, the number of offers, the currency, and availability. The factor is a single yes/no observation: it tells you the type string was detected, nothing more about its accuracy or completeness.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "AggregateOffer" with flexible whitespace around the colon, optionally allowing a schema: prefix. The detector is case-sensitive and returns 1 on any match. Because it pattern-matches the raw source rather than parsing the document, the capitalization must match the implementation exactly.
What RankGear looks for
"@type": "AggregateOffer"
"@type":"AggregateOffer"
"@type": "schema:AggregateOffer"| Value | Meaning |
|---|---|
| 1 | An AggregateOffer @type string was found in the raw HTML. |
| 0 | No matching string was found, or its capitalization did not match exactly. |
How to optimize it
Use AggregateOffer only for a real collection of offers, and populate it with accurate low, high, count, currency, and availability data. Treat the 1/0 as an observation of what is in your source, not a target to chase: adding the string without genuine offer data 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
- RankGear pattern-matches the raw source; it does not parse or validate the JSON-LD graph.
- A matching string that sits outside a valid JSON-LD script can still produce a 1.
- Capitalization must match the implementation exactly, or the detector returns 0.
- The type and all its properties should accurately reflect the content visible on the page.
- 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.