Has MicroData Telephone reports whether a page’s rendered HTML contains the Microdata attribute itemprop="telephone". It returns 1 when at least one match is present and 0 when none is found. This is a presence check on the raw markup text — it does not confirm the phone number is valid or that the surrounding Microdata item is well formed.
| Factor ID | RG-SCM-044 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor records whether RankGear finds the Microdata property itemprop="telephone" in the rendered body HTML after <script> elements are removed. It is a signal that a page marks up a telephone number using the Microdata vocabulary — typically inside a person, organization, or place item.
What RankGear looks for
<span itemprop="telephone">+1-800-555-0100</span>How RankGear measures it
RankGear runs a case-insensitive search for the literal double-quoted form itemprop="telephone". The attribute name, equals sign, double quotes, and property value must be contiguous. It returns 1 when at least one match exists in the rendered body and 0 otherwise.
| Value | Meaning |
|---|---|
| 1 | The exact string itemprop="telephone" appears at least once in the rendered body (scripts removed). |
| 0 | No matching occurrence — the attribute is absent, or written with single quotes or extra spacing that the pattern does not accept. |
How to optimize it
Treat this as an observation of your markup, not a target to force. Use telephone only as part of a genuine, working telephone number for the person, organization, or place being marked up. Keep the value aligned with the number shown to visitors and with the vocabulary the parent item type expects. If you intend to expose a phone number in Microdata and this factor reads 0, confirm the attribute is written with double quotes in the contiguous form the detector matches.
Important considerations
- The detector pattern-matches HTML text rather than parsing or validating a Microdata item graph — a match does not prove the item is complete or correct.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing will not match.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, the property value, nesting, and structured-data eligibility independently of this factor.
- Correlation is not causation. Presence of this markup relates to position within a measured result set; it is a prioritization signal, not a guarantee that a page will rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.