Variations in Footer Tags counts how many times your keyword’s whole-word variations appear inside the content held by paired <footer> tags. It is an observation of where variation language lands in the page’s footer region, not a target to chase — because footers are usually shared sitewide, the same count tends to repeat across every page that reuses the template.
| Factor ID | RG-KWD-056 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured footer contents |
What it measures
This factor counts keyword variations that occur inside recognized <footer> elements. It looks only at the text held between paired footer tags, so it reflects how much of your variation language sits in the footer — typically navigation, contact details, copyright lines, and other contextual information — rather than in the main body, headings, or links.
How RankGear measures it
RankGear extracts capture group two between paired <footer> tags from the script-free body — the page with scripts already removed — without an additional cleaning pass, then sums whole-word variation matches case-insensitively. Because the capture is taken directly from the raw footer contents, any nested markup inside the footer stays in the captured text, and matches are counted as complete words regardless of letter case.
What RankGear looks for
<footer ...>( ...captured contents, nested markup included... )</footer>
sum of whole-word variation matches, case-insensitive, inside the captured groupHow to optimize it
Treat this as an observation, not a target. Keep footers useful and concise, using topical words only where they belong in legitimate navigation, contact, or contextual information. The presence of variations in the footer should be a by-product of a well-built footer, not the result of padding it with keywords. Do not stuff sitewide footers with terms to raise the count — the factor is meant to describe the language already present, not to reward footer markup.
Important considerations
- Nested markup inside the footer remains in the capture, so links, spans, and other inline elements contribute their text to what is counted.
- Repeated template footers affect every analyzed page — a keyword added once to a shared footer shows up on all pages that reuse it.
- The parser is bounded and regex-based, so unusual or malformed footer markup can change what falls inside the captured region.
- Do not stuff sitewide footers with keywords; a footer exists to serve navigation and context, not to hold repeated terms.
- This is a correlation-based signal measured within a result set. A higher count does not make a page rank or guarantee a position; it is one prioritization observation among many.
Related factors
Part of the Factors reference · how RankGear measures · glossary.