Variations in NAME Attributes counts how many of your keyword variations appear inside the page’s double-quoted name="…" values — the identifiers on form fields and other named elements, not visible copy. It is an incidental-placement observation, so read it as one small signal and never rename functional fields just to raise it.
| Factor ID | RG-KWD-070 |
|---|---|
| Family | Keyword usage & density |
| Measurement | Variation occurrence count |
| Measured zone | Double-quoted name attribute values |
What it measures
This factor counts keyword-variation occurrences in recognized HTML name attributes. It looks past visible text into the markup itself, tallying how often the run’s variation set shows up inside the name values that identify form fields and other named elements, rather than inside the words a reader sees.
How RankGear measures it
RankGear extracts double-quoted name="…" values from the script-free body, then applies case-insensitive whole-word variation matching to the raw attribute strings. Only the double-quoted form is read, and the match is made against the literal name text exactly as written in the source.
What RankGear looks for
<input name="product-review-rating" type="text">
<select name="pricing-comparison-plan">…</select>
match: case-insensitive, whole-word, on the raw double-quoted valueHow to optimize it
Use stable, descriptive names required by your forms and application logic, and let topical wording appear only when it genuinely describes the field. Treat this as an observation of how your existing markup happens to line up with the variation set, not a target to hit — do not rename functional fields to chase keyword relevance, because those names are wired into how the page actually works.
Important considerations
- Single-quoted name forms may not match this parser, so real occurrences can go uncounted.
- Names can be part of submitted data contracts, so the field identifier a form posts is often fixed by the receiving system.
- Punctuation changes word-boundary behavior, which alters what counts as a whole-word match.
- Changing names can break integrations, form handling, and application logic, so it is not recommended for SEO reasons.
- This count tracks how a page relates to a measured result set; it is a prioritization signal, not a cause of ranking and not a guarantee of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.