Has MicroData Location is a binary presence check: RankGear returns 1 when it finds the Microdata attribute itemprop="location" in a page’s rendered body HTML (after scripts are stripped), and 0 when it does not. It is a literal text match, not a validation of your Microdata graph — a hit means the string is present, nothing more.
| Factor ID | RG-SCM-024 |
|---|---|
| Family | Structured Data – Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether RankGear finds the Microdata attribute itemprop="location" in the rendered body after script elements are removed. It answers a single question — is that property string present on the page or not — and nothing about whether the surrounding Microdata item is well-formed or eligible for a rich result.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="location". It returns 1 when at least one match exists and 0 otherwise. The match is on raw HTML text, not on a parsed item graph, so the attribute name, equals sign, double quotes, and property value must appear contiguously for the detector to fire.
What RankGear looks for
<div itemscope itemtype="https://schema.org/Event">
<span itemprop="location">Denver Convention Center</span>
</div>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="location" appears at least once in the script-stripped body HTML. |
| 0 | The string is absent — including when location is written with single quotes or extra spacing, which the detector does not match. |
How to optimize it
Use location only as part of the real place or virtual location associated with the marked-up entity or event. Keep the value aligned with visible content and with the vocabulary expected by its parent item type. Write the attribute in the contiguous double-quoted form the detector recognizes — single quotes or added spacing around the equals sign will read as absent. Treat this as a presence observation rather than a target to chase: mark up a location because the entity genuinely has one, not to move this signal.
Important considerations
- The detector pattern-matches HTML text instead of parsing or validating a Microdata item graph.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing do not match.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently — a match here is no guarantee your Microdata is valid or eligible.
- This is a correlation-level prioritization signal within a measured result set, not a cause of ranking; presence of the attribute does not make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.