Number of Email Addresses counts how many email-address-like strings RankGear finds in a page’s rendered body after script elements are removed. It is a raw count of pattern matches — it does not verify that any address is real, deliverable, or owned by the business, and more addresses is not inherently better.
| Factor ID | RG-TRS-008 |
|---|---|
| Family | Trust and Contact Signals |
| Measurement | Count |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor counts email-address-like strings found in the rendered body after script elements are removed. It is a tally of how many times an email pattern appears in the visible page content, not a judgment of whether those addresses are appropriate, active, or trustworthy.
How RankGear measures it
RankGear applies a case-insensitive regular expression that requires a local part, an @ sign, and one or more dot-separated domain components. Every regex match is counted, so repeated appearances of the same address each add to the total. Addresses that live only inside removed script elements are not seen and do not count.
What RankGear looks for
# Case-insensitive match on the rendered, script-free body
pattern: local-part "@" domain-component ("." domain-component)+
example: hello@rankgear.com -> one match, counted once
# every match increments the count; duplicates are counted separately| If the page shows… | How to read the count |
|---|---|
| 0 addresses | No email pattern was detected in the rendered body. Fine for pages that route contact through a form, but check whether users on this page expect a direct email. |
| 1 address | A single, consistent contact address — usually the cleanest reading of the signal. |
| Several addresses | Multiple or repeated matches. Confirm they are intentional (for example, distinct departments) rather than duplicates or scraped noise, and that they stay consistent with the business identity. |
How to optimize it
Publish a monitored, appropriate contact email when users genuinely need email contact, and keep it consistent with the business identity. Use clear contact context, and protect addresses from abuse where practical without making contact inaccessible. Treat the number itself as an observation rather than a target to inflate: the goal is a usable, trustworthy way to reach the business, not a high count.
Important considerations
- The regular expression recognizes email-like text; it does not verify deliverability, ownership, or domain reputation.
- Repeated appearances are counted separately, so the same address in a header and footer adds more than one to the total.
- Addresses present only in removed script elements do not count.
- More addresses are not inherently better; compare the competitive data and the actual user need for the page.
- This is a prioritization signal that relates to patterns within a measured result set, not a cause of ranking; a count neither makes a page rank nor guarantees a position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.