Variations in H2 Tags counts how many times the run’s keyword variations appear in a page’s H2 headings. It returns an occurrence total, not a count of unique H2s, so repeating near-identical headings can inflate it without adding coverage.
| Factor ID | RG-HDG-037 |
|---|---|
| Family | Headings |
| Measurement | Occurrence count |
| Measured zone | H2 text in the rendered page body |
What it measures
This factor counts occurrences of the run’s keyword variations across a page’s H2 headings. It reflects how often secondary section labels reach for query-related language beyond the exact keyword alone, giving a view of how broadly the subheadings echo the topic’s related terms.
How RankGear measures it
RankGear extracts every recognized H2, then counts case-insensitive, word-aware occurrences of the run’s variation terms across the heading text. Longer terms are processed first, and matched text is consumed so overlapping matches are not double-counted. The result is an occurrence total across all H2s, not a count of how many distinct H2s contain a variation.
How to optimize it
Treat the number as an observation about your subheadings, not a target to inflate. Use relevant variations in H2s where they accurately label distinct subtopics, questions, services, attributes, or stages of the subject, and let each heading genuinely preview the section beneath it. Broaden the terminology naturally across sections rather than repeating near-identical headings to push the count up.
| If the page is… | Do this |
|---|---|
| Short or tightly focused on one subtopic | A low value may be correct — don’t force extra variations into headings that don’t need them. |
| Broad, covering many facets competitors also cover | Label distinct sections with the natural variations they’re actually about, so subheadings preview real subtopics. |
| Repeating similar H2s to raise the count | Consolidate or rephrase — repetition lifts the number without improving coverage. |
Important considerations
- The variation list is specific to the analysis run, so the same page can score differently under a different set of variation terms.
- Repetition can raise the count without improving coverage — more occurrences is not automatically better.
- A low value may be correct for a short or tightly focused page.
- Interpret it alongside H2 count, entity coverage, and the actual sections competitors provide, rather than on its own.
- This is a correlation-based prioritization signal measured within a result set — it relates to position, it does not guarantee a ranking or make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.