Has MicroData Address Region records whether RankGear finds the Microdata attribute itemprop="addressRegion" in a page’s rendered body HTML. It returns 1 when the exact double-quoted attribute is present and 0 when it is not — a text-pattern match, not a validation of the surrounding structured-data graph.
| Factor ID | RG-SCM-004 |
|---|---|
| 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="addressRegion" in the rendered body after script elements are removed. In the schema.org PostalAddress vocabulary, addressRegion carries the state, province, or region of a postal address, so its presence signals that a page marks up that part of an address in machine-readable Microdata.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="addressRegion". It returns 1 when at least one match exists in the rendered body and 0 otherwise. Script elements are stripped before the search runs, so markup that appears only inside scripts does not count.
What RankGear looks for
<span itemprop="addressRegion">CA</span>| Value | Meaning |
|---|---|
| 1 | The exact attribute itemprop="addressRegion" appears at least once in the rendered body. |
| 0 | The attribute is absent, or written with single quotes or extra spacing, so the literal double-quoted form does not match. |
How to optimize it
Use addressRegion only as part of the correct state, province, or region within a genuine postal address, and keep the markup aligned with the visible content and the vocabulary expected by its parent item type. Treat this factor as an observation of whether that markup is present, not a target to chase — adding the attribute where no real address exists does not help. Because the detector matches a literal double-quoted string, write it as itemprop="addressRegion" with double quotes and no added spacing.
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 the attribute is a correlation-based prioritization signal within a measured result set, not a guarantee — it relates to position, it does not make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.