Variations in Value Attributes counts how many of your keyword variations appear inside the page’s double-quoted value="…" strings — the data carried by form fields and other controls, not visible reader copy. It is implementation context, so read it as one small signal and never rewrite functional values just to raise it.
| Factor ID | RG-KWD-090 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Double-quoted value attribute strings |
What it measures
This factor counts keyword-variation occurrences in recognized HTML value attributes. It looks past visible text into the markup itself, tallying how often the run’s variation set shows up inside the value strings that carry the data on inputs, options, buttons, and other controls, rather than inside the words a reader sees on the page.
How RankGear measures it
RankGear extracts double-quoted value="…" strings from the script-free body, then applies case-insensitive whole-word variation matching to their raw values. Only the double-quoted form is read, and the match is made against the literal value text exactly as written in the source.
What RankGear looks for
<input type="hidden" value="product-review-guide">
<option value="best-pricing-plan">…</option>
match: case-insensitive, whole-word, on the raw double-quoted valueHow to optimize it
Use the values your forms and application logic require, and optimize visible labels separately — do not alter data contracts for keywords. Treat this as a read on how your existing markup happens to line up with the variation set, not a target to hit. If topical wording appears in a value, let it be because that value genuinely describes the control, never because you are chasing keyword relevance in fields the page depends on to function.
Important considerations
- Single-quoted and dynamically generated
valueattributes may not match this parser, so real occurrences can go uncounted. - Values can be hidden from users — they often live on hidden inputs and controls the reader never sees — so this count need not reflect visible copy at all.
- Changing values can break form submissions or scripts, because those strings are wired into how the page actually works.
- Treat this as implementation context, not an editorial target.
- 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.