Bytes To First H Tag reports how far into a page’s raw rendered HTML the first structural heading appears — specifically, the UTF-16 offset of the earliest supported H1 through H4 opening tag. A smaller number means a heading arrives sooner in the markup; despite the name it counts UTF-16 string positions, not encoded or transferred bytes, and returns 99999 when no supported heading tag is found.
| Factor ID | RG-SIZ-005 |
|---|---|
| Family | Markup Position |
| Measurement | UTF-16 offset or sentinel |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports the UTF-16 offset of the earliest supported H1 through H4 opening tag in the raw rendered HTML. It is a position measurement: the distance, in UTF-16 code units, from the start of the document to where the first structural heading begins. A smaller offset means the first heading sits nearer the top of the markup; a larger one means the reader — and any parser reading structure from headings — reaches your first heading later.
How RankGear measures it
RankGear searches the raw rendered HTML case-sensitively for H1, H2, H3, and H4 opening tags in either all-lowercase or all-uppercase form, each followed by either a space or an immediate >, and returns the smallest UTF-16 index at which any of those forms appears. If no supported form occurs anywhere in the document, it returns the sentinel value 99999.
What RankGear looks for
<h1 <h1> <H1 <H1>
<h2 <h2> <H2 <H2>
<h3 <h3> <H3 <H3>
<h4 <h4> <H4 <H4>| Value | Meaning |
|---|---|
| Low offset (e.g. a few hundred) | A supported H1–H4 opening tag appears early in the raw HTML. |
| High offset | The first supported heading appears deep into the markup. |
99999 | Missing-tag sentinel — no supported H1–H4 form was found. Not a literal position. |
How to optimize it
Place semantic H1 through H4 opening tags where the document structure and visible content genuinely require them. Treat this offset as an observation of where your first heading lands, not a target to be minimized: keep important content accessible and readable, and do not add empty or premature heading tags merely to lower the number. A heading arriving early because the page is well structured is meaningful; a heading forced to the top to game the offset is not. As with every RankGear factor, this value relates to position within a measured result set — it is a prioritization signal, not something that on its own makes a page rank.
Important considerations
- Despite “Bytes” in the name, this is a UTF-16 string offset, not encoded or transferred bytes.
- The detector recognizes only the enumerated all-lowercase or all-uppercase forms of H1 through H4.
- Mixed-case tag names (such as
<H1 >written as<H1>) or unusual whitespace between the tag name and its attributes can be missed. - The
99999value is a missing-tag sentinel, not a literal location in the document. - Correlation is not causation: this factor tracks a structural property of the markup, not a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.