Entities in H6 Tags

Entities in H6 Tags checks whether any of the run’s tracked entities appears inside an H6 heading in the rendered page body. It returns 1 when at least one entity string is found and 0 when none is — and because most well-structured pages have no H6s at all, a 0 here is normal, not a defect.

Factor IDRG-ENT-010
FamilyEntities
MeasurementBoolean presence (0 / 1)
Measured zoneH6 text in the rendered page body

What it measures

This factor reports whether any run entity appears in any H6 heading. H6 is the deepest heading level in HTML, so it typically labels a very granular subsection several levels down from the main topic. The factor is a plain presence check at that depth: it asks whether the entities RankGear is tracking for this run surface in H6 text anywhere on the page, and returns a single boolean answer for the whole page.

How RankGear measures it

RankGear lowercases the text of every H6 in the rendered body, then checks each supplied entity string against that text using substring matching. Any hit scores 1; if no entity from the list is found, the factor scores 0. The entity strings are matched as supplied, so their casing on the entity-list side affects whether a match is found against the lowercased H6 text.

What RankGear looks for

<h6>Recombinant antibody expression</h6>

match when: lowercase(H6 text) contains the entity string (as supplied)
ValueMeaning
1At least one tracked entity string was found in H6 text on the page.
0No tracked entity was found in any H6 — including pages that have no H6 headings at all.

How to optimize it

Use entities in H6s only when they accurately label genuinely deep subsections. Treat this factor as an observation about how far your entities reach into the heading hierarchy, not as a target to hit. If your page has no legitimate need for H6-level structure, leave it alone: a 0 is the correct reading for most pages, and forcing entities into artificial sub-sub-headings degrades the outline rather than improving it.

Important considerations

  • Most pages correctly have no H6s, so a 0 on this factor is normal and expected rather than a problem to fix.
  • Entity-list casing can affect detection: H6 text is lowercased, but entity strings are matched as supplied, so a mixed-case or uppercase entity string may fail to match lowercased heading text.
  • It does not count occurrences — one matching entity and many matching entities both score 1.
  • Do not deepen your heading hierarchy just to satisfy this factor.
  • This is a correlation-based prioritization signal measured within a result set. Presence of an entity in an H6 does not make a page rank or guarantee a position; it describes a relationship, not a cause.

Related factors

Part of the Factors reference · how RankGear measures · glossary.