Keyword Export to Topic Map | How MIRENA Creates Page Plans
MIRENAby Semantec SEO
Menu

Topical Mapping · Keyword to architecture

How MIRENA turns a keyword export into page ownership, roles, and publishing order.

Give MIRENA the keyword export, source context, current site inventory, result set notes, business priorities, audience, and protected pages. MIRENA cleans the input, groups by topic and intent, assigns page treatment and ownership, and returns a processed page inventory.

See the MIRENA process Review Topical Maps with MIRENA
MIRENA internal workflow Static decision model Human approval required No ranking guarantee
Raw inputKeyword exportRows show demand signals, not page decisions.
Core transformationPhrase to intent to ownerGrouping by wording alone is not enough.
Treatment setPage, block, merge, rejectNot every keyword receives a URL.
Final outputProcessed page inventoryThe export becomes a site plan.

Planning problem

A keyword export is raw search evidence. A topic map is the processed set of page, block, ownership, role, route, overlap, and publishing decisions built from that evidence.

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

Failure signal

Every modifier becomes a page

Tiny wording differences create thin and competing URLs.

Failure signal

Phrase similarity controls grouping

Queries with different jobs are merged while same intent variants split.

Failure signal

The export skips page roles

Every row becomes a blog post and the architecture stays flat.

Boundary: MIRENA does not turn every export row into a page. Query treatment depends on intent, answer shape, depth, page role, site fit, overlap risk, evidence, and the next route.

How MIRENA handles the work

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

Intake and clean the export

Record source, date, region, fields, duplicates, noise, and site fit.

Group terms by parent topic

Move from rows into topic families and potential cluster homes.

Classify intent and user job

Separate informational, comparative, commercial, transactional, navigational, and support needs.

Scan modifiers and facets

Identify audience, feature, location, price, problem, format, and stage signals.

Choose page or block treatment

Decide page, child page, section, question, table, snippet, merge, or rejection.

Assign page roles and owners

Give each approved query cluster one canonical home and page role.

Build parent and child relationships

Place hubs, children, comparisons, use cases, docs, templates, and examples.

Set publishing order and routes

Prioritize pages by fit, value, dependencies, overlap risk, and commercial support.

Create the brief handoff

Pass page purpose, role, query group, entities, links, exclusions, and warnings.

Decision record

MIRENA keeps the important fields visible through the handoff.

Decision field

Keyword group

The related query evidence.

Decision field

Parent topic

The broad cluster home.

Decision field

Intent

The dominant user job.

Decision field

Treatment

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

Decision field

Canonical owner

The approved page target.

Decision field

Priority and route

The build wave and next workflow.

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
  • Raw phrasesTopical map template, example, process, SEO, build, comparison
  • Parent topicTopical Mapping
  • Page decisionsHub, process page, template page, example page, comparison page
  • Block decisionShort cluster overview remains on the hub
  • Next routeProcessed page rows into content briefs

Review states

MIRENA returns an owned decision instead of an unqualified recommendation.

Review statePass

The export becomes clear page ownership, roles, routes, and order.

Review stateRevise

The topic groups fit but intent or page treatment is still weak.

Review stateHold

Source context, result set evidence, or current site inventory is missing.

Review stateBlock

The plan publishes directly from rows or duplicates an existing owner.

Connected workflow

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

Intent

Intent to Page Mapping

Choose the correct content treatment and owner.

Open the route
Dependencies

Topic Dependency Mapping

Sequence parents, support, and later pages.

Open the route
Architecture

Site Architecture for Semantic SEO

Place the processed rows in the full site model.

Open the route
Growth

Site Growth Model

Turn the map into publishing waves.

Open the route
Map

Topical Maps with MIRENA

Build the processed page inventory from the export.

Open the route
Brief

Content Briefs

Create writer instructions from approved map rows.

Open the route

Questions

Keyword Export to Topic Map questions.

What is the difference between a keyword export and a topic map?

A keyword export lists search phrases. A topic map turns those phrases into page ownership, page roles, clusters, block decisions, routes, and publishing order.

Should every keyword become a page?

No. MIRENA chooses among page, child page, section, question, table, snippet, merge, and rejection.

How does MIRENA stop overlap?

MIRENA groups by meaning and intent, assigns one canonical owner, and keeps close variants under that owner.

What does the final page inventory include?

It includes page label, parent hub, page role, intent, query group, overlap notes, internal routes, and publishing priority.

What follows the processed map?

Approved rows move into content briefs, examples, templates, internal links, and site growth planning.

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