Concept first internal linking · Entity SEO

Entity led internal links connect one clear concept to the next page that genuinely deepens it.

MIRENA starts with the page owner and local section job, identifies the concept already grounded in the block, matches it to the most specific approved destination, writes natural anchor direction, checks spacing and reader value, and sends the decision into the brief or rewrite plan.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 link types6 MIRENA stages8 review dimensions8 production actions

ConceptOne clear local entityThe idea controlling the source block

ContextA grounded relationshipWhy the destination belongs at that point

RouteOne useful next pageThe sibling, hub, proof, support, or workflow owner

OutputA controlled link instructionSource, target, anchor direction, timing, and owner

Definition and evidence boundary

Entity led internal links are a concept first internal linking model with a clear evidence boundary.

The route should deepen the current thought, not interrupt the paragraph, introduce a random topic, or send the reader to a broad page when a tighter sibling owns the next task.

Local concept

The source block must already explain what the link is about

MIRENA does not treat a loose mention as sufficient context.

Destination ownership

The target should own the deeper entity or reader task

A specific sibling can be stronger than a broad hub when it matches the local need.

MIRENA rule

Every link must justify source, target, anchor, timing, and journey role

Links without a clear reader and cluster job are removed, moved, replaced, or held.

Evidence boundary: Google Search documentation recommends crawlable links and concise, relevant anchor text, but it does not publish one entity led linking formula or ranking score. MIRENA uses the method as an editorial, information architecture, and reader journey control.

Google link best practices Google helpful content guidance Google structured data introduction Google Cloud entity analysis Schema.org data model

MIRENA internal workflow

MIRENA plans entity led internal links through six wide workflow stages.

The workflow prevents links from loose mentions, generic anchors, broad destinations, crowded paragraphs, duplicated routes, and instructions that never reach production.

Confirm the page owner and local section jobs

Fix the main entity, section owners, query, audience, source context, completion event, and cluster role.

Map approved destination entities and page owners

Record hubs, siblings, support pages, proof assets, workflow pages, commercial routes, and protected destinations.

Identify grounded concept blocks

Review the opening, explanations, comparisons, processes, examples, evidence, questions, and closing transitions.

Match source concept to destination owner

Check the entity relationship, reader need, destination specificity, page ownership, overlap, and route timing.

Write anchor direction and spacing rules

Set natural anchor guidance, surrounding context, placement, priority, exclusions, and density controls.

Create the link handoff

Move accepted, moved, replaced, removed, blocked, and held links into the brief, rewrite, topical map, or link plan.

Eight entity led link types

A strong internal route can deepen identity, attributes, comparisons, processes, evidence, support, workflow, or the next reader task.

Definition link

Moves from a grounded concept into the page that owns the deeper definition or boundary.

Attribute or relationship link

Connects the entity to the page that develops a property, function, constraint, or connection.

Comparison link

Moves from a clear criterion or tradeoff into a focused alternative or decision page.

Process link

Connects planning to the workflow, implementation step, gate, or handoff it activates.

Evidence link

Connects a claim or example to the approved source, case, record, or evidence owner.

Support link

Routes the reader to the focused support page that owns the follow up question or problem.

Hub or sibling link

Returns the reader to the broader entity owner or the nearest related asset.

Next workflow link

Moves from explanation into the brief, rewrite, topical map, schema, support, or product workflow.

Eight entity led link review dimensions

MIRENA checks whether the concept, local context, destination, anchor, timing, spacing, ownership, and reader value align.

Concept clarity

Is the source block already clear enough for the reader to understand the linked idea?

Entity relationship

Does the target genuinely deepen, compare, prove, apply, or continue the current entity?

Destination specificity

Does the chosen page own the exact next task better than a broader destination?

Anchor fit

Can the link use natural wording that reflects the local concept and destination role?

Placement timing

Does the link appear after enough context and before the reader loses the connection?

Link spacing and density

Does the block remain readable without stacking several routes into one small area?

Page ownership and conflict

Does the target reinforce the approved hub, sibling, support, and canonical model?

Reader journey value

Does the route help the reader move into the next useful level of depth or action?

Eight entity led link actions

Each candidate becomes a keep, move, replace, rewrite, add, remove, space, or hold action.

Keep the current link

Use when concept, context, anchor, destination, timing, and journey value already align.

Move the link to a stronger concept block

Place the route where the entity or relationship is already grounded.

Replace the destination

Choose the specific sibling or support page that owns the deeper task.

Rewrite the anchor and surrounding context

Make the relationship clear without pasting a target phrase into the sentence.

Add a missing route

Connect a completed concept to the hub, sibling, proof, support, or next workflow page.

Remove a random or duplicate link

Delete routes that come from loose mentions, repeat the same job, or interrupt the block.

Redistribute crowded links

Move links into the sections where each concept becomes stable and useful.

Hold for ownership or destination review

Pause when the correct target, canonical owner, evidence, or page status remains unresolved.

Examples

The stronger pattern links from the point where the concept is clear and the destination owns the next job.

Review targetEntity order concept

Weak route

Every mention of entity links to the broad Entity SEO hub.

MIRENA route

Link the explanation of primary and supporting roles to Entity Hierarchy.

Review targetLocal meaning concept

Weak route

A generic read more link appears before the paragraph explains the idea.

MIRENA route

Ground the local meaning block, then link the concept to Entity Context Windows.

Review targetPlanning to production

Weak route

A product link appears in the middle of a technical explanation.

MIRENA route

Complete the planning concept, then link the transition to the Entity Led Brief or relevant workflow.

Review targetOlder asset rewrite

Weak route

Several links use generic anchors and broad destinations.

Main job

Places source, target, concept, anchor direction, and exclusions into the brief.

Relationship

Turns the route decision into production instructions.

Ownership and production decisions

MIRENA decides whether the concept routes to the hub, a sibling, a proof or support asset, or no destination.

Route to the hub

Use when the reader needs broader orientation or the main entity owner.

Route to a focused sibling

Use when the reader needs deeper coverage of the exact concept, attribute, comparison, or process.

Route to proof, support, or workflow

Use when the reader needs evidence, implementation, help, briefing, rewriting, or the next controlled action.

Remove or hold

Use when the candidate is random, duplicated, unsupported, crowded, conflicting, or lacks an approved target.

Common mistakes

Weak internal linking scans for phrases, links before the concept is clear, overuses hubs, or crowds one paragraph.

Linking from phrase matches alone

A repeated word does not prove that the local block and destination share the same entity job.

Linking too early

The route should deepen a concept after the reader understands it.

Sending every route to a broad hub

A focused sibling can own the next task more precisely.

Using vague anchors

Generic wording hides the relationship between the source block and target page.

Stacking several links in one small block

Crowding weakens readability and makes each route less distinct.

Ignoring the final next step

A strong asset should connect the completed explanation to the next useful page or workflow.

Accepted, moved, replaced, removed, blocked, and held routes with owners and next workflows.

Review the route

Entity SEO routes

Move from entity led link planning into semantic link architecture, anchor direction, briefing, and rewriting.

Should every entity mention receive a link?

No. A link should perform a real reader and cluster job and should not crowd or interrupt the content.

Should the hub always be the destination?

No. A focused sibling or support page is often the better route when it owns the exact deeper task.

What does MIRENA return?

MIRENA can return the destination register, concept inventory, link matrix, placement plan, brief insertions, and final handoff.

Next route

Give MIRENA the asset, page owner, entity map, page inventory, approved destinations, current links, and source context.

It returns the concept blocks, target routes, anchor direction, spacing rules, and handoff.

Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules, plan charges, model access, and usage limits remain separate.

Open MIRENA Review Internal Link Briefing