Variations in Template Tags counts how many of your tracked keyword variations appear inside inert HTML <template> elements — markup the browser parses but holds in reserve, unrendered until a script activates it. The value is a raw occurrence count, and because template contents are invisible to an ordinary reader, it belongs beside your visible-relevance signals rather than inside them.
| Factor ID | RG-KWD-087 |
|---|---|
| Family | Keyword Usage & Density |
| Measurement | Variation occurrence count |
| Measured zone | Raw captured template contents |
What it measures
This factor counts keyword variations inside inert HTML <template> elements. A <template> holds a fragment of markup that the browser parses but keeps dormant — it is not painted to the page until JavaScript clones and activates it. RankGear looks at that reserved content specifically and tallies how many of your tracked keyword variations land there.
How RankGear measures it
RankGear extracts recognized template contents from the script-free body without additional cleaning and sums whole-word variation matches case-insensitively. Nothing is normalized beyond removing scripts from the surrounding body: the raw template payload is read as captured, and every whole-word match against your variation set adds one to the count, regardless of letter case.
What RankGear looks for
<template id="card">
<li>best running shoes review</li>
<li>running shoe comparison</li>
</template>| If the count is… | What it suggests |
|---|---|
| 0 | No tracked variations live in template fragments; visible content carries all of the page’s keyword relevance. |
| Elevated | Reusable template markup repeats your keywords. Confirm it reflects genuine components, not phrasing hidden from readers. |
How to optimize it
Treat this as an observation, not a target. Do not optimize hidden templates for keyword use; keep reusable markup accurate and surface the information that matters inside rendered content a reader actually sees. A high count here usually reflects how your component library builds template fragments rather than a lever worth pulling for relevance.
Important considerations
- Template contents are not rendered until activated, so they never reach a reader unless a script clones them into the page.
- Nested markup remains in the capture — elements inside the template are counted along with everything else it holds.
- Component libraries and frameworks can influence the value, since they often ship repeated template fragments.
- Treat it separately from visible relevance; a variation counted here is not the same as one a reader sees.
- This is a prioritization signal that relates to position within a measured result set, not a cause of ranking — correlation is not causation, and no single factor guarantees a position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.