Variations in Address Tags counts how many keyword variations appear inside recognized HTML <address> elements, returning a whole-word occurrence count for that contact block. It describes wording inside your contact markup that correlates with position in a measured result set — an observation about a page, not a lever that makes a page rank.
| Factor ID | RG-KWD-034 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | address element contents |
What it measures
This factor counts keyword variations within recognized HTML <address> elements. The <address> element is the semantic container for contact information — a business name, a street address, a phone number, or the byline for the nearest article or page. Rather than scoring the whole document, RankGear narrows to that contact block and tallies how many of your tracked keyword variations show up inside it.
How RankGear measures it
RankGear extracts capture group two — the content between the <address> tags — from the script-free body without an extra HTML-cleaning pass, then counts case-insensitive whole-word variation matches inside that captured text. Matching is whole-word, so a variation is only counted when it appears as a complete token, and it is case-insensitive, so capitalization in the contact block does not change the count.
What RankGear looks for
<address>
Acme Plumbing · 12 Main St · Springfield
(555) 010-0100
</address>The text captured between the opening and closing <address> tags is scanned for whole-word matches against each tracked keyword variation.
How to optimize it
Use <address> for legitimate contact information, and include business or service terminology only where it accurately belongs in that contact block. Treat this factor as an observation about how your contact markup is written, not a target to inflate: adding keyword variations to an <address> element where they do not honestly belong misuses the element and does nothing to earn a position. If your top-performing peers naturally carry service or location terms in their contact blocks, a low count is a prompt to check that your own contact information is complete and correctly marked up.
Important considerations
- The factor measures element contents, not attributes — text inside the tags is counted, values on attributes are not.
- Nested markup can influence the uncleaned capture, because the content is read without an extra HTML-cleaning pass.
- Bounded compatibility parsing may exclude malformed
<address>elements from the capture. - Do not misuse
<address>as a keyword container — it is meant for genuine contact information. - This is a correlation, not a cause. A higher count tracks with, but does not guarantee, a stronger position; it is a prioritization signal within a measured result set, never a promise that a page will rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.