This factor counts how many keyword variations appear inside a page’s button elements. It is a raw occurrence count of the words your interactive controls actually say — and because it reads the captured button contents verbatim, nested markup, icons, and repeated template buttons all shape the number.
| Factor ID | RG-KWD-040 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured button contents |
What it measures
This factor counts keyword variations inside recognized button elements. It looks only at the text carried by button tags — the labels on the page’s clickable controls — and tallies how many times your target term and its variants show up there. The result is a count of topical words in your calls to action, not a score of button quality or usability.
How RankGear measures it
RankGear extracts button contents from the script-free body without an extra HTML-cleaning pass, then counts case-insensitive whole-word variation matches. Because there is no additional cleaning step, whatever text sits inside the tag — including nested spans or stray markup — is what gets read and matched. Matching is whole-word and case-insensitive, so “Download”, “download”, and “downloads” are evaluated against the variation list rather than treated as arbitrary substrings.
What RankGear looks for
<button>Download the SEO report</button>
<button type="submit">Start your audit</button>How to optimize it
Write concise button labels that clearly describe the action, and include topical words only when they make that action more specific. Treat this count as an observation of how your controls read, not a target to inflate: adding keywords to buttons for the sake of the number works against the clarity that makes a button worth clicking. If a label reads well and names the thing the user is about to do, it is already doing its job.
| If the button label is… | Do this |
|---|---|
| Vague (“Click here”, “Submit”) | Name the action and, where it sharpens meaning, the topic (“Download the SEO report”). |
| Keyword-stuffed | Cut it back to the plain action; usability outranks the count. |
| Icon-only | Expect little or no contribution; add a visible text label if the action needs describing. |
Important considerations
- Nested markup inside a button can affect the raw capture, since the contents are read without an extra cleaning pass.
- Icon-only controls and
input-based buttons may not contribute to the count. - Repeated template buttons — the same control echoed across a layout — can inflate the total.
- Usability, not this count, should determine how a button is worded.
- This is a correlation-based prioritization signal within a measured result set. A higher count does not make a page rank and guarantees nothing about position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.