This factor checks whether a page’s body HTML contains the legacy Schema.org Place type declared over HTTP. It returns a simple present-or-absent signal (1 or 0) — it confirms only that the URI string appears, not that any location properties are correct.
| Factor ID | RG-SCH-017 |
|---|---|
| Family | Schema.org |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
This factor detects the legacy Schema.org Place type URI within the page. Place represents a physical location with a somewhat fixed extent — a business, a landmark, a venue. Its presence indicates that the page has marked up an entity as a real-world location using this vocabulary.
How RankGear measures it
RankGear case-insensitively searches the body HTML (with scripts excluded) for the string http://schema.org/Place. If that URI is found, the factor scores 1; otherwise it scores 0. Note the protocol: the match targets the http:// form specifically, so an https:// URI or a bare JSON-LD type will not satisfy this exact string.
What RankGear looks for
<div itemscope itemtype="http://schema.org/Place">
<span itemprop="name">Central Library</span>
<div itemprop="address">…</div>
</div>| Value | Meaning |
|---|---|
| 1 | The http://schema.org/Place URI is present in the body HTML. |
| 0 | The URI is absent — including HTTPS-only or bare JSON-LD type declarations. |
How to optimize it
Where the page describes a genuine physical location, use Place — or a more specific subtype — with an accurate address and consistent geographic information. Treat this factor as an observation of which vocabulary form is present rather than a target to chase: the goal is correct, honest markup for a real location, not the mere appearance of a URI string. If your entity fits a narrower type, prefer that narrower type over generic Place.
Important considerations
- HTTPS URIs and bare JSON-LD type declarations can score 0, because this factor matches the
http://schema.org/Placeform specifically. - Location properties (address, geo coordinates, and the like) are not checked — only the presence of the type URI is.
- Prefer the most specific valid type for your entity over the generic
Place. - Keep geographic details consistent and accurate across the page and your other structured data.
- This is a correlation-based prioritization signal observed within a measured result set. Presence of the URI does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.