Number of Bytes to First Match

Number of Bytes to First Match reports how early your keyword first appears in the page’s body HTML — specifically the UTF-16 offset of the earliest match from the run’s variation set, measured in script-free body HTML. Despite the name it is a character offset, not a network-byte count, and a value of 9999999 means no match was found rather than a real position.

What it measures

This factor reports the UTF-16 offset of the earliest match from the run’s generated variation set within the script-free body HTML. In plain terms, it locates the first place your keyword — or any of the variations RankGear generated for the run — shows up in the page’s markup, and returns how far into that markup the match sits. A smaller offset means the subject surfaces earlier in the HTML; a larger one means it appears further down.

How RankGear measures it

RankGear sorts the variation strings and joins them into a single regular-expression alternation, then finds the first captured match and looks up that captured text’s first location in the body HTML. The offset returned is a UTF-16 character position, not a count of network bytes. If the expression cannot be built, or no variation matches anywhere in the body, RankGear returns the sentinel value 9999999 to signal the absence of a usable match rather than a literal page position. The scan runs against body HTML with scripts removed, so surrounding markup counts toward the position — the offset is not measured against cleaned visible text.

How to optimize it

Make the page’s subject clear early in visible content and structural elements when doing so genuinely serves users. Treat this value as an observation of where your topic surfaces, not a target to game: do not inject keywords into markup or boilerplate merely to reduce the offset. Because the scan reads body HTML rather than cleaned text, artificially front-loading terms in non-visible markup distorts the measurement without helping readers.

Important considerations

• Despite the name, the value is a UTF-16 offset, not a network-byte count.
• The scan uses body HTML rather than cleaned visible text, so surrounding markup can affect the position.
• Variation strings enter the legacy regular expression unescaped.
• 9999999 means no usable match, not a literal page position.
• This is a measured signal that relates to position within a result set, not a lever that makes a page rank — correlation is not causation.

Related factors

• Inline JavaScript Kilobytes
• Number of HREF Lang Tags

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