Topical Mapping · Merger and migration

How MIRENA maps a site merger before redirects and rewrites begin.

Give MIRENA both site inventories, traffic and business notes, current taxonomies, page roles, redirects, internal links, protected URLs, product routes, and migration constraints. MIRENA finds topic collisions and builds the surviving structure before redirect mapping begins.

See the MIRENA process Review Topical Maps with MIRENA

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

First artifactCombined inventoryBoth sites are reviewed in one system.

Main riskTopic collisionsDuplicate intent matters more than folder names.

Order ruleMap before redirectsDestinations follow the new structure.

Final outputMigration handoffEvery URL receives a governed action.

Planning problem

A site merger topic map combines two or more page inventories into one topic system with surviving owners, page roles, URL actions, redirects, links, and rewrite priorities.

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

Failure signal

Both taxonomies survive

The merged site still behaves like two separate systems.

Failure signal

Redirects are planned by phrase match

Old URLs point to similar wording rather than the right role and intent.

Failure signal

Duplicate hubs remain live

Two parent pages compete for the same broad topic.

Boundary: MIRENA does not choose a surviving page from traffic alone. Intent ownership, role, evidence, links, business value, brand priority, history, and redirect safety remain in the decision.

How MIRENA handles the work

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

Combine both site inventories

Create one view of every URL, title, topic, role, value, link, and risk.

Ignore weak legacy taxonomies

Recluster from the topic, intent, audience, product, and page job.

Assign one role to every candidate

Compare hubs, spokes, use cases, docs, proof, templates, examples, product, and commercial pages.

Find topic collisions

Identify duplicate parent topics, queries, pages, examples, and commercial routes.

Choose the surviving parent structure

Select the strongest owners and create missing hubs where needed.

Assign one URL action

Keep, merge, split, redirect, retire, or rebuild.

Build the redirect plan

Point old URLs to the approved role and intent owner.

Rebuild internal routes

Replace both legacy link systems with the new parent, child, sibling, proof, and action paths.

Create rewrite and QA queues

Brief surviving pages, test redirects, and monitor cluster health after launch.

Decision record

MIRENA keeps the important fields visible through the handoff.

Decision field

Origin site

The source inventory.

Decision field

Surviving owner

The approved destination and page role.

Decision field

Collision type

Parent, intent, role, content, proof, route, or product.

Decision field

URL action

Keep, merge, split, redirect, retire, or rebuild.

Decision field

Redirect destination

The approved new owner.

Decision field

Migration state

Approved, revise, hold, block, test, or monitor.

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

CollisionTwo parent hubs for the same topic
Surviving ownerThe page with the clearer role, stronger support, and better route
Loser actionMerge unique value, then redirect
Link actionRebuild child links around the surviving hub
Next routeMerge brief, redirect QA, then cluster health review

Review states

MIRENA returns an owned decision instead of an unqualified recommendation.

Review statePass

One merged topic system owns every surviving intent and route.

Review stateRevise

The structure works but selected page or redirect actions need evidence.

Review stateHold

Traffic history, ownership, protected status, or redirect risk is unclear.

Review stateBlock

The plan keeps duplicate hubs or maps redirects before ownership.

Connected workflow

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

Legacy

Legacy Site to Processed Map

Use the single site restructure model for each source inventory.

Open the route

Growth

Site Growth Model

Plan how the merged site expands after launch.

Open the route

Health

Cluster Health Check

Review the merged branches after implementation.

Open the route

Architecture

Site Architecture for Semantic SEO

Define the target system before redirects.

Open the route

Map

Topical Maps with MIRENA

Create the merged page ownership and action model.

Open the route

Rewrite

Drafting and Rewriting

Repair surviving pages after the map is approved.

Open the route

Questions

Site Merger Topic Maps for SEO questions.

What is a site merger topic map?

It is the structure plan for combining two or more sites into one set of clusters, page roles, URL actions, redirects, and routes.

Is it the same as a redirect plan?

No. The topical map and ownership decisions come first. Redirects follow the approved structure.

How does MIRENA choose the surviving page?

MIRENA reviews intent, role, evidence, quality, links, business value, history, and migration risk.

What does MIRENA return?

MIRENA returns the merged map, surviving owners, page actions, redirects, link plan, rewrite queue, blockers, and QA states.

What happens after launch?

MIRENA routes the merged clusters into health checks, map refresh, internal link review, and monitored repair.

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