This factor counts the H5 headings on a page whose entire text is the search query itself. It returns a whole-heading match count for the H5 zone — a page can rank perfectly well with a count of zero, since many pages never nest headings that deeply.
| Factor ID | RG-HDG-015 |
|---|---|
| Family | Headings |
| Measurement | Whole-heading match count |
| Measured zone | H5 text |
What it measures
RankGear counts the H5 headings whose entire text matches the search query. This is a whole-heading test, not a contains test: the H5 has to read as the query and nothing more. A heading that includes the query alongside extra words is not counted, so the value reflects H5 headings that are dedicated, verbatim restatements of the query rather than headings that merely mention it.
How RankGear measures it
RankGear parses every H5 on the page and tests each one against a pattern built from the query. It replaces each space in the query with an optional single character, anchors the resulting case-insensitive expression at both the start and the end of the heading text, and counts the headings that match. Anchoring at both ends is what enforces the whole-heading rule — the heading has to begin and end with the query, with nothing left over. The per-space substitution is what gives the match its separator flexibility.
What RankGear looks for
<h5>how to measure h5 tags</h5> ← counted (whole heading is the query)
<h5>how-to-measure-h5-tags</h5> ← counted (separators satisfy each space)
<h5>how to measure h5 tags fast</h5> ← not counted (extra word)How to optimize it
Treat this as an observation about heading structure, not a target to chase. Use the exact query as an H5 only when it honestly names a deeply nested subsection and fits the page’s existing heading hierarchy. Do not promote or demote headings to H5, or reword a subsection into the raw query, purely to raise this count — forcing verbatim query headings into an outline that does not call for them degrades the page for readers and does nothing dependable for position.
Important considerations
- The whole H5 must match the query; any extra words in the heading prevent a match.
- Separator flexibility means the match can accept punctuation — a hyphen, slash, or other single character — in place of a space.
- The query is inserted into the compatibility pattern without escaping, so characters in the query are treated as part of the expression rather than as literal text.
- A useful, well-structured page may legitimately have no H5 headings at all, and therefore a count of zero.
- This is a correlation-based prioritization signal measured within a result set. It relates to position; it does not cause a page to rank or guarantee any placement.
Related factors
Part of the Factors reference · how RankGear measures · glossary.