a builder's codex
codex · operators · Mike King · ins_relevance-engineering-passage-level

The unit of optimization is the passage, not the page

By Mike King · Founder & CEO, iPullRank; creator of Relevance Engineering · 2026-04-22 · essay · How AI Mode Works (and How SEO Can Prepare)

Tier A · TL;DR
The unit of optimization is the passage, not the page

Claim

In AI-mediated search, optimization means engineering individual passages — H2-bounded blocks — to survive chunking and embed cleanly against likely query variants, not optimizing pages for keyword rank.

Mechanism

AI search systems run a retrieval pipeline: chunk the doc into passages, embed each, score embeddings against query fan-out (the model expands one query into many sub-queries), then assemble passages that match into a synthesized answer. A page that ranks #1 for a head term can still be invisible in AI Mode if its passages don't survive the chunker (too short, too long, poor entity density) or don't embed against the right sub-queries. The work is moved from page-level signals (links, meta tags, headings) to passage-level signals (size, entity shape, citation hooks, query-fan-out coverage).

Conditions

Holds when:

Fails when:

Evidence

"Answers are generated, not linked."

iPullRank reports from controlled studies: 34% higher citation retention versus baseline when pages were rewritten to the relevance-engineering spec. 67%+ of enterprise SEO budgets allocate to GEO in 2026. "Result-as-a-Service" contracts up 340% YoY.

— Mike King, How AI Mode Works, https://ipullrank.com/how-ai-mode-works, and AI Search Manual, 2026-04-22

Signals

Counter-evidence

Some operators argue the chunker behavior changes faster than content can be rewritten — every model generation alters embedding spaces and chunk sizes, so passage-level investments depreciate quickly. Engineering for one chunker can underperform when the model shifts. The right hedge is to optimize for human readability AND chunker survival; sole optimization for chunkers is fragile.

Cross-references

Open the interactive view → View original source → Markdown source →