Search path planning · Information Gain

Query expansion gaps reveal the search paths a page or cluster still does not serve well.

MIRENA maps the wider query network around a core topic, separates phrase variation from real intent branches, checks existing page ownership, and turns every accepted gap into a section, format block, internal route, sibling page decision, or hold state.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 path types6 MIRENA stages8 audit dimensions4 ownership decisions

Core queryOne page jobThe main intent and completion event

Query networkBranches and modifiersComparisons, contexts, questions, use cases, and decisions

OwnershipPage, block, link, or clusterThe gap receives the smallest useful home

OutputA controlled handoffBrief, map, link plan, rewrite, reject, or hold

Definition and research boundary

Query expansion gaps are larger than missing keywords and narrower than uncontrolled topic expansion.

The review asks which search paths belong to the current page, which need another format or link, and which deserve separate ownership.

Search intent

The same words can serve different user jobs

MIRENA checks the reason behind the query before it groups or separates a branch.

Semantic network

The path can be a relationship, comparison, use case, or next decision

The branch is reviewed as meaning and user progress rather than a phrase checklist.

MIRENA rule

Every accepted path needs an owner

A gap moves into the current page, an existing page, a new planning route, or a hold state.

Research boundary: Google’s public guidance emphasizes helpful, reliable, people focused, unique, and valuable content. Keyword and clustering tools can reveal related queries and result patterns, but MIRENA still validates intent, page ownership, overlap, and reader value before a branch enters production.

Google helpful content guidance Google AI search guidance Ahrefs search intent guidance Ahrefs keyword clustering guidance Surfer content gap guidance

MIRENA internal workflow

MIRENA finds and routes missing search paths through six controlled stages.

The workflow prevents large query lists, minor wording variations, and off topic branches from becoming unnecessary sections or URLs.

Confirm source context and core query

MIRENA fixes the audience, offer, page role, target query, allowed lanes, protected pages, and next workflow.

Build the query network

MIRENA collects comparisons, use cases, support questions, narrower contexts, entities, formats, and next step searches from supplied evidence.

Classify each branch

Every branch receives an intent, user state, semantic relationship, likely treatment, and confidence note.

Compare the network with the page and cluster

MIRENA checks what is covered, weak, missing, already owned, duplicated, or stranded across the site.

Choose ownership and treatment

The gap becomes a section, answer block, comparison, example, internal route, existing page route, sibling page candidate, rejection, or hold.

Create the handoff

MIRENA records the evidence, owner, page role, format, link path, blocker, review state, and approved next workflow.

Eight search path types

A useful query branch changes the reader need or the production decision.

Comparison path

The reader needs to compare the core route with the nearest alternative.

Specificity path

A narrower context, audience, location, stage, or constraint changes the answer.

Support question path

The main answer creates a follow up question the page or cluster leaves open.

Use case path

A role, situation, workflow, or page type needs a distinct application.

Entity relationship path

A missing attribute or relationship changes how the main concept is understood.

Format path

The query needs a table, process, question block, checklist, example, or decision component.

Next decision path

The reader needs criteria, rejection rules, proof, or the next action after the first answer.

Cluster support path

The current page is adequate, but the wider cluster lacks a supporting route or owned page.

Eight audit dimensions

MIRENA tests the branch before it becomes a content or architecture decision.

Intent difference

Does the branch express a genuinely different user job or only new wording?

User state

Does it serve a beginner, comparer, skeptic, implementer, buyer, or returning user?

Semantic relationship

How does the branch connect to the core entity, attribute, process, or decision?

Current coverage

Is the path already covered, weak, missing, buried, or split across the current asset?

Existing ownership

Does an approved URL already own the deeper task or evidence source?

Format need

Does the branch belong in prose, a list, comparison, process, question block, example, or route?

Overlap risk

Would a separate block or page duplicate the parent, sibling, or protected content?

Journey value

Does the path reduce friction and move the reader into the next useful decision or action?

Eight query treatments

The gap becomes a page action rather than a loose research note.

Add to the current section

Use when the branch supports the existing answer and does not create a new user job.

Create a direct answer block

Use when a focused question needs a compact answer and supporting explanation.

Add a comparison or table

Use when the branch changes choice, fit, criteria, or tradeoffs.

Add a grounded example or use case

Use when the branch needs context, application, or a reusable scenario.

Create an internal route

Use when another approved page already owns the deeper question or proof source.

Create a sibling page candidate

Use when the branch has distinct intent, enough depth, low overlap, and cluster value.

Merge or reject

Use when several branches express the same intent or drift outside source context.

Hold for validation

Use when evidence, demand, ownership, or page fit remains unclear.

Examples

The useful opening becomes clear when the weak pattern and production route are shown together.

Asset type Content briefs

Missing path

The core guide explains what a brief is and what fields it contains.

MIRENA route

Add or route comparison page briefs, refresh briefs, use case briefs, internal link briefs, and result format briefs according to page ownership.

Asset type Internal linking

Missing path

The page explains anchor text and broad best practices.

MIRENA route

Add cluster role, journey stage, proof path, support path, refresh priority, and next best route decisions.

Asset type Topical maps

Missing path

The page explains hubs and clusters but stops before page ownership.

MIRENA route

Add split, merge, parent, child, bridge, protected page, and build order decisions.

Asset type Information gain

Missing path

The asset defines useful difference in broad terms.

Main job

Plans source, target, anchor, reason, and journey value.

Relationship

Receives the paths owned by another approved URL.

Ownership and production decisions

MIRENA decides whether the path belongs in the current page, another page, or the map.

Keep inside the current section

The branch strengthens the same answer and needs no separate component.

Create a dedicated block

The branch needs a comparison, process, question, example, evidence, or decision component.

Route to an existing page

Another approved URL already owns the deeper search path.

Send to topical planning

The branch has distinct intent, enough depth, low overlap, and clear cluster value.

Common mistakes

Weak reviews expand the notes but fail to improve the page or workflow.

Treating every modifier as a new opportunity

Minor wording changes often belong on one canonical page.

Expanding before intent is clear

A larger list does not help when the primary page job is unresolved.

Ignoring existing page ownership

A missing path on one asset may already belong to another URL.

Confusing phrase variation with path variation

A different phrase is not automatically a different user need.

Creating pages without enough depth

A new URL needs distinct intent, support value, and low overlap.

Stopping at the gap list

The work is incomplete until every branch has a treatment, owner, route, and review state.

Every accepted, held, rejected, blocked, or review needed branch receives an owner and next workflow.

Review the route

Review SERP consensus Review novel subtopics Review query paths Review the scorecard method

Questions

Query Expansion Gaps for SEO questions.

What is a query expansion gap?

It is a missing search path around a topic that a page or cluster does not cover well.

Is a query expansion gap the same as a keyword gap?

No. A keyword gap can be a missing phrase. A query expansion gap is a missing intent branch, context, comparison, support question, decision, or continuation path.

Should every missing path become a new page?

No. Many paths belong in the current section, a focused block, an example, a question, or an internal route.

How does MIRENA decide page ownership?

MIRENA checks intent difference, depth, existing ownership, overlap risk, cluster value, and the page role before it recommends a new URL.

Can query expansion improve an older page?

Yes. It can expose missing comparisons, follow up questions, entity relationships, formats, internal routes, and sibling page needs.

What does MIRENA return?

MIRENA can return the query network, gap matrix, treatment plan, brief insertions, map or link route, and final handoff.

Next route

Give MIRENA the core query, source context, current page, cluster, and search evidence. It returns the query network, ownership decisions, treatments, and handoff.

Use the Information Gain prompt library for query gap analysis, query treatment, semantic clustering, brief insertions, topical planning, internal routes, and final handoff.

Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.

Open MIRENA Browse Information Gain prompts