Has Schema Organization

Abstract illustration of Organization schema markup linking a company entity to its logo, URL, and identity nodes, in RankGear indigo and coral.

Has Schema Organization checks whether a page’s body HTML contains the legacy Schema.org Organization type URI — http://schema.org/Organization. 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 HTTPS URIs and bare JSON-LD @type values can score 0 even when Organization markup is present.

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

What it measures

This factor detects the legacy Schema.org Organization type URI in a page. Organization markup describes the entity behind a site — a company, publisher, or institution — and links it to a canonical name, URL, logo, and identity references. The factor is a binary presence check: it reports whether the specific legacy type URI appears, not how complete or accurate the surrounding markup is.

Back to Top

How RankGear measures it

RankGear case-insensitively searches the page’s body HTML (scripts excluded) for the string http://schema.org/Organization. If that URI is found, the factor returns 1; otherwise it returns 0. It matches the raw text of the URI, so the match 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/Organization">
  <span itemprop="name">RankGear</span>
  <link itemprop="url" href="https://rankgear.com/">
</div>

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

How to optimize it

Use Organization markup for a real entity, describing it with a consistent name, URL, logo, contact details, and identity links. Because this factor keys on the legacy http:// URI form specifically, the practical fit is to ensure your Organization markup references that URI where this signal is what you are checking against — while recognizing that most modern implementations use the HTTPS URI or bare JSON-LD types, which this particular check reads as 0. 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 URIs and bare JSON-LD types can return 0 — only the exact legacy http://schema.org/Organization string matches.
  • The factor does not validate Organization properties; a present URI does not mean the entity data is complete or correct.
  • Use a more specific subtype (for example LocalBusiness or NewsMediaOrganization) when it better describes the entity.
  • Keep entity information consistent across name, URL, logo, contact, and identity links.
  • 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