Exact Matches in the HTML Tag counts every occurrence of the analyzed search phrase across a page’s complete rendered HTML source — content, headings, metadata, attributes, and markup alike, not only visible body text. Because it reads the whole source, the same wording can be counted more than once, so treat the number as an observation rather than a target.
| Factor ID | RG-KWD-012 |
|---|---|
| Family | Keyword usage & density |
| Measurement | Count |
| Measured zone | Complete rendered HTML source |
What it measures
This factor counts occurrences of the analyzed search phrase across the complete rendered HTML source of the page. Despite the legacy display name, it is not limited to the opening HTML element and is not restricted to visible body text. The count can reflect phrase usage anywhere in the source — content, headings, metadata, attributes, or other areas of the rendered markup.
How RankGear measures it
RankGear converts each run of whitespace in the analysis phrase into a pattern that accepts one or more whitespace characters, then counts every match of that pattern across the raw rendered HTML captured for the page. Because the entire source is measured, wording that is visible once on the page may also appear elsewhere in the markup and contribute additional matches. If no occurrence is found, the result is 0.
What RankGear looks for
phrase: content marketing services
pattern: content\s+marketing\s+services
scanned: the complete rendered HTML source
result: count of all matches (0 if none)| Count value | How to read it |
|---|---|
| 0 | The phrase does not appear anywhere in the rendered source. |
| >0 | The phrase appears this many times across the whole source — some matches may come from markup or repeated representations, not only visible copy. |
How to optimize it
Improve visible, useful content first. Use the search phrase where it genuinely describes the page — in the title, headings, body, metadata, links, or other meaningful locations that the competitive evidence supports. Do not add hidden text, unnecessary attributes, repeated metadata, or nonfunctional markup merely to raise this source-level count. Treat the number as an observation, not a goal: review the zone-specific RankGear factors to find where a genuine gap actually exists.
Important considerations
- This value is not a count of visible exact matches alone — it reads the whole rendered source.
- Markup and repeated source representations can affect the total.
- The measurement is specific to RankGear’s rendered DOM capture.
- Raw count increases are not automatically beneficial and may simply indicate repetition.
- Use the cleaned-content, body, title, heading, and density factors for more targeted decisions.
- This is a prioritization signal that relates to position within a measured result set; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.