The Has Schema Local Business factor returns 1 when a page’s body HTML contains the legacy Schema.org type URI http://schema.org/LocalBusiness, and 0 when it does not. It is a presence check for one exact string — it confirms the type is declared, not that the underlying business data is valid, complete, or accurate.
| Factor ID | RG-SCH-012 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
This factor detects the legacy Schema.org LocalBusiness type URI within a page. Its presence tells RankGear that a page has explicitly declared a local-business entity type using the older HTTP form of the Schema.org namespace. The check is strictly about whether that specific type reference appears — it does not read, parse, or judge the address, hours, or contact details attached to it.
How RankGear measures it
RankGear searches the page’s body HTML (with script contents excluded) case-insensitively for the string http://schema.org/LocalBusiness. If that exact type URI is found, the factor records 1; otherwise it records 0. Only this legacy HTTP form of the URI counts toward the match.
What RankGear looks for
<div itemscope itemtype="http://schema.org/LocalBusiness">
<span itemprop="name">…</span>
<span itemprop="telephone">…</span>
</div>| Value | Meaning |
|---|---|
| 1 | The legacy http://schema.org/LocalBusiness type URI is present in the body HTML. |
| 0 | The URI is absent — including pages that use the HTTPS form or a bare JSON-LD type, which this detector does not count. |
How to optimize it
Where a local-business entity genuinely applies to the page, declare it with the most specific valid LocalBusiness subtype and keep the name, address, phone, hours, and URL data consistent with what visitors see. Treat this factor as an observation about which markup form a page uses, not a target to chase for its own sake — the goal is accurate, well-matched structured data, and this detector simply notes whether the legacy type string is one of the ways that data is expressed.
Important considerations
- The HTTPS form of the URI and bare JSON-LD type declarations do not satisfy this detector; it matches only the legacy
http://form. - Business data is not validated — presence of the type says nothing about whether the name, address, or hours are correct.
- Markup should match the page’s visible content and the business’s real-world details.
- Consistency across external listings and directories remains important beyond what any single page declares.
- This is a correlation-based prioritization signal within a measured result set, not a guarantee of ranking — declaring the type does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.