Has MicroData Offers

Has MicroData Offers is a yes/no signal that reports whether RankGear finds the Microdata attribute itemprop="offers" in a page’s rendered body HTML after scripts are stripped. It confirms the presence of the literal markup string only — it does not parse, validate, or judge the surrounding Microdata item.

Factor IDRG-SCM-029
FamilyStructured Data — Microdata
MeasurementBinary presence (0 / 1)
Measured zoneRendered body HTML with scripts removed

What it measures

This factor reports whether the Microdata attribute itemprop="offers" appears in the page’s rendered body once script elements have been removed. In Microdata vocabularies such as Schema.org, the offers property attaches offer details — price, availability, and similar terms — to a marked-up product, service, event, or other eligible entity. The factor is a presence check on that attribute, not an assessment of the offer data itself.

How RankGear measures it

RankGear performs a case-insensitive search for the literal double-quoted form itemprop="offers" within the rendered body after scripts are removed. It returns 1 when at least one match exists and 0 otherwise.

What RankGear looks for

<div itemprop="offers" itemscope itemtype="https://schema.org/Offer">
  <span itemprop="price">49.00</span>
  <link itemprop="availability" href="https://schema.org/InStock">
</div>
ValueMeaning
1The exact string itemprop="offers" was found at least once in the script-free body.
0No match — the attribute is absent, or written with single quotes or extra spacing that the pattern does not accept.

How to optimize it

Use offers only as part of genuine, current offer information tied to the marked-up product, service, event, or other eligible entity. Keep the value aligned with visible content and with the vocabulary expected by its parent item type. Because the detector matches a contiguous double-quoted string, write the attribute in that exact form — itemprop="offers" — rather than with single quotes or added spacing. Treat this factor as an observation of markup presence, not a target to chase: adding the attribute where no real offer exists helps neither the signal nor the page.

Important considerations

  • The detector pattern-matches HTML text rather than 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.
  • Correlation is not causation. This factor relates to position within a measured result set as a prioritization signal; it does not make a page rank or guarantee a ranking.

Related factors

Part of the Factors reference · how RankGear measures · glossary.