Variations in Legend Tags counts how many keyword variations appear inside a page’s <legend> captions — the group-level labels that title form fieldsets. It returns a whole number: the total case-insensitive whole-word variation matches found in captured legend text. It is an observation about how forms are labelled, not a target to write toward.
| Factor ID | RG-KWD-066 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured legend contents |
What it measures
This factor counts keyword variations inside form-group legends. A <legend> is the caption for a <fieldset> — the short heading that names a group of related controls, such as “Billing address” or “Contact preferences.” RankGear reads the text captured within those legends and tallies how many times your tracked keyword and its variations occur there.
How RankGear measures it
RankGear extracts the recognized <legend> contents without an additional cleaning pass, then totals case-insensitive whole-word variation matches within that text. Nested markup remains in the capture, so any elements wrapped inside the legend are part of what gets scanned. Matching is whole-word, so a variation embedded inside a longer token is not counted.
What RankGear looks for
<fieldset>
<legend>Shipping address</legend>
<label>City</label> <input name="city">
</fieldset>The captured text of every legend is scanned, and each whole-word variation match adds one to the count.
How to optimize it
Use legends to give fieldsets clear group-level labels, and include topical wording only when it genuinely describes the form task. Treat this factor as an observation, not a target: it simply reports what your existing form legends contain. Do not write keyword-stuffed captions or add legends to place terms — that degrades the form without earning anything.
Important considerations
- Nested markup remains in the capture, so the count reflects the raw legend content rather than cleaned prose.
- Pages without fieldsets may appropriately score zero; a zero here is normal, not a defect.
- The factor does not assess accessibility implementation — the count says nothing about whether legends are correctly associated with their form groups.
- Do not add legends unrelated to actual form groups.
- Correlation is not causation. This is a prioritization signal that relates to position within a measured result set — it does not make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.