Has Schema Corporation is a yes/no signal that returns 1 when a page’s body HTML contains the legacy Schema.org Corporation type URI http://schema.org/Corporation, and 0 when it does not. It only detects that exact URI string — it does not check whether the organization is real, whether the entity details are complete, or whether Corporation is even the right type to use.
| Factor ID | RG-SCH-007 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
This factor detects the legacy Schema.org Corporation type URI on the page. It is a presence check for one specific identifier — the older http://schema.org/Corporation form used to mark up a corporate organization — not an assessment of how well that markup is built or whether the entity behind it is accurate.
How RankGear measures it
RankGear searches the page’s body HTML, with scripts removed, case-insensitively for the string http://schema.org/Corporation. A match scores 1 and no match scores 0. Because the search runs over the body without scripts and keys on the legacy http:// URI, the modern https://schema.org/Corporation form and bare JSON-LD type declarations such as "@type": "Corporation" inside a script block do not match. The detector does not inspect or validate any of the entity’s details.
What RankGear looks for
<div itemscope itemtype="http://schema.org/Corporation">
<span itemprop="name">Example Co</span>
</div>The match is on the literal http://schema.org/Corporation URI, regardless of case. The modern HTTPS URI and JSON-LD type strings carried inside <script> blocks fall outside what this particular check sees.
| Value | Meaning |
|---|---|
| 1 | The body HTML contains the legacy http://schema.org/Corporation type URI. |
| 0 | The legacy Corporation URI was not found in the body HTML. |
How to optimize it
Use the Corporation type only when it accurately describes the organization, and pair it with consistent identity information — a stable name and the same corporate details you present elsewhere. Where a more general or more specific type fits the entity better, prefer that instead. Treat the 1 / 0 result as an observation of whether this legacy URI is present, not as a target to force onto pages where a corporation entity does not belong.
Important considerations
- Modern HTTPS URIs and bare JSON-LD types do not match — this detector keys on the legacy
http://schema.org/Corporationstring in the body HTML. - Entity details are not checked; presence of the URI says nothing about whether the organization data is accurate or complete.
Organizationmay be a more suitable type for many businesses — useCorporationonly when it genuinely applies.- Keep the marked-up data consistent with the visible branding and identity on the page.
- This is a prioritization signal that relates to position within a measured result set — it does not, on its own, cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.