Has Entities in H3 Tags reports whether any of your run’s entities appears anywhere in the page’s H3 headings. It is a simple yes/no signal (1 or 0) — it flags presence only, and does not count how many entities matched or how often.
| Factor ID | RG-ENT-015 |
|---|---|
| Family | Entities |
| Measurement | Boolean presence (0 / 1) |
| Measured zone | H3 text in the rendered page body |
What it measures
This factor reports whether any run entity appears in an H3 heading. It looks only at the text inside H3 elements and returns a single yes/no result: 1 if at least one entity is found in any H3, and 0 otherwise. It says nothing about which entity matched, how many matched, or how many H3s contained a match — only that at least one hit exists.
How RankGear measures it
RankGear lowercases the H3 text and performs substring checks using the entity strings exactly as supplied in your run. Any single hit scores the factor 1. Because the match is a substring test against the entity strings as provided, the casing of the strings in your entity list can affect whether a match is registered. An empty entity list scores 0.
What RankGear looks for
<h3>Choosing a <strong>heat pump</strong> for cold climates</h3>
<!-- entity "heat pump" appears in the H3 text → factor scores 1 -->| Value | Meaning |
|---|---|
| 1 | At least one of your run’s entities was found somewhere in the page’s H3 text. |
| 0 | No entity matched any H3 — either the H3s don’t reference your entities, the casing didn’t align, or the entity list is empty. |
How to optimize it
Use an entity in an H3 when it accurately labels a supporting subsection beneath an H2. H3s mark third-level detail, so an entity belongs there when the subsection is genuinely about that entity. Treat this as an observation about your heading structure rather than a target to force — inserting entity names into H3s that don’t warrant them works against clear, logical headings. Let each subsection earn its heading first, and let the presence flag follow.
Important considerations
- It does not count how many entities matched — the result is presence only, so one hit and many hits both score 1.
- Casing in the entity list can affect compatibility matching, because the check compares the lowercased H3 text against the entity strings as supplied.
- Empty entity lists score 0.
- Preserve a logical heading hierarchy — H3s should sit beneath a relevant H2, not stand in for higher-level structure just to place an entity.
- This is a correlation-based prioritization signal within a measured result set. It relates to position among analyzed pages — it does not by itself make a page rank or guarantee any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.