This factor is a yes/no check for whether the Microdata attribute itemprop="addressLocality" appears in the page’s rendered body after scripts are stripped. It returns 1 when at least one literal match is found and 0 otherwise — it detects the attribute string, it does not validate that your address markup is correct.
| Factor ID | RG-SCM-003 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
RankGear reports whether the Microdata property itemprop="addressLocality" is present anywhere in the rendered body once script elements have been removed. In the schema.org vocabulary, addressLocality carries the city or locality of a postal address, so this factor tells you whether a page exposes that specific piece of address markup to machines reading the HTML.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="addressLocality". It returns 1 when at least one match exists and 0 otherwise. The match is a text search over the rendered body: the attribute name, the equals sign, the double quotes, and the property value must be contiguous.
What RankGear looks for
<span itemprop="address" itemscope itemtype="https://schema.org/PostalAddress">
<span itemprop="addressLocality">Austin</span>
</span>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="addressLocality" was found in the rendered body. |
| 0 | No contiguous double-quoted match was found (the attribute is absent, uses single quotes, or has extra spacing). |
How to optimize it
Use addressLocality only as part of the correct city or locality within a genuine postal address. Keep the markup aligned with visible content and with the vocabulary expected by its parent item type. Treat a 1 as confirmation that the attribute string is present, not as a target to chase — adding the attribute where there is no real address, or where it does not match what visitors see, does not help and can undermine your structured data.
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.
- Presence of this attribute correlates with, and does not cause, position within a measured result set; it is one prioritization signal among many, not a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.