Orient
Learn the language, page roles, evidence rules, and first route.
Main category hub · Transit network
Move through Internal Linking from first principles to governed practice.
The Internal Linking hub connects pages by meaning, page role, journey stage, proof need, support need, and next useful action rather than by loose keyword mention.
The hub is the main node for 16 complete assets. It gives beginners a clear first route, gives practitioners a production path, and gives advanced operators the controls needed to govern ownership, evidence, approval, maintenance, and scale.
16 complete assets
5 learning levels
5 entry states
One main category node
Beginner route
Understand semantic links, anchor intent, hubs, spokes, and orphan recovery.
Start with language, ownership, and the first useful decision.
Practitioner route
Turn approved decisions into a working output
Build only after the input, scope, and owner are clear.
Advanced route
Govern link depth, sitewide patterns, adjacency, route roles, priorities, refreshes, and large scale maintenance.
Govern evidence, dependencies, and long term quality.
Hub rule
Every asset earns a clear role and route
No child asset sits as an unowned archive item.
Start from the current state
Choose the route that matches the decision already in front of you.
The route selector moves a beginner, practitioner, or advanced operator into the smallest asset that can own the next decision. Every route remains visible without relying on fragile tabs.
I need the foundations
Recommended route
Start with Semantic Internal Linking, Anchor Text by Intent, and Hub and Spoke Linking.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need to audit the site
Recommended route
Use Internal Link Audit, Orphan Page Recovery, Broken Topic Paths, and Deep Link Distribution.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need route logic
Recommended route
Use Cluster Roles, Context vs Navigation, Sitewide vs Contextual, and the Adjacency Matrix.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need prioritization and governance
Recommended route
Use Link Depth, Page Importance, Prioritization, Variation, and Governance.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI am refreshing content
Recommended route
Use Internal Links for Refresh Projects and connect repairs to the rewrite plan.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetBeginner through advanced
The journey grows from orientation into system governance.
The levels are not credentials. They describe the complexity of the decision, the amount of evidence required, and the number of connected assets that must be controlled.
Frame
Choose ownership, intent, scope, inputs, and the correct workflow.
Build
Create the map, brief, draft, format, link route, or implementation.
Refine
Audit overlap, gaps, weak answers, structure, proof, and performance.
Govern
Control approvals, ownership, maintenance, refresh, policy, and scale.
Visual semantics · Transit network
The interface mirrors the way the category is meant to be understood.
Transit network is more than decoration.
The visual system gives the category one stable mental model. The hero shows the category center, the route selector shows the current state, the journey rail shows progression, the complete index shows every owned asset, and the connected hub section shows where the work moves next.
Color carries stage and category meaning. Repeated card geometry signals comparable choices. Larger nodes indicate parent ownership. Lines, rings, grids, or layers express relationships, sequence, evidence, and handoff without asking the reader to decode a decorative illustration.
The copy follows the same grammar. Every block names the job, the input, the decision, the output, and the route. The result is a page that can orient a beginner without flattening the system for an experienced operator.
CenterInternal Linking
EntryUnderstand semantic links, anchor intent, hubs, spokes, and orphan recovery.
DepthGovern link depth, sitewide patterns, adjacency, route roles, priorities, refreshes, and large scale maintenance.
MetaphorTransit network
Asset count16
Next routeEvidence decides
Complete child asset index
All 16 assets remain visible from the main node.
Search by title, task, stage, or concept. Filter by learning level without hiding the full category architecture from users or search systems.
Fixing Broken Topic Paths
Repair a focused failure without changing strong work outside the approved page, block, link, or system boundary.
Open the assetInternal Link Prioritization
Rank the available work by ownership, value, weakness, evidence, effort, risk, and dependency.
Open the assetInternal Links for Refresh Projects
Rebuild or update existing content through structure, intent, entities, proof, answer form, links, and controlled review.
Open the assetAnchor Variation Strategy
Use this Internal Linking asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetSitewide Links vs Contextual Links
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetLink Depth and Page Importance
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetDeep Link Distribution
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetContext Links vs Navigation Links
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetLink Routing by Cluster Role
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetAdjacency Matrix
Use this Internal Linking asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetInternal Link Governance
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetOrphan Page Recovery
Repair a focused failure without changing strong work outside the approved page, block, link, or system boundary.
Open the assetHub and Spoke Internal Linking
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetAnchor Text by Intent
Use this Internal Linking asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetInternal Link Audit
Diagnose the current asset, record evidence and severity, and route each failure into the smallest useful repair.
Open the assetSemantic Internal Linking
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetOperator field guide
Read the transit network as a working system.
The visual metaphor creates a memory structure for the category. Each part of the model represents a decision the operator must make, not a decorative label.
Name the origin
The transit network begins with the source page, the reader state, and the job already completed at that point.
A beginner should be able to state the current job in one sentence before opening a deeper asset. That sentence becomes the reference point for scope, evidence, page ownership, and the next route.
Assign the route role
Every link receives a route role such as orientation, explanation, proof, comparison, support, fallback, conversion, or next best answer.
The edge marks the point where a related topic stops supporting the current job and needs another page, block, workflow, policy, or hold state. This boundary prevents the hub from becoming a catch all archive.
Connect the destination
Anchors describe the value of the destination, while hubs, spokes, navigation, and contextual routes preserve page importance and progression.
The route should make the next action obvious to a beginner while preserving the evidence, dependencies, exclusions, and review burden an advanced operator needs.
Maintain the network
Audits, orphan recovery, broken path repair, refresh work, and route governance keep the network usable as pages change.
A completed handoff records what was accepted, what remains uncertain, who owns the next action, which trigger reopens the decision, and when the system should be reviewed again.
Worked progression
The same hub supports five levels of decision maturity.
The route becomes more connected as the operator gains context. The advanced path does not replace the beginner path; it adds evidence, dependencies, ownership, review, and maintenance.
Start with Fixing Broken Topic Paths, Internal Link Prioritization, Internal Links for Refresh Projects. The aim is to learn the category language, recognise the main asset roles, and avoid solving a structural problem with an unstructured content request.
Move into Fixing Broken Topic Paths, Internal Link Prioritization, Internal Links for Refresh Projects. At this level the operator defines what belongs in the current asset, what belongs elsewhere, which inputs are approved, and which decision must be completed before production begins.
Use Fixing Broken Topic Paths, Internal Link Prioritization, Internal Links for Refresh Projects. The practitioner produces a map, brief, block, rewrite, link route, answer form, schema graph, comparison, template, or policy action while keeping the approved boundary visible.
Review Fixing Broken Topic Paths, Internal Link Prioritization, Internal Links for Refresh Projects. Advanced work separates symptoms from causes, keeps alternative explanations visible, ranks repair priorities, and avoids changing strong parts of the system without evidence.
Use Fixing Broken Topic Paths, Internal Link Prioritization, Internal Links for Refresh Projects. Governance adds owners, approvals, versions, refresh triggers, exception rules, change records, measurement, and a safe route when the evidence no longer supports the existing model.
Why the main node exists
The hub holds the broad journey while child assets own focused depth.
The hub is a semantic and behavioral contract.
The parent node defines Internal Linking, shows the complete branch system, and explains how the parts connect. It does not absorb every child lesson. The child assets earn their own URLs by owning a narrower reader task, decision, process, comparison, audit, template, policy, or production stage.
That split creates a cleaner journey. A beginner can understand the category without reading every guide. A practitioner can jump to the owned task without losing the parent context. An advanced operator can inspect dependencies, overlap, evidence, and governance without turning the hub into an unstructured knowledge dump.
The internal links follow the same model. The hub links down to every core child. Children link back to the hub. Close siblings link across when the reader has reached the point where the relationship becomes useful. Connected category hubs receive the work when the next job changes discipline.
Six rules protect the hub and ring.
- One parent topic. The H1, opening, route selector, journey, and index stay centered on Internal Linking.
- Complete visibility. All 16 child assets remain accessible from the main node and are not hidden behind a shortened archive.
- Distinct ownership. Every child earns a focused job that the hub should not carry in full.
- Progressive depth. Beginner, guided, practitioner, advanced, and operator routes use the same system at different levels of decision complexity.
- Evidence before expansion. New pages, blocks, routes, claims, and policies require enough approved material and a clear owner.
- Maintenance after release. Live signals, product changes, platform changes, legal updates, and user feedback can reopen the model through a recorded review route.
Advanced operating controls
A complete hub is maintained as a system, not published as a one time archive.
Advanced use adds ownership, evidence, change records, review triggers, and route quality. These controls keep the category useful as the site, product, search environment, and user needs change.
Ownership
Every query, entity, page, block, link, policy, and output has one accountable home.
Evidence
Claims, examples, product facts, links, and search observations retain their source and confidence.
Boundary
Related work stays outside the asset when it changes the page job or exceeds the approved scope.
Approval
Pass, revise, hold, and block states remain visible through the production handoff.
Maintenance
Owners, dates, triggers, versions, and refresh actions keep the hub and child assets current.
Measurement
Live signals can support or challenge the plan, but one metric does not prove the cause.
Connected category hubs
Move across the operating system when the current category exposes the next job.
The connection is based on workflow dependency and user progression rather than topical similarity alone.
Topical Mapping
The Topical Mapping hub turns topics, URLs, queries, business goals, user states, and existing pages into a governed architecture with page roles, cluster homes, overlap controls, publishing order, and useful next routes.
Open the Topical Mapping HubEntity SEO
The Entity SEO hub gives every important concept a stable identity, role, hierarchy, attribute set, relationship network, placement plan, page owner, and route through the wider site.
Open the Entity SEO HubContent Briefs
The Content Briefs hub turns approved site and page decisions into a writer ready operating plan with page job, intent, entities, section roles, evidence, answer formats, internal links, exclusions, and approval controls.
Open the Content Briefs HubDrafting and Rewriting
The Drafting and Rewriting hub diagnoses why an asset fails, protects the approved page job, selects the smallest repair boundary, rewrites only what needs to change, and returns reviewed copy with evidence and next routes.
Open the Drafting and Rewriting HubQuestions
Internal Linking Hub questions.
Does every entity mention deserve a link?
No. The link must improve understanding, proof, progression, support, or action.
How are context links different from navigation links?
Context links respond to the local passage need. Navigation links provide repeated orientation or broad access.
What is a route role?
It explains why the link exists, such as orientation, proof, comparison, support, fallback, or conversion.
What does governance add?
It assigns owners, rules, limits, review triggers, exceptions, and maintenance records.
Next route
Start with the current state, choose the owned asset, and move only when the evidence supports the next stage.
MIRENA connects the category decision to source context, planning, production, review, internal routes, and the final handoff. The hub remains the main node as the category grows.
Founder access is €20 for each 30 day subscription period excluding VAT, with one seat and one active MIRENA instance. OpenAI account rules, plan charges, model access, availability, and usage limits remain separate.