EEAT Mechanics

SegIndexer: How Google Tiers Its Index

Not all pages are indexed equally — the SegIndexer decides which tier (level) of the index a page lands in, from lightning-fast to slow storage

By Thomas Wawra· Published · Version 1.0· Systems referenced: SegIndexer / Tiers

What is SegIndexer?

Google doesn't index all pages equally quickly or cheaply. The SegIndexer decides which 'tier' (level) of the index a page lands in — from expensive, lightning-fast servers (for important pages) to slower, cheaper storage (for rarely needed pages).

The Google API leak confirmed a scaledSelectionTierRank field with values 0-32767. This 16-bit integer determines the tier: pages with high values (close to 32767) are stored on fast servers and served quickly. Pages with low values are stored on slower, cheaper infrastructure.

SegIndexer is fed by Q* (System 6), the site-level quality score. This creates a direct link: high Q* → high tier rank → fast serving. Low Q* → low tier rank → slow serving. The quality of the site determines not just ranking position, but also the speed at which the page can be served.

Claim-level evidence (3)
B
SegIndexer tiers the index: fast servers (important) to slow storage (rare).
Source: Google API leak — system description · SegIndexer / Tiers
B
scaledSelectionTierRank: 0-32767 (16-bit integer).
Source: Google API leak — field type and range · SegIndexer / Tiers · scaledSelectionTierRank
B
SegIndexer is fed by Q* (S6) — quality determines tier.
Source: Google API leak — fedBy: [6] · SegIndexer / Tiers

How tiering affects serving

The tier determines how quickly Google can serve a page in search results. A page in tier 32767 (highest) can be retrieved and included in search results in milliseconds. A page in tier 0 (lowest) might take hundreds of milliseconds — long enough that it might be excluded from results that need to be assembled quickly.

This creates a practical consequence: pages in low tiers may not appear in search results for time-sensitive queries, not because they're not relevant, but because they can't be retrieved fast enough. The SegIndexer is a serving optimization — it trades completeness for speed.

For large publishers, this means that not all pages are equal in Google's index. A high-quality page on a high-quality site will be served faster and more consistently than a low-quality page on the same site. The site-level Q* affects all pages on the site, and the SegIndexer translates that into serving speed.

Claim-level evidence (3)
C
High-tier pages are served in milliseconds; low-tier pages may take hundreds.
Source: Inference from tier architecture + serving latency · SegIndexer / Tiers
C
Low-tier pages may be excluded from time-sensitive queries — not relevance, but speed.
Source: Inference from serving speed optimization · SegIndexer / Tiers
C
Site-level Q* affects serving speed for all pages on the site.
Source: Inference from Q* → SegIndexer dependency · SegIndexer / Tiers

SegIndexer in the ranking architecture

SegIndexer has no downstream dependencies (feedsInto is empty). It is a terminal system — the tier assignment is the final step in the indexing pipeline. Once a page is assigned a tier, it stays there until the Q* changes or the page is re-evaluated.

The E-E-A-T dimension mapping shows SegIndexer as indirect for Authority (A: indirect). This is an unusual mapping: SegIndexer doesn't measure authority, but it responds to it. A page from an authoritative site (high Q*) gets a higher tier, which means faster serving, which means more visibility in search results — an indirect authority effect.

The architectural significance: SegIndexer creates a feedback loop between quality and visibility. High quality → high tier → more visibility → more traffic → more behavioral data → higher NavBoost → higher Q* → even higher tier. The loop is self-reinforcing for high-quality sites and self-diminishing for low-quality sites.

Claim-level evidence (3)
B
SegIndexer is terminal — no downstream dependencies.
Source: Google API leak — feedsInto empty · SegIndexer / Tiers
B
SegIndexer is indirect Authority (A: indirect) — responds to authority, doesn't measure it.
Source: Google API leak — dims: {A: indirekt} · SegIndexer / Tiers
C
Feedback loop: high quality → high tier → more visibility → more traffic → higher Q*.
Source: Architectural inference from Q* → SegIndexer → visibility chain · SegIndexer / Tiers

This Deep Dive is Schicht 2 content — interpreted and referenced, but always pointing back to Schicht 1 (the reference layer). Every claim is mapped to a source with an evidence code: [A] DOJ/sworn material, [B] leak field, [P] patent, [O] official Google communication, [C] interpretation.

© Thomas Wawra · Senior SEO Manager · wetter.com — a Funke Digital company