Has Email is a yes/no signal that reports whether RankGear found at least one email-address pattern in a page’s rendered body after scripts are stripped — 1 when a qualifying pattern is present, 0 when none is found. It confirms only that an address-like string exists; it does not verify that the address is visible, current, deliverable, monitored, or appropriate for the page.
| Factor ID | RG-TRS-003 |
|---|---|
| Family | Trust & contact signals |
| Measurement | Boolean (0 / 1) |
| Measured zone | Rendered page body source |
What it measures
Has Email reports whether RankGear detects at least one email-address pattern in the rendered page body after scripts are removed. A value of 1 means a qualifying pattern was found; a value of 0 means none was found. The factor identifies the presence of an address-like string. It does not verify that the address is visible, current, deliverable, monitored, or appropriate for the page.
How RankGear measures it
RankGear searches the script-free body HTML for a pattern containing an allowed local part, an at sign, a domain, and one or more dot-separated domain segments. The matching is case-insensitive and can detect addresses in visible text or in body markup such as link attributes. One or more matches produce 1; the number of addresses is measured by a separate factor.
What RankGear looks for
<a href="mailto:hello@example.com">Email us</a>
hello@example.com| Value | Meaning |
|---|---|
| 1 | At least one email-address pattern was found in the script-free body. |
| 0 | No qualifying email-address pattern was found. |
How to optimize it
Provide an appropriate contact route when users reasonably need one. A business may show a monitored email address or link to a contact page or form, depending on its privacy, spam, support, and operational requirements. Make contact information easy to find, accurate, accessible, and consistent with the business identity. Treat this factor as an observation rather than a target: do not publish an address solely to change the value if another contact method better serves users.
Important considerations
- An address in markup can satisfy the detector even when it is not visibly presented to readers.
- Obfuscated email addresses may not match the pattern.
- Presence does not confirm deliverability or response quality.
- Publishing email addresses can increase spam exposure.
- Review this factor alongside contact-page, mail-link, address-count, phone, and other trust signals.
- This is a prioritization signal that relates to position within a measured result set; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.