Corpus Engineering vs Relevance Engineering: How They Compare

“Credit to Michael King for the foundation. The distinction is on scope, not on substance. Both disciplines are needed. One sits inside the other.”

~ Cody C. Jensen, CEO, Searchbloom

Relevance Engineering, introduced by Michael King at iPullRank and articulated in the AI Search Manual, is the first practitioner discipline in the SEO industry to take embedding-driven, retrieval-driven, AI-generated visibility seriously and give it a working vocabulary. Corpus Engineering, introduced inside the MERIT Framework, is the broader systems-level discipline. Relevance Engineering sits inside Corpus Engineering as one of its six components.

This article is a head-to-head comparison: where the two disciplines overlap, where they diverge, and how they fit together. It is not an argument that Relevance Engineering is wrong. It is an argument that the scope, as currently defined, is incomplete, and that a broader systems-level frame is needed to cover the rest of the stack.

TL;DR

• Both disciplines are new to the SEO space. Relevance Engineering came first. Corpus Engineering is the broader synthesis that includes Relevance Engineering as one of six components.
• Relevance Engineering optimizes how content matches a query. Corpus Engineering optimizes the conditions that make matching possible in the first place: accessibility, semantic infrastructure, information gain, expansion, retrieval optimization, and lifecycle maintenance.
• The distinction is on scope, not on substance. The retrieval optimization component of Corpus Engineering is the same work Relevance Engineering describes. Where they diverge: accessibility, lifecycle, infrastructure, expansion, and maintenance.
• Failure modes are different. Relevance Engineering fails when content doesn’t match. Corpus Engineering fails when the corpus isn’t retrievable, complete, or durable. An excellent relevance engagement can still fail if the surrounding stack isn’t engineered.
• Different deliverables. A Relevance Engineering engagement produces semantic alignment audits, embedding analysis, query fan-out mapping, passage optimization. A Corpus Engineering engagement produces all of those plus corpus accessibility audits, semantic infrastructure design, entity relationship architecture, information gain assessment, expansion roadmaps, and drift monitoring.
• Both fit together cleanly. A practitioner doing Relevance Engineering work is doing a subset of Corpus Engineering. A practitioner doing Corpus Engineering necessarily includes the relevance optimization Relevance Engineering describes.

Credit Where Credit Is Due

Michael King saw the shift before most of the field was paying attention. He named it. He gave practitioners working concepts for it. Embeddings, query fan-out, retrieval precision, semantic alignment as practitioner concerns in this industry trace through his published work and the team at iPullRank.

That contribution is foundational. Without it, the conversation about AI search and AI visibility would still largely be stuck in keyword-density arguments and on-page checklists.

This article is not an attempt to one-up Relevance Engineering. The terminology and tactical work King has put into the field stands. Corpus Engineering builds on top of it.

Where I respectfully disagree is on scope.

Relevance Engineering, as articulated, treats semantic alignment and retrieval precision as the unit of practitioner work. Accessibility, lifecycle, infrastructure, expansion, and maintenance sit either as preconditions to relevance work or as separate concerns. My argument is that they are not preconditions. They are co-equal components of the same systems-level problem. Treating them as separate concerns leaves practitioners with structural blind spots: an excellent relevance engagement can ship into a corpus that is inaccessible, semantically incomplete, or drifting out of retrieval favor over time.

Corpus Engineering is the framework I propose to address the broader scope. Relevance Engineering sits inside it as the retrieval optimization component. The disagreement is not with what King has built. It is with where the line of the discipline gets drawn.

What Relevance Engineering Is

Relevance Engineering, as introduced and developed by Michael King at iPullRank, is the practice of optimizing content for semantic relevance and retrieval precision within modern retrieval systems.

The discipline is grounded in:

• semantic alignment between queries and content
• embedding-aware optimization
• retrieval precision in dense and hybrid retrieval systems
• passage-level and chunk-level relevance
• query fan-out and sub-query coverage
• LLM and AI Overview retrieval alignment

Relevance Engineering treats relevance as the unit of analysis. The question it answers:

When a retrieval system evaluates content for a query, does ours surface as the most semantically aligned match for the underlying query, sub-query, and intent?

Relevance Engineering is a genuine evolution beyond keyword-driven SEO. It operationalizes embedding behavior, vector similarity, and retrieval-system selection logic into practitioner work in a way no prior SEO discipline has done.

What Corpus Engineering Is

Corpus Engineering is the systems-level discipline of designing, structuring, expanding, maintaining, and optimizing a corpus for retrieval, semantic understanding, citation, ranking, and AI generation.

The discipline is grounded in six components:

• Corpus accessibility (rendering, crawlability, machine readability)
• Semantic structure (entity relationships, topical organization, semantic adjacency)
• Information gain (originality, uniqueness, citation-worthiness)
• Corpus expansion (semantic breadth, supporting evidence, external corroboration)
• Retrieval optimization (chunk structure, passage clarity, semantic precision)
• Corpus maintenance (drift management, freshness, entity evolution)

Corpus Engineering treats the corpus as the unit of analysis. The question it answers:

Across the entire information ecosystem we control or influence, is the corpus retrievable, accessible, semantically complete, citation-worthy, and durable across model evolution?

Relevance Engineering optimizes how content matches a query. Corpus Engineering optimizes the conditions that make matching possible in the first place.

Head-to-Head Comparison

Where They Overlap

Retrieval optimization sits at the intersection. Both disciplines:

• treat embeddings as a primary signal
• treat passage and chunk retrieval as critical
• focus on semantic alignment over keyword density
• recognize that retrieval systems behave differently from ranking systems
• accept that AI and search systems increasingly evaluate semantic ecosystems rather than isolated pages

The retrieval optimization component of Corpus Engineering is, in practical terms, the same work Relevance Engineering describes.

Where They Diverge

1. Accessibility

Relevance Engineering generally assumes content is accessible, parseable, and indexable. The discipline focuses on what happens once retrieval systems are evaluating it.

Corpus Engineering treats accessibility as a first-class component. Server-side rendering, clean HTML, parser compatibility, and indexation are explicit corpus-engineering concerns. If retrieval systems cannot render, crawl, or parse the corpus, no amount of semantic relevance work matters.

2. Lifecycle and Drift

Relevance Engineering generally addresses the present state: this content, this query, this retrieval moment.

Corpus Engineering addresses the temporal dimension. Corpus drift (the informational layer evolves), vector drift (embedding representations change as models update), and semantic-relationship drift are all explicit components. The corpus must be designed for durability across model upgrades, terminology shifts, and entity evolution.

3. Semantic Infrastructure

Relevance Engineering operates at the document, passage, and chunk level.

Corpus Engineering operates at the architectural level. Internal linking patterns, entity relationship design, semantic clustering, and topical hierarchy are corpus-level concerns that determine whether individual passages can be relevant in the first place.

4. Corpus Expansion

Relevance Engineering typically focuses on the corpus the practitioner already has.

Corpus Engineering includes the deliberate expansion of semantic breadth: supporting content, adjacent topics, related entities, external corroboration, and the construction of a semantically complete information ecosystem.

5. Information Gain

Both disciplines treat information gain as important, but the unit differs. Relevance Engineering evaluates information gain at the document or passage level. Corpus Engineering evaluates it across the entire corpus: does the ecosystem contribute non-commodity, citation-worthy, original information at scale?

6. Maintenance

Relevance Engineering tends to treat optimization as a forward-looking practice: improve relevance, ship.

Corpus Engineering treats maintenance as a continuous discipline. Corpora decay. Entities evolve. Models change embedding behavior. Without active maintenance, even an excellent corpus drifts out of retrieval favor.

How the Two Fit Together

The cleanest way to describe the relationship: Corpus Engineering is the parent discipline. Relevance Engineering is one of its six components, alongside accessibility, semantic structure, information gain, corpus expansion, and corpus maintenance.

The hierarchy:

MERIT Framework → Corpus Engineering → [Accessibility, Semantic Structure, Information Gain, Expansion, Retrieval Optimization (Relevance Engineering), Maintenance] → Tactical execution

A practitioner doing Relevance Engineering work is doing a subset of Corpus Engineering. A practitioner doing Corpus Engineering work necessarily includes the relevance optimization that Relevance Engineering describes.

Why the Distinction Matters in Practice

The two disciplines lead practitioners toward different deliverables.

Relevance Engineering engagements typically produce:

• semantic alignment audits
• embedding analysis
• query fan-out mapping
• passage-level optimization
• relevance scoring against retrieval systems

Corpus Engineering engagements produce all of the above, plus:

• corpus accessibility audit
• semantic infrastructure design
• entity relationship architecture
• information gain assessment at the corpus level
• corpus expansion roadmap
• drift monitoring and corpus maintenance cadence

The distinction also matters for organizations evaluating their visibility programs. A program built on Relevance Engineering alone will improve retrieval matching but may leave accessibility gaps, expansion gaps, and drift exposure unaddressed. A program built on Corpus Engineering covers the entire stack.

Both Disciplines Are New

Both Relevance Engineering and Corpus Engineering are new to the SEO, search, and digital marketing space. The two emerged in response to the same shift: retrieval systems and AI generation systems now evaluate semantic ecosystems, not just individual documents. Each is grounded in established information retrieval concepts. Neither replaces SEO; they extend it.

The terminology is new. The underlying mechanics are not. Embedding research, corpus linguistics, and retrieval evaluation have decades of academic history. What is new is the synthesis of those concepts into practitioner disciplines built specifically for the AI-retrieval era.

Relevance Engineering came first in this industry. King was the practitioner who recognized the shift, named it, and put a working vocabulary around it. Every serious AI-search practitioner today is operating with concepts King helped surface.

Corpus Engineering is the broader synthesis I propose to extend that work. It absorbs Relevance Engineering as one component within a systems-level discipline that also addresses accessibility, expansion, infrastructure, and lifecycle. The goal is not to compete with what King has built. The goal is to give practitioners a complete frame for the work that surrounds and supports the relevance optimization Relevance Engineering describes.

Frequently Asked Questions

What is Relevance Engineering?

Relevance Engineering, introduced by Michael King at iPullRank, is the practice of optimizing content for semantic relevance and retrieval precision within modern retrieval systems. It is grounded in semantic alignment, embedding-aware optimization, query fan-out coverage, and passage-level relevance work. Relevance Engineering treats relevance as the unit of analysis.

What is Corpus Engineering?

Corpus Engineering is the systems-level discipline of designing, structuring, expanding, maintaining, and optimizing a corpus for retrieval, semantic understanding, citation, ranking, and AI generation across modern search and language systems. It addresses six components: corpus accessibility, semantic structure, information gain, corpus expansion, retrieval optimization, and corpus maintenance. Corpus Engineering treats the corpus as the unit of analysis.

Who introduced Relevance Engineering?

Michael King at iPullRank introduced and developed Relevance Engineering. He was the first practitioner in the SEO industry to take embedding-driven, retrieval-driven, AI-generated visibility seriously and give it a working vocabulary. The conversation about AI search and AI visibility in this industry traces through his work and the team at iPullRank.

How are Relevance Engineering and Corpus Engineering different?

Relevance Engineering optimizes how content matches a query. Corpus Engineering optimizes the conditions that make matching possible in the first place: accessibility, semantic infrastructure, information gain, corpus expansion, retrieval optimization, and lifecycle maintenance. Relevance Engineering is one of the six components of Corpus Engineering. The distinction is on scope, not on substance.

Where do the two disciplines overlap?

Retrieval optimization is the intersection. Both disciplines treat embeddings as a primary signal, treat passage and chunk retrieval as critical, focus on semantic alignment over keyword density, and recognize that AI and search systems increasingly evaluate semantic ecosystems rather than isolated pages. The retrieval optimization component of Corpus Engineering is the same work Relevance Engineering describes.

Is Relevance Engineering wrong?

No. Relevance Engineering is foundational work that gave the SEO industry a working vocabulary for retrieval-aware practice. The argument is not that Relevance Engineering is wrong; it is that the scope, as currently defined, is incomplete. Accessibility, lifecycle, infrastructure, expansion, and maintenance are co-equal components of the same systems-level problem rather than preconditions to relevance work.

Should I implement Relevance Engineering or Corpus Engineering?

Both. A practitioner doing Relevance Engineering work is doing a subset of Corpus Engineering. A practitioner doing Corpus Engineering work necessarily includes the relevance optimization that Relevance Engineering describes. The distinction matters for evaluating visibility programs: a program built on Relevance Engineering alone may leave accessibility gaps, expansion gaps, and drift exposure unaddressed. A Corpus Engineering program covers the entire stack.

What deliverables differ between the two?

A Relevance Engineering engagement typically produces semantic alignment audits, embedding analysis, query fan-out mapping, passage-level optimization, and relevance scoring. A Corpus Engineering engagement produces all of those plus a corpus accessibility audit, semantic infrastructure design, entity relationship architecture, information gain assessment at the corpus level, corpus expansion roadmap, and drift monitoring with corpus maintenance cadence.

Are Relevance Engineering and Corpus Engineering replacing SEO?

No. Both extend SEO rather than replace it. Traditional SEO continues to matter for ranking eligibility. Relevance Engineering and Corpus Engineering address the parts of modern visibility that traditional SEO does not address: embedding behavior, retrieval precision, semantic infrastructure, and corpus lifecycle.

Where does Corpus Engineering fit inside the MERIT Framework?

The MERIT Framework defines what AI visibility requires across five pillars: Mentions, Evidence, Relevance, Inclusion, and Transformation. Corpus Engineering is the operating discipline beneath MERIT that engineers the corpus to satisfy those pillars. Relevance Engineering, in turn, sits inside Corpus Engineering as the retrieval optimization component.

The Bottom Line

If Relevance Engineering asks:

Is our content the most semantically aligned match for the query?

Then Corpus Engineering asks:

Is our corpus retrievable, accessible, complete, durable, and worth citing?

Both questions matter. The first sits inside the second.

Modern visibility is no longer about winning a single query. It is about engineering the conditions under which a corpus is retrievable, citation-worthy, and durable across the systems that increasingly mediate how information is found, cited, and generated.

Michael King opened the door on this conversation in the SEO industry by naming Relevance Engineering. The work I am doing with Corpus Engineering is to extend that conversation into the rest of the stack: accessibility, semantic infrastructure, expansion, information gain at the corpus level, and lifecycle maintenance.

Credit to King for the foundation. The distinction is on scope, not on substance. Both disciplines are needed. One sits inside the other.