Coverage angle planning · Information Gain

Novel subtopic discovery finds the useful branch the result set still leaves thin.

MIRENA maps the result set baseline, identifies open space, creates candidate subtopics, checks query fit, reader value, evidence, format, and cluster overlap, then routes the strongest angle into the correct production job.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 candidate types6 MIRENA stages6 validation gates4 ownership decisions

BaselineWhat the result set already coversConsensus, crowded patterns, weak sections, and shared omissions

Open spaceWhere the field stays thinComparisons, decisions, attributes, objections, examples, and process

ValidationFit, value, evidence, and ownershipMIRENA rejects decorative or duplicated angles

OutputOne approved angle and routeSection, component, page, brief, refresh, or hold

Definition and research boundary

Novel subtopic discovery starts with a result set baseline and ends with a page decision.

The goal is not to collect fresh ideas. The goal is to find a useful branch the field still handles poorly and place it without creating drift or overlap.

Result set baseline

Open space appears only after common coverage is mapped

MIRENA separates required consensus, crowded repetition, weak support, and shared omissions.

Reader value

The branch must change understanding or choice

A useful subtopic adds a comparison, decision, example, attribute, objection, process, proof block, or route.

MIRENA rule

One strong branch is better than several loose extras

The winning angle receives a page role, format, evidence need, owner, and next workflow.

Research boundary: Google’s public guidance emphasizes helpful, reliable, people focused, unique, and valuable content. Gap and competitor tools can reveal thin coverage and related ideas, but MIRENA rejects angles that do not fit the query, page role, source context, evidence, or cluster ownership.

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

MIRENA internal workflow

MIRENA turns result set open space into one controlled subtopic decision.

The workflow prevents blank page brainstorming, random novelty, copied sections, and unnecessary URLs from entering the brief.

Confirm source context and page role

MIRENA fixes the query, audience, offer, user task, allowed lanes, protected pages, and page ownership boundary.

Build the result set baseline

MIRENA records repeated headings, definitions, comparisons, examples, questions, proof, formats, and next actions.

Identify the open space

MIRENA marks thin sections, weak answers, missing attributes, absent comparisons, ignored objections, poor examples, and shared omissions.

Create candidate subtopics

The open space becomes specific branches with a user job, target section, possible format, source need, and expected value.

Validate the candidates

MIRENA checks query fit, reader value, result gap evidence, page fit, source support, and cluster overlap.

Select and route the winner

The strongest angle becomes a section, component, existing page route, new page candidate, refresh action, rejection, or hold.

Eight candidate subtopic types

Useful openings often sit inside missing decisions, relationships, proof, and application.

Missing comparison angle

The field explains one route but does not contrast the nearest alternative or tradeoff.

Missing decision frame

The reader needs criteria, fit rules, thresholds, or rejection conditions.

Missing use case

A role, situation, workflow, audience, or page type changes the application.

Weak entity attribute

A missing property, constraint, role, or relationship changes interpretation.

Missing objection or limit

The result set explains benefits but avoids poor fit, risk, failure, or when not to use the route.

Missing example or evidence

The field stays abstract and needs a grounded scenario, source, comparison, or proof block.

Missing process or failure point

The steps exist but gates, owners, blockers, failures, and handoffs remain absent.

Missing format or next route

The idea needs a table, checklist, decision block, question set, visual aid, or continuation path.

Six validation gates

A candidate becomes useful only after it passes the MIRENA validation layer.

Query fit

The branch must support the main query rather than pull the asset into another intent.

Reader value

The branch must improve understanding, comparison, trust, choice, action, or continuation.

Result gap evidence

The opening must come from thin, weak, missing, or buried coverage across the result set.

Page and format fit

The branch must belong in the page role and work inside an appropriate component.

Source support

The angle needs enough evidence, examples, observations, or approved source material.

Cluster overlap

The branch must not duplicate an existing page or a sibling that should own the task.

Eight placement forms

The winning subtopic receives the smallest useful content or architecture form.

Add a focused section

Use when the branch adds a distinct answer but remains part of the current page job.

Add a comparison table

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

Add a best fit block

Use when the reader needs a clear condition for choosing the route.

Add a poor fit block

Use when the missing value is a limitation, objection, risk, or rejection rule.

Add a use case section

Use when a role, situation, or workflow needs application detail.

Add a focused question

Use when a genuine follow up question needs a compact answer.

Add a process or failure block

Use when the branch needs sequence, gates, owners, blockers, or handoffs.

Add an evidence or example block

Use when the page needs a concrete source, scenario, observation, or proof.

Examples

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

Asset type SEO content briefs

Weak result pattern

Most pages define the brief and list common fields.

MIRENA opening

Show how the brief changes for comparison pages, use case pages, refresh work, internal links, and result formats.

Asset type Internal linking

Weak result pattern

Most pages repeat anchor text and broad best practices.

MIRENA opening

Show how routing changes by cluster role, journey stage, page depth, proof need, and refresh priority.

Asset type Information gain

Weak result pattern

The field uses broad language about unique content.

MIRENA opening

Show how to map the baseline, validate an opening, choose the format, and route the production work.

Asset type Older ranking page

Weak result pattern

The asset still ranks but repeats the field and uses stale examples.

Main job

Reviews the finished asset across useful difference categories.

Relationship

Checks whether the chosen angle survived drafting and support.

Ownership and production decisions

MIRENA decides whether the angle belongs in a section, component, existing route, or new page.

Keep as a section

The branch strengthens the same intent and fits the parent page.

Create a dedicated component

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

Route to an existing page

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

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.

Chasing novelty that does not fit

An interesting angle can still weaken the page when it misses the query or user job.

Confusing phrases with subtopics

A wording variation does not automatically create new reader value.

Adding too many branches

Several weak extras can dilute the structure and hide the main contribution.

Ignoring cluster overlap

A strong branch may already belong to another page or deserve separate ownership.

Treating every gap as publishable

Some openings are too small, unsupported, or risky for production.

Leaving the winner as a note

The work is incomplete until the angle has a section role, format, evidence need, owner, and route.

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

Review the route

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

Questions

Novel Subtopic Discovery for SEO questions.

What is novel subtopic discovery?

It is the process of finding useful branches the current result set leaves thin, weak, buried, or missing.

Is novel subtopic discovery the same as keyword expansion?

No. Keyword expansion can supply ideas. Novel subtopic discovery validates a stronger coverage angle that changes the value of the asset.

How does MIRENA validate a subtopic?

MIRENA checks query fit, reader value, result gap evidence, page and format fit, source support, and cluster overlap.

Should every useful subtopic become a new page?

No. Many belong in a section, comparison, decision block, use case, question, process, example, or internal route.

Can the method improve an older URL?

Yes. One strong missing comparison, decision, attribute, example, process, or format can improve a refresh without a full rebuild.

What does MIRENA return?

MIRENA can return the open space record, candidate list, validation record, selected angle, brief or refresh insertions, and final handoff.

Next route

Give MIRENA the query, source context, current asset, cluster, and result pages. It returns the baseline, open space, validated angle, placement, and handoff.

Use the Information Gain prompt library for novel subtopics, unique angle selection, entity gaps, brief insertions, refresh planning, scoring, 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