A distinct user job needs a different structure, enough depth, a clear parent, and its own next route.
Topical Mapping · Cartographer · Guided
Decide when a query needs its own page and when it belongs inside a stronger one.
Query deserves granularity is the routing rule that matches the size of the page to the size of the intent. MIRENA compares the reader job, answer form, scope, depth, existing owners, and next route before it approves a new URL.
Protected centerpiece
Four outcomes stop a keyword list from becoming a bloated page list.
MIRENA assigns one outcome after the intent, scope, role, evidence, and overlap checks are complete.
The point supports the same intent and can be answered without creating a new ownership problem.
Two candidates solve the same job and should be combined under one canonical page.
The intent, proof, parent, route, or differentiation is not clear enough for approval.
How MIRENA handles the decision
The workflow keeps source context, ownership, evidence, and handoff connected.
Receive the query set
MIRENA receives the source context, candidate queries, existing URLs, page inventory, and the intended cluster.
Compare the reader job
The system compares the primary intent, user state, expected answer, task, and completion event.
Test page difference
MIRENA checks whether a new URL needs a different structure, depth, proof, page type, or action route.
Check existing ownership
The system compares live and planned pages for duplicate intent, entity overlap, role overlap, and link conflict.
Assign the route
The output names page, section, merge, hold, or reject, plus the parent, role, internal links, and next workflow.
Decision checks
MIRENA tests the signals that can change the structural outcome.
Would the reader arrive for a different result?
Would the answer need a different page shape?
Can the topic support a complete and useful page?
Would the reader need a different next step?
Is there already a page that should own the need?
Does the page strengthen the approved topic lane?
Worked example
A topical mapping query set
MIRENA would not treat every phrase as a separate URL.
Topical map definition, define topical map, and what is a topical map in SEO share the same reader job.
How to build a topical map needs a different structure and completion event.
Topical map template can earn a separate asset when the user wants a reusable working record.
A slight wording change with no new task stays inside the canonical owner.
Common failure modes
The wrong upstream decision can create clean looking content inside a weak architecture.
Phrase variation is not proof of a different intent.
Traffic estimates do not replace page purpose and ownership.
A clean new idea can still duplicate a live owner.
A page without a parent, links, or next step is not ready.
MIRENA handoff
The MIRENA granularity record
Page, section, merge, hold, or reject
The URL or planned page that owns the intent
The one job the approved page performs
Cluster home and architectural function
What belongs and what must hand off
Briefing, consolidation, splitting, or review
Connected Topical Mapping routes
Continue with the asset that owns the next decision.
Questions
Query Deserves Granularity questions.
What does query deserves granularity mean?
It is the rule used to decide whether a topic needs a standalone page or belongs inside a broader page.
Does every keyword variation need a page?
No. Variations that share the same reader job usually belong on one canonical page.
What makes a query strong enough for a separate page?
A distinct intent, different answer structure, enough depth, a clear cluster role, and a useful next route.
What happens when two proposed pages overlap?
MIRENA routes them to one owner, a merge, a narrower split, or a hold state.
Next route
Give MIRENA the source context and working evidence. MIRENA returns the governed map decision.
Founder access provides one seat and one active MIRENA instance for 30 days at €20 excluding VAT. OpenAI account rules and usage limits remain separate.