Semantic separation review · Entity SEO

Entity distance finds where the main concept and the support that defines it have been pulled too far apart.

MIRENA maps the primary entity, marks its defining attributes, relationships, examples, evidence, and next routes, then checks how far those signals have drifted across paragraphs, sections, headings, and the wider cluster.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

6 classifications6 MIRENA stages8 review dimensions8 production actions

CenterOne clear entity or asset jobThe subject and reader task that control the review

SupportOnly relevant meaningAttributes, relationships, examples, evidence, and routes

DecisionA visible ownership boundaryKeep, move, route, split, remove, or hold

OutputA controlled handoffBrief, rewrite, map, link, schema cue, or review state

Definition and evidence boundary

Entity Distance is an editorial and structural model with a clear evidence boundary.

The problem is not a fixed word count. It is the loss of a clear local relationship between an entity and the support the reader needs.

Local meaning

The entity and its defining support should form a readable unit

The right distance depends on the question, format, and amount of explanation the reader needs.

Wider structure

Distance can grow across sections and internal routes

An asset can have a clear opening and still scatter attributes, examples, or sibling paths later.

MIRENA rule

Every distance finding needs a visible repair

The issue receives a target block, movement instruction, bridge, source need, owner, and review state.

Evidence boundary: Google Cloud documents entity mentions and salience in text analysis, while Google Search guidance emphasizes helpful content and descriptive links. Neither source defines one public entity distance score for Search. MIRENA uses distance as an editorial, structural, and routing model.

Google Cloud Entity reference Google Cloud entity analysis Google helpful content guidance Google link best practices Google structured data introduction

MIRENA internal workflow

MIRENA finds and repairs entity distance through six wide workflow stages.

The workflow prevents arbitrary spacing rules, overloaded openings, distant examples, fragmented sections, and internal links that arrive before the current concept is grounded.

Confirm the page job and primary entity

MIRENA fixes the query, audience, completion event, source context, page owner, and approved cluster boundary.

Map the defining support set

Attributes, relationships, examples, evidence, comparisons, questions, and next routes are attached to the entity they support.

Mark every important mention and support location

The title, opening, headings, paragraphs, components, summary, anchors, and sibling pages are recorded.

Classify the distance failure

Each issue becomes delayed definition, detached attribute, distant example, fragmented explanation, early route, or cluster separation.

Choose the smallest useful repair

MIRENA moves, groups, bridges, reformats, links, splits, compresses, or holds the affected material.

Create the distance handoff

The approved repairs receive target sections, source needs, owners, review conditions, and the next workflow.

Six distance failure types

Separation can weaken the definition, attribute, example, section, link, or cluster relationship.

Delayed definition

The entity appears before the asset explains what it means in the approved frame.

Detached attribute

A defining property, function, limit, input, or output sits far from the entity.

Distant example or evidence

The scenario or proof appears after the reader has lost the concept it supports.

Fragmented explanation

One answer is split across several sections with no clear bridge or summary.

Premature internal route

A link sends the reader away before the current entity and question are grounded.

Cluster separation

A support asset exists but the hub, sibling, or link path does not reveal the relationship.

Eight distance review dimensions

MIRENA checks separation from the first mention through the final route.

First mention clarity

Does the entity receive enough meaning when it first appears?

Attribute distance

How far are the defining properties and functions from the entity?

Example distance

Does the example sit beside the explanation it makes concrete?

Section fragmentation

Must the reader combine several blocks before the answer becomes complete?

Heading continuity

Do the headings move from entity to support in a logical sequence?

Internal route timing

Does the link appear after the need for deeper coverage becomes clear?

Readability cost

Would pulling support closer improve clarity without crowding the passage?

Cluster ownership

Does another asset own depth that should be reached through a cleaner route?

Eight distance repair actions

Each excessive gap becomes a movement, grouping, bridge, format, route, or hold action.

Move the definition closer

Place the working explanation in the first useful block after the entity appears.

Group defining attributes

Keep properties, functions, limits, and examples near the entity they define.

Move the example or evidence

Place the supporting material beside the claim, process, or decision it supports.

Combine fragmented blocks

Bring parts of one answer into one coherent section or component.

Add a bridge statement

Explain how the current entity connects to the next support concept or section.

Delay the internal route

Keep the reader on the current concept until the deeper need is established.

Create a sibling route

Send distinct depth to the approved page that owns it instead of widening the asset.

Hold for hierarchy or evidence review

Stop when the page owner, support role, source, or canonical route remains unresolved.

Examples

The stronger version keeps the concept, support, example, and next route inside one understandable path.

Review targetOpening block

Weak distance

The entity is named, then broad background fills several paragraphs before the definition appears.

MIRENA repair

Define the entity first, add the closest attribute, and delay wider context until the frame is stable.

Review targetComparison section

Weak distance

The compared entities appear early, while the criteria and recommendation arrive much later.

MIRENA repair

Keep the comparison frame, criteria, tradeoffs, and decision summary inside the same section sequence.

Review targetProcess section

Weak distance

The workflow names an input and only explains its role after several unrelated steps.

MIRENA repair

Place the input, owner, gate, output, and handoff inside the step where the relationship matters.

Review targetInternal route

Weak distance

A sibling link appears in the intro before the current topic has been explained.

Main job

Connects the asset to the hub, siblings, proof, and next task.

Relationship

Repairs distance across the site and reader journey.

Ownership and production decisions

MIRENA decides whether the support moves inside the block, elsewhere in the asset, to a sibling page, or into a hold state.

Keep inside the local block

The support directly defines or develops the current entity and question.

Move within the asset

The support belongs to the same page job but another section or component.

Route to a sibling asset

Another approved page owns the deeper entity or user task.

Remove or hold

The material is irrelevant, unsupported, duplicated, private, or unresolved.

Common mistakes

Weak distance reviews use rigid sentence counts, crowd the opening, or move support without preserving flow.

Using a fixed word rule

Different questions and formats need different amounts of local context.

Cramming every signal into one paragraph

Closer support should remain readable and ordered.

Moving support without a bridge

The reader still needs to understand how the pieces connect.

Ignoring hierarchy

Close placement around the wrong entity does not repair the page owner.

Linking away too early

The current answer should be grounded before the next route appears.

Treating cluster distance like page distance

A sibling page may be correct when the internal route makes the relationship visible.

Accepted, held, rejected, blocked, and review needed repairs with owners and workflows.

Review the route

Entity SEO routes

Move from distance diagnosis into proximity, local context, section structure, and rewriting.

How close should attributes sit?

They should appear close enough that the reader can connect them without crowding or breaking the passage.

Can entity distance affect internal links?

Yes. A link can appear too early, too late, or without enough local context to explain the route.

What does MIRENA return?

MIRENA can return the location record, distance matrix, regrouping plan, section plan, route repair, and final handoff.

Next route

Give MIRENA the asset, primary entity, source context, section outline, and internal routes. It returns the distance failures, regrouping plan, section repairs, and handoff.

Use the Entity Led Brief before drafting, or send a live asset into rewriting when definitions, attributes, examples, and routes have drifted apart.

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 the Entity Led Brief