Variations in Form Tags counts how many of your tracked keyword variations appear inside the opening <form> tag itself — its attributes, not the labels or fields a visitor reads. It returns an occurrence count, and because it inspects implementation attributes rather than visible copy, treat it as a legacy compatibility signal to observe, not a target to optimize.
| Factor ID | RG-KWD-057 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Captured opening form tag text |
What it measures
This is a compatibility factor. It counts keyword variations found in the portion of markup captured immediately after the form tag name — in practice, the attributes of the opening tag, such as action, method, id, class, and name. It does not read the form’s inner content: the input fields, buttons, and labels people see are scored by their own factors, not this one.
How RankGear measures it
RankGear matches a complete form block, then evaluates capture group one from the <form(...)> pattern — the text inside the opening tag — rather than the form’s inner content. That captured attribute string is scanned for your tracked keyword variations, and each occurrence is counted. No additional cleaning pass is applied to the captured text before matching.
What RankGear looks for
<form action="/newsletter-signup" method="post" id="signup">
ââ capture group one = the opening-tag text scanned for variations
(action="/newsletter-signup" method="post" id="signup")
</form> <!-- inner fields and labels are NOT read here -->How to optimize it
Do not optimize form attributes for this metric. Choose action and name values for what the form needs to work — meaningful, stable, and correct — and let your visible form labels be optimized through their own factors. Stuffing keyword variations into attributes chases a legacy compatibility count and risks breaking the form. Read this value as an observation, not a target.
Important considerations
- The display name can imply inner content, but the implementation measures opening-tag text — the attributes, not the fields inside the form.
- Attribute punctuation (quotes, slashes, hyphens, equals signs) affects word-boundary matching, so how a variation is counted can depend on the surrounding syntax.
- Changing form attributes to influence this count may break the form’s functionality.
- Treat the value as a legacy compatibility signal, kept for continuity rather than active tuning.
- Correlation is not causation: this factor tracks how a captured attribute string relates to position within a measured result set. It is a prioritization signal, not something that makes a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.