Topical Mapping · Intent and ownership

How MIRENA maps search intent to the right page, section, or answer block.

Give MIRENA the query set, source context, current pages, page roles, result patterns, and conversion routes. MIRENA classifies the intent, groups queries by the same job, assigns one primary home, and records the correct content treatment.

See the MIRENA process Review Topical Maps with MIRENA

MIRENA internal workflow Static decision model Human approval required No ranking guarantee

First decisionWhat does the user need?Intent comes before template choice.

Ownership ruleOne primary homeA second asset needs a distinct sub intent.

Treatment choicesPage, block, route, merge, rejectNot every query earns a URL.

Final outputIntent ownership recordThe decision enters the brief before drafting.

Planning problem

Intent to page mapping decides which asset owns each query job and whether the correct treatment is a page, child page, section, question, comparison, snippet, link target, merge, or rejection.

The job is structural. MIRENA reviews ownership, intent, role, evidence, dependencies, routes, user progression, and downstream production before a decision is accepted.

Failure signal

Several pages chase one intent

The site creates silent duplication and weak page ownership.

Failure signal

One page absorbs several jobs

The page loses focus and gives the wrong answer shape.

Failure signal

Templates lead the decision

The query is forced into a blog, product, or comparison format before the user job is understood.

Boundary: MIRENA does not create one page for every keyword and does not split pages on wording alone. The page earns a separate home through distinct intent, depth, route, proof, or user action.

How MIRENA handles the work

The internal process moves from evidence into governed page and route decisions.

Confirm source context

Set the audience, offer, allowed topic lanes, protected pages, and next workflow.

Classify the query job

Assign informational, comparative, commercial investigation, transactional, navigational, or support intent.

Group queries by meaning

Cluster queries that need the same answer and user progression.

Choose the content treatment

Decide page, child page, section, question, snippet, comparison, route, merge, or rejection.

Assign the primary home

Give the query cluster one clear owner and record any supporting assets.

Assign the page role

Hub, spoke, use case, comparison, product, pricing, docs, support, template, or example.

Check overlap and boundaries

Block duplicate intent and clarify nearby page roles.

Create the brief handoff

Pass intent, page job, format, exclusions, proof, and internal routes into the brief.

Decision record

MIRENA keeps the important fields visible through the handoff.

Decision field

Primary intent

The dominant user job.

Decision field

Secondary intent

A supporting need that does not change ownership.

Decision field

User state

Learning, comparing, skeptical, ready, stuck, or returning.

Decision field

Treatment

Page, child, section, question, snippet, merge, route, or reject.

Decision field

Primary home

The URL or approved page label that owns the cluster.

Decision field

Next route

Mapping, brief, rewrite, link work, or hold.

Illustrative output

The record shows what MIRENA decided and where the work moves next.

The example shows structure only. It is not a client result, live audit, ranking claim, or automatic implementation.

Example MIRENA record

Query groupMIRENA pricing and access
Primary intentNavigational and transactional
TreatmentOne pricing page with direct answer blocks
Primary homePricing
Supporting routeUse case and trust pages link into pricing

Review states

MIRENA returns an owned decision instead of an unqualified recommendation.

Review statePass

One primary home answers the user job with the right format.

Review stateRevise

The home is right but the page role or answer shape needs repair.

Review stateHold

Intent is mixed or the result set is unstable.

Review stateBlock

A proposed page duplicates an existing owner without a distinct job.

Connected workflow

The work moves into the next page that owns the decision.

Measure

Topic Coverage Score

Judge coverage against the assigned page role.

Open the route

Structure

Site Architecture for Semantic SEO

Place intent owners inside the wider site model.

Open the route

Navigate

Navigational Cluster Planning

Build fast destination routes for known intent.

Open the route

Compare

Compare Cluster Planning

Give evaluation intent a stable cluster.

Open the route

Brief

Content Briefs

Translate intent ownership into writer instructions.

Open the route

Map

Topical Maps with MIRENA

Process the query set into page ownership.

Open the route

Questions

Intent to Page Mapping for SEO questions.

What is intent to page mapping?

It is the process of matching a query job to the correct page, child page, section, question, snippet, or route.

Does every query need a page?

No. Many queries belong as sections, questions, comparison blocks, snippets, anchors, merges, or rejected ideas.

What is the one primary home rule?

Each query cluster receives one main owner. A second asset only exists when it serves a clearly different sub intent.

How does MIRENA use intent in a brief?

MIRENA carries the user job, page role, answer format, proof need, exclusions, and internal routes into the content brief.

What happens when intent is mixed?

MIRENA can split the page job, hold the decision, merge queries, or route a narrow need into a child page or section.

Next route

Give MIRENA the source context and working evidence. MIRENA returns the governed handoff.

The current Founder plan includes one seat and one active MIRENA instance for 30 days at €20 excluding VAT. OpenAI account rules and usage limits remain separate.

MIRENA output requires factual, editorial, legal, technical, and business review before publication or implementation.

Open MIRENA Review Founder access