This factor counts how many times your keyword’s variations appear inside HTML <dialog> elements on the page. It is a raw occurrence count of the text RankGear captures from dialog markup — a descriptive observation of where topical language lives, not a target to inflate.
| Factor ID | RG-KWD-048 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured dialog contents |
What it measures
The factor counts keyword variations inside recognized HTML <dialog> elements. Rather than checking the body copy a reader normally sees, it isolates the text held in dialog markup — modal windows, confirmation prompts, and similar overlay containers — and tallies how often your keyword’s variant forms occur there.
How RankGear measures it
RankGear extracts the contents of each <dialog> element from the script-free body without additional cleaning, then sums case-insensitive whole-word variation matches. No stripping of nested markup or normalization beyond removing scripts happens first, so the captured text is the dialog’s raw content, and every whole-word match of a keyword variation adds to the count.
What RankGear looks for
<dialog open>
<h2>Compare running shoes</h2>
<p>Pick the trail running shoe that fits your gait.</p>
</dialog>In the snippet above, variations of a “running shoes” keyword inside the dialog are what the factor tallies. Whether the dialog is open or closed does not change what is captured.
How to optimize it
Treat this as an observation, not a number to push up. Write clear, task-focused dialog content and include topical language only when it genuinely helps users understand the interaction in front of them. If a dialog reads naturally and contains a variation because the wording calls for it, that is fine; there is no benefit to padding a modal with keywords users did not come for.
Important considerations
- Hidden or closed dialog markup can still contribute to the count — the factor reads the content in the markup, not what is currently visible on screen.
- Nested markup remains in the captured content, so text inside tags nested within the dialog is still counted.
- The factor does not measure accessibility or interaction behavior — it says nothing about whether the dialog is usable, focus-trapped, or announced to assistive technology.
- Avoid loading keyword-rich dialogs that users do not need; content added only to raise this count works against the reader.
- This is a prioritization signal that relates to position within a measured result set. It does not, on its own, cause or guarantee a ranking — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.