Local semantic grouping · Entity SEO

Entity proximity keeps the main concept close to the support that makes it understandable.

MIRENA identifies the page owner, selects the defining support, chooses the right local block, keeps attributes and relationships near the mention, controls passage crowding, and extends the same connection through sections and contextual internal routes.

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 Proximity is an editorial and structural model with a clear evidence boundary.

The target can be one sentence, a short paragraph, a section opening, a comparison, a process step, or a contextual route.

Local relationship

The support should arrive when the entity needs it

A definition, attribute, example, or comparison gains value when the connection is easy to see.

Readable grouping

Closer does not mean denser

Support can be distributed across a short sequence instead of crowded into one line.

MIRENA rule

Proximity must preserve one center

Supporting concepts deepen the local owner without taking control of the page or section.

Evidence boundary: Google Cloud documents entities, mentions, and salience in text analysis, while Google Search guidance emphasizes helpful content and descriptive links. No public Search documentation sets one ideal proximity window. MIRENA uses proximity as an editorial grouping 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 designs useful entity proximity through six wide workflow stages.

The workflow prevents keyword stuffing, overpacked openings, late definitions, distant examples, mixed section owners, and internal links without local context.

Confirm the local owner and question

MIRENA fixes the page entity, section entity, user need, source context, and the answer the local block must deliver.

Select the defining support set

Only attributes, relationships, examples, evidence, comparison criteria, and routes needed for that answer are kept.

Choose the local meaning unit

The support is assigned to a sentence pair, paragraph, component, section opening, process step, or contextual link.

Check order, spacing, and readability

MIRENA reviews whether the support arrives early enough, stays close enough, and remains easy to parse.

Control crowding, drift, and ownership

Extra entities, repeated attributes, mixed intents, and deeper topics are demoted, moved, routed, or held.

Create the proximity handoff

The approved grouping receives target placement, bridge copy, format, source need, link, owner, and review state.

Six proximity patterns

Useful closeness can appear in a definition, attribute block, comparison, process, example, or route.

Definition proximity

The entity and working explanation appear in the same opening unit.

Attribute proximity

The properties, functions, limits, inputs, and outputs sit close to the entity they define.

Comparison proximity

The compared entities, criteria, tradeoffs, and decision summary stay inside one coherent sequence.

Process proximity

Inputs, owners, gates, blockers, outputs, and handoffs appear inside the steps where they matter.

Example and evidence proximity

The scenario, source, or proof sits beside the claim or concept it supports.

Link proximity

The contextual route appears at the moment the reader reaches the deeper entity or next task.

Eight proximity review dimensions

MIRENA checks local grouping, order, readability, hierarchy, and route timing.

Local owner clarity

Does one entity lead the sentence, block, or section?

Support relevance

Does each nearby concept perform a defining, comparing, proving, applying, or routing job?

Relationship explicitness

Does the copy explain why the entities belong together?

Order

Does the entity appear before or with the support needed to understand it?

Spacing

Can the reader connect the mention and support without holding the idea across unrelated copy?

Readability

Does the grouping remain natural rather than cramped?

Salience balance

Do support entities deepen the center without taking it over?

Route timing

Does the link arrive when the current explanation creates the need for the next asset?

Eight proximity grouping actions

Each weak local relationship becomes a grouping, movement, explanation, format, route, or hold action.

Group the definition and entity

Keep the working explanation in the first useful local block.

Pull attributes closer

Move defining details into the paragraph or component where the entity is introduced.

Place the example beside the concept

Reduce the memory gap between explanation and application.

Build a focused comparison unit

Keep criteria, tradeoffs, and decision support beside the compared entities.

Use an ordered process block

Place inputs, roles, gates, failures, and handoffs inside the relevant steps.

Add a bridge statement

Explain how the support concept connects and why it enters now.

Move the contextual link

Place the route where the deeper task becomes relevant.

Demote, route, or hold extra support

Remove crowding and protect the local and page level owner.

Examples

The stronger version groups the right support without turning the passage into a term list.

Review targetOpening definition

Weak grouping

The entity, four related concepts, two links, and an example are packed into one long sentence.

MIRENA grouping

Define the entity in one sentence, add the closest attribute next, and move the example into the following block.

Review targetAttribute block

Weak grouping

Attributes are scattered across several unrelated sections.

MIRENA grouping

Group the defining properties into the section that owns the entity and route advanced depth elsewhere.

Review targetProcess step

Weak grouping

The owner and output are explained before the step, while the failure condition appears much later.

MIRENA grouping

Keep the task, owner, gate, failure, and output inside the same step component.

Review targetInternal route

Weak grouping

A sibling link appears beside a loose keyword mention.

Main job

Extends the entity relationship across the cluster.

Relationship

Creates page to page proximity at the right point in the reader journey.

Ownership and production decisions

MIRENA decides whether the support stays in the local unit, moves elsewhere in the asset, routes to a sibling, or leaves.

Keep in the local unit

The support is required for the immediate definition, answer, comparison, process, or proof.

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 support is irrelevant, repetitive, unsupported, private, or unresolved.

Common mistakes

Weak proximity work crowds sentences, front loads support, ignores hierarchy, or links from loose mentions.

Forcing a fixed distance

The correct grouping depends on the question, format, and reading flow.

Packing every related entity together

Closer support should still have clear roles and sentence structure.

Front loading the whole entity network

The opening needs only enough support to establish the page owner and frame.

Using co occurrence without explanation

Nearby names do not replace an explicit relationship.

Ignoring section ownership

Good local grouping can still sit in the wrong block.

Linking from the first mention

The route should appear when the reader understands why the deeper asset matters.

Accepted, held, rejected, blocked, and review needed grouping actions with owners.

Review the route

Entity SEO routes

Move from proximity into context windows, density control, section integration, and briefing.

How is proximity different from distance?

Distance diagnoses separation. Proximity designs the closer structure used to repair it.

Can proximity include internal links?

Yes. A contextual link can extend the entity relationship when it appears at the right moment.

What does MIRENA return?

MIRENA can return the local unit record, proximity matrix, component plan, section plan, link plan, and final handoff.

Next route

Give MIRENA the asset, primary entity, section jobs, source context, and internal routes. It returns the local groups, proximity repairs, route timing, and handoff.

Use the Entity Led Brief before drafting, or send a live asset into rewriting when the support is scattered, crowded, or introduced at the wrong moment.

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