Has Schema Image Object

RG-SCH-009 checks whether a page’s body HTML contains the legacy http://schema.org/ImageObject type URI. It returns a binary present/absent (1 / 0) signal — confirming the string appears, not that the ImageObject markup is valid or that its images resolve.

Factor IDRG-SCH-009
FamilySchema.org
MeasurementBinary presence (0 / 1)
Measured zoneBody HTML without scripts

What it measures

This factor detects the legacy Schema.org ImageObject type URI within a page’s body HTML. ImageObject is the Schema.org type used to describe a meaningful image as a first-class entity — its URL, dimensions, caption, and licensing — rather than leaving it as an undescribed img element. RankGear records only whether the type reference is present; it is a presence observation, not a quality or validity check.

How RankGear measures it

RankGear searches the page’s body HTML (with script contents excluded) case-insensitively for the exact string http://schema.org/ImageObject. If that string is found, the factor is 1; if it is not found, the factor is 0. No parsing of the surrounding markup, properties, or image files is performed.

What RankGear looks for

<div itemscope itemtype="http://schema.org/ImageObject">
  <img itemprop="contentUrl" src="/hero.jpg" alt="...">
  <meta itemprop="width" content="1200">
</div>
ValueMeaning
1The string http://schema.org/ImageObject appears in the body HTML.
0The string is absent — including pages that use the HTTPS URI or a bare @type value.

How to optimize it

Where you use ImageObject, reserve it for meaningful images and give it accurate values — the image URL, dimensions, caption, and licensing where applicable. Treat this factor as an observation of one specific legacy string rather than a target to chase: because RankGear matches only the http://schema.org/ImageObject form, a page using the modern HTTPS URI or a bare @type in JSON-LD can be fully valid yet still read as 0. Fix your markup for correctness first, and let this factor report what it finds.

Important considerations

  • The HTTPS variant (https://schema.org/ImageObject) and bare @type formats are missed — only the http:// URI is matched.
  • JSON-LD placed inside <script> tags falls outside the measured zone (body HTML without scripts), so schema declared there is not counted.
  • Image availability is not tested — the factor never fetches the referenced files.
  • Presence does not validate properties; a matching string says nothing about whether the ImageObject is complete or correct.
  • Avoid marking decorative assets unnecessarily.
  • This is a correlation-based prioritization signal that tracks how a value relates to position within a measured result set. It does not cause or guarantee a ranking.

Related factors

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