Has Schema Product

Abstract illustration of a product schema tag matching a single legacy http namespace URI, in RankGear indigo and coral.

Has Schema Product checks whether a page’s body HTML contains the legacy Schema.org Product type URI written as http://schema.org/Product, returning 1 when that exact string is present and 0 when it is not. It is a narrow literal match: the modern https:// form and a bare JSON-LD "@type": "Product" do not satisfy this detector.

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

What it measures

This factor detects the legacy Schema.org Product type URI on the page. It is a presence signal for the older http:// form of the vocabulary namespace, typically emitted by microdata that types a region of the page as a product. It reports only whether that specific URI appears, not whether the surrounding markup is complete or valid.

Back to Top

How RankGear measures it

RankGear performs a case-insensitive search of the page’s body HTML (with scripts excluded) for the literal string http://schema.org/Product and returns 1 when it is found, 0 otherwise. There is no normalization of the scheme or trailing path, so only this exact URI counts.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/Product">
  <span itemprop="name">...</span>
  <span itemprop="brand">...</span>
</div>
ValueMeaning
1The literal http://schema.org/Product URI appears in the body HTML.
0The URI is absent — including pages that use the https:// form or JSON-LD only.
Back to Top

How to optimize it

Use Product structured data for a genuine product, with an accurate name, brand, offers, images, and identifiers. Because this detector matches only the legacy http://schema.org/Product URI, a page marked up exclusively with the modern https:// namespace or with bare JSON-LD will read as 0 here even when its structured data is otherwise correct. Treat the value as an observation about which URI form the page emits, not as a target to force: adding the legacy string purely to flip this signal changes nothing about how the page is understood.

Back to Top

Important considerations

  • https://schema.org/Product and a bare JSON-LD "@type": "Product" do not satisfy this detector.
  • Presence of the URI does not validate that required or recommended Product properties are present.
  • Structured data must match visible, truthful content on the page.
  • Validate the complete markup with current platform tools rather than relying on this presence check alone.
  • This factor is a prioritization signal that relates to position within a measured result set. It does not make a page rank and guarantees no ranking outcome — correlation is not causation.
Back to Top

Related factors

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

Back to Top