This factor reports whether RankGear finds the Microdata attribute itemprop="offerCount" anywhere in the rendered body HTML after scripts are stripped out. It returns 1 when at least one match is present and 0 when none is found — a presence signal, not a validation of whether the offer count is correct or eligible for rich results.
| Factor ID | RG-SCM-028 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether RankGear finds the Microdata attribute itemprop="offerCount" in the rendered body after script elements are removed. In Microdata vocabulary, offerCount belongs to an aggregate offer and states how many individual offers a listing represents. This check tells you only that the property is present in the markup — it does not read or verify the number attached to it.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="offerCount". It returns 1 when at least one match exists and 0 otherwise. The match is a plain text search: the attribute name, equals sign, double quotes, and property value must be contiguous, so single quotes or added spacing will not match.
What RankGear looks for
<div itemscope itemtype="https://schema.org/AggregateOffer">
<span itemprop="offerCount">24</span> offers
<span itemprop="lowPrice">19.99</span>
<meta itemprop="priceCurrency" content="USD">
</div>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="offerCount" appears at least once in the rendered body after scripts are removed. |
| 0 | No contiguous, double-quoted match is present — the attribute is absent, uses single quotes, or has extra spacing. |
How to optimize it
Use offerCount only as part of the accurate number of offers represented by an aggregate offer. Keep the value aligned with visible content and with the vocabulary expected by its parent item type. Treat this factor as an observation of whether the property exists in your markup, not a target to chase — adding the attribute where no aggregate offer genuinely exists misrepresents the page and adds no legitimate signal.
Important considerations
- The detector pattern-matches HTML text instead of parsing or validating a Microdata item graph.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing do not match.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently — presence of the attribute does not confirm valid or eligible markup.
- This is a correlation-based prioritization signal within a measured result set; presence of the property does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.