Exact Matches making whole H4-H6 Tags counts the lower-level subheadings — H4, H5, and H6 combined — whose entire text is the analyzed query and nothing else. A whole-heading match means the query fills the heading, not merely appears inside it. A count of 0 is normal and often correct, because most deep subsections read better with descriptive wording than with the bare query.
| Factor ID | RG-HDG-014 |
|---|---|
| Family | Headings |
| Measurement | Whole-heading match count |
| Measured zone | H4, H5, and H6 text |
What it measures
This factor counts lower-level headings whose entire text matches the exact-query pattern. It looks only at the three deepest heading levels — H4, H5, and H6 — and tallies each one whose full text qualifies as a whole-heading match, then aggregates all three levels into a single number. A heading that merely contains the query alongside other wording does not count here; the query must be the whole heading.
How RankGear measures it
RankGear applies its both-end-anchored, case-insensitive, separator-flexible query pattern to every H4, H5, and H6 heading on the page. Both-end-anchored means the pattern is fixed to the start and the end of the heading text, so the whole heading has to be the query rather than contain it. Case-insensitive means capitalization does not affect the match. Separator-flexible means each space in the query can match a single optional separator between words, preserving RankGear’s established compatibility behavior. Each qualifying heading across the three levels adds one to the count.
What RankGear looks for
Query: "cast iron care"
Anchored, case-insensitive pattern: ^cast.?iron.?care$
<h4>Cast Iron Care</h4> → whole match, counts
<h5>cast-iron-care</h5> → whole match, counts
<h4>Cast iron care for new pans</h4> → extra wording, does not count
<h6>Seasoning basics</h6> → does not count| Count | How to read it |
|---|---|
| 0 | No H4-H6 heading is exactly the query. Common and often correct — deep subsections rarely need the bare query as their whole heading. |
| 1 | One lower-level subsection is titled with the exact query. Reasonable when a specific deep subsection genuinely warrants it. |
| 2+ | Several deep headings are the exact query. Confirm each is a real, distinct subsection rather than repetition padding the count. |
How to optimize it
Treat this as an observation, not a target to maximize. Use exact standalone phrases only where a legitimate lower-level subsection clearly requires them. Do not add H4-H6 headings, or strip them down to the bare query, just to raise the count — deep exact headings are not inherently valuable, and a naturally structured page will often read 0 here, which is fine. Let document hierarchy and reader clarity decide the wording, then read this count as a description of what the page already does.
Important considerations
- It aggregates three levels — H4, H5, and H6 — into one combined count.
- Deep exact headings are not inherently valuable; a whole-heading match this far down the outline carries no special weight on its own.
- Repetition inflates the count — the same exact heading used across several deep subsections raises the number without adding meaning.
- Avoid artificial structure created only to produce whole-heading matches; deep headings should follow the document’s real hierarchy.
- This value relates to position within a measured result set; it is a prioritization signal, not a cause of ranking. Never distort your heading structure merely to move this count.
Related factors
Part of the Factors reference · how RankGear measures · glossary.