Page led search coverage · Information Gain

Query gap analysis finds the relevant searches a page or cluster still fails to satisfy.

MIRENA starts with the page job, maps the nearby query family, reviews the result set, compares the current page and cluster, then routes each accepted gap into the current asset, an existing page, a new planning route, or a hold state.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 gap types6 MIRENA stages8 evaluation dimensions8 treatments

Page jobOne primary search taskExplain, compare, help choose, support, convert, or route

Query familyNearby searches that matterIntent, modifiers, questions, comparisons, use cases, and stages

OwnershipWhere the gap belongsCurrent page, existing page, new map route, merge, reject, or hold

OutputA ranked treatment planBrief, rewrite, map, link plan, or review state

Definition and research boundary

Query gap analysis is narrower than keyword research and more page specific than query expansion.

The review starts with the asset in front of you and asks which nearby searches should be answered, routed, split, merged, or rejected.

Current asset

The page or cluster is the comparison target

MIRENA does not build a broad keyword universe before the page job and current coverage are clear.

Search path

Intent, stage, context, and format shape the gap

A meaningful gap changes what the reader expects or what the page must do next.

MIRENA rule

Every gap needs ownership

The gap becomes a page block, an existing route, a new planning candidate, a merge, a rejection, or a hold.

Research boundary: Google’s current AI search guidance explains query fan out while also warning against creating separate content for every possible search variation. MIRENA uses query evidence to improve useful coverage and routing, not to manufacture a large number of thin pages.

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

MIRENA internal workflow

MIRENA audits missing page and cluster search paths through six wide workflow stages.

The workflow prevents inflated keyword lists, mixed intent pages, duplicated routes, and weak add on copy.

Set the primary query and page job

MIRENA fixes the main search, page role, audience, offer, source context, protected pages, and completion event.

Map the nearby query family

MIRENA collects intent layers, modifiers, comparisons, questions, problems, roles, use cases, formats, and next step searches.

Read the result set pattern

MIRENA records repeated subtopics, title modifiers, formats, comparisons, question shapes, and blind spots.

Compare the page and cluster

Every query path becomes covered, weak, missing, buried, duplicated, owned elsewhere, or unclear.

Score fit and choose treatment

MIRENA checks page job fit, intent difference, reader value, cluster fit, format need, overlap risk, and production effort.

Create the handoff

The ranked gaps receive a page role, owner, section or URL target, source need, link route, blocker, and next workflow.

Eight query gap types

Missing search paths often appear through intent, modifiers, comparisons, questions, and routing.

Missing intent layer

The page answers the basic query but misses comparison, commercial investigation, action, or support intent.

Missing modifier path

Audience, role, location, stage, price, template, example, checklist, workflow, or audit language changes the need.

Missing comparison angle

The reader needs differences, tradeoffs, criteria, and selection logic.

Missing question chain

The first question is answered, but the next relevant question remains open.

Missing problem query

The page explains the concept but does not address failure, risk, limitation, or poor fit.

Missing role or use case

A team, situation, workflow, or page type needs distinct application guidance.

Missing format expectation

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

Missing route or next step

The answer is adequate, but the reader cannot reach the next proof, comparison, support page, or action.

Eight evaluation dimensions

MIRENA decides whether the gap deserves a section, route, page, merge, rejection, or hold.

Page job fit

Does the query support the approved purpose of the current page?

Intent difference

Does the path represent a new user job or only a language variation?

Current answer quality

Is the query absent, weak, buried, split, or already resolved?

Format need

Does the answer require prose, a list, table, process, question, comparison, or example?

Cluster ownership

Does another approved page already own the deeper task?

Reader and business value

Will closing the gap improve progress and support the approved offer or workflow?

Overlap risk

Would the treatment duplicate the parent, sibling, or protected page?

Evidence and effort

Is there enough source support and production value to justify the work?

Eight query treatments

The query gap becomes a controlled page, cluster, or routing action.

Add to the current section

Use when the path supports the same answer and needs little new structure.

Create a direct answer block

Use when a focused question needs a compact answer and development.

Add a comparison or table

Use when criteria, fit, tradeoffs, or alternatives shape the decision.

Add a focused question or process

Use when the query needs a follow up answer or ordered workflow.

Route to an existing page

Use when another approved URL already owns the deeper task or proof source.

Create a sibling page candidate

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

Merge or reject

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

Hold for validation

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

Examples

The page decision becomes clearer when the weak pattern and MIRENA treatment are shown together.

Asset type Content brief page

Query gap

The guide covers the definition and fields but misses templates, scoring, handoffs, refresh work, and review flow.

MIRENA treatment

Keep close paths as blocks and route deeper brief types to the approved pages that own them.

Asset type Software page

Query gap

The page covers the product broadly but misses comparison, price sensitivity, role fit, workflow, and limitation queries.

MIRENA treatment

Add decision support where it fits and route distinct comparison or pricing tasks to separate owned pages.

Asset type Educational guide

Query gap

The page answers the head term but ignores problem queries and follow up questions.

MIRENA treatment

Add focused answers, examples, and next routes without mixing a different buying stage into the page.

Asset type Older ranking URL

Query gap

The page still covers the topic but serves only a narrow slice of the current search family.

Main job

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

Relationship

Receives query paths already owned by another URL.

Ownership and production decisions

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

Keep inside the current page

The path shares the same page job and needs a section or focused block.

Create a dedicated component

The path needs a comparison, process, question, example, or decision format.

Route to an existing page

Another approved URL already owns the deeper intent or support need.

Send to topical planning

The path 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 variation as a gap

Language variants often belong on the same canonical page.

Ignoring the cluster

A missing path on one page may already be owned elsewhere and need a link rather than more copy.

Mixing buying stages

Forcing commercial intent into a clearly educational page can weaken the page job.

Closing gaps with weak add on copy

A comparison, process, question, or table should use the correct format.

Creating pages without enough depth

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

Stopping at the ranked list

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

Accepted, held, rejected, blocked, and review needed gaps receive owners and next workflows.

Review the route

Review SERP consensus Compare novelty and redundancy Review entity attributes Review the scorecard method

Questions

Query Gap Analysis for SEO questions.

What is query gap analysis?

It is the process of finding relevant searches a page or cluster still does not satisfy clearly.

Is query gap analysis the same as keyword gap analysis?

No. Keyword gaps focus on phrases. Query gaps focus on missing intent, context, comparison, question, format, and routing paths.

Can one page cover every nearby query?

No. Some paths belong in the current page, while others need an existing route, separate planning, a merge, rejection, or hold.

How does MIRENA decide page ownership?

MIRENA checks page job, intent difference, answer quality, cluster ownership, overlap risk, reader value, evidence, and effort.

Can the method improve an older URL?

Yes. It can expose missing comparisons, questions, modifiers, formats, use cases, and internal routes.

What does MIRENA return?

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

Next route

Give MIRENA the primary query, current asset, cluster, source context, and search evidence. It returns the query family, gap matrix, treatments, ownership, and handoff.

Use the Information Gain prompt library for query intent, query gaps, treatment selection, 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