Variations in Fieldset Tags counts how many keyword variations appear inside a page’s <fieldset> groups. It returns a whole number — the total case-insensitive whole-word variation matches found in captured fieldset content — and it is an observation about how forms are structured, not a target to write toward.
| Factor ID | RG-KWD-052 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured fieldset contents |
What it measures
This factor counts keyword variations that appear inside grouped form controls enclosed by <fieldset> elements. The <fieldset> tag groups related inputs together — a set of radio buttons, an address block, a billing section — usually under a <legend>. RankGear reads the text captured within those groups and tallies how many times your tracked keyword and its variations occur there.
How RankGear measures it
RankGear extracts the recognized <fieldset> contents from the script-free body without cleaning them, then totals case-insensitive whole-word variation matches within that text. Nested inputs and surrounding markup remain in the capture, so label text, legends, and control values inside the group are all part of what gets counted. Matching is whole-word, so a variation embedded in a longer token is not counted.
What RankGear looks for
<fieldset>
<legend>Shipping address</legend>
<label>City</label> <input name="city">
<label>State</label> <input name="state">
</fieldset>The captured text of every such group is scanned, and each whole-word variation match adds one to the count.
How to optimize it
Use <fieldset> to group genuinely related controls and give that form content clear, task-relevant wording — legends and labels that describe what the person is actually filling in. Treat this factor as an observation, not a target: it simply reports what your existing forms contain. Do not add form groups, or pad legends and labels, to place keywords — that harms the form without earning anything.
Important considerations
- Nested inputs and markup remain in the capture, so the count reflects the raw grouped content rather than cleaned prose.
- The factor does not assess form usability or accessibility — a high count says nothing about whether the form is well-built.
- Pages without forms may correctly score zero; a zero here is normal and not a defect.
- Do not add form groups for keyword placement.
- 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.