Has Schema Store

Abstract illustration of Store schema markup linking a retail storefront glyph to a structured-data tag node, in RankGear indigo and coral.

Has Schema Store checks whether a page’s body HTML contains the legacy Schema.org Store type URI — http://schema.org/Store. It returns 1 when that exact URI is present and 0 when it is not. The important caveat: RankGear looks only for the legacy http:// form, so an HTTPS URI or a bare JSON-LD "@type": "Store" can score 0 even when Store markup is present.

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

What it measures

This factor detects the legacy Schema.org Store type URI in a page. Store describes a retail location — a physical or online shop — and is the schema type used to mark up a business’s storefront identity. The factor is a binary presence check: it reports whether the specific legacy type URI appears, not whether the surrounding markup is complete or accurate.

Back to Top

How RankGear measures it

RankGear performs a case-insensitive search of the page’s body HTML (scripts excluded) for the literal string http://schema.org/Store. If that URI is found, the factor returns 1; otherwise it returns 0. The match is on the raw text of the URI, so it is exact to the legacy http:// scheme and does not resolve equivalent HTTPS or bare-type forms.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/Store">
  <span itemprop="name">Example Retail</span>
  <span itemprop="address">123 Main St</span>
</div>

// note: an HTTPS URI or a bare JSON-LD type is NOT matched:
"@type": "Store"
ValueMeaning
1The legacy http://schema.org/Store URI was found in the body HTML.
0The URI was not found — no Store markup, or it uses an HTTPS URI or a bare Store type name.
Back to Top

How to optimize it

Use Store, or a more specific subtype, for a real retail location described with consistent business details — name, address, and the properties that identify the storefront. Because this factor keys on the legacy http:// URI form specifically, most modern implementations that use the HTTPS URI or bare JSON-LD types will read as 0 here. Treat the result as an observation about which URI form your markup uses, not a target to chase for its own sake.

Back to Top

Important considerations

  • https://schema.org/Store and a bare JSON-LD "@type": "Store" do not satisfy this detector — only the exact legacy http://schema.org/Store string matches.
  • Presence does not validate the required or recommended properties of the Store type.
  • 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 is a prioritization signal that relates to position within a measured result set. It does not cause or guarantee rankings — correlation is not causation.
Back to Top

Related factors

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

Back to Top