Supporting entity control · Entity SEO

Support entity selection gives every surrounding concept a clear job around the main entity.

MIRENA fixes the page owner first, builds the candidate support network, tests each entity against the local and full asset job, assigns a support function, removes duplicates and drift, and routes deeper concepts to the pages that own them.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 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

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

The selected support should define, qualify, compare, demonstrate, prove, sequence, answer, or route the primary entity without becoming another owner.

Page owner first

Support cannot be judged before the main entity is fixed

MIRENA compares every candidate with one clear asset owner and completion event.

Local job

A useful support entity performs one visible function

It can define, qualify, compare, demonstrate, prove, sequence, answer, or route.

MIRENA rule

Support must have a stopping point

The concept stays local, moves to another section, routes to a sibling, or leaves the plan.

Evidence boundary: Google Cloud documents entities, mentions, metadata, and salience in text analysis, while Google Search guidance emphasizes helpful content and descriptive links. No public Search documentation publishes one support entity selection formula. MIRENA uses selection as an editorial and site architecture decision.

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

MIRENA internal workflow

MIRENA selects support entities through six wide workflow stages.

The workflow prevents broad relevance lists, equal weighting, repeated support jobs, overloaded sections, and related concepts trapped on the wrong asset.

Confirm the main entity and page job

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

Build the candidate support network

Secondary concepts, attributes, relationships, examples, evidence, process roles, questions, and routes are collected.

Assign a support function

Every candidate receives a definition, attribute, comparison, process, example, evidence, question, or route role.

Test relevance, value, and ownership

MIRENA checks the local section job, reader gain, source readiness, density risk, overlap, and canonical owner.

Choose weight, placement, and boundary

Candidates become secondary, local support, attribute, evidence, routed, merged, rejected, or held.

Create the support selection handoff

The approved network becomes hierarchy, placement, section, link, brief, rewrite, and review instructions.

Eight support entity jobs

A support entity should define, qualify, compare, sequence, demonstrate, prove, answer, or route.

Definition support

The entity helps explain what the main entity is and what it is not.

Attribute support

The entity supplies a property, function, limit, input, output, or use case.

Comparison support

The entity creates criteria, contrast, fit, tradeoffs, or a decision frame.

Process support

The entity acts as an input, owner, stage, tool, blocker, output, or handoff.

Example support

The entity makes an abstract concept concrete through a grounded scenario.

Evidence support

The entity acts as a source, observation, record, screenshot, dataset, or proof.

Question support

The entity is required to answer a real follow up question or objection.

Route support

The entity points to the sibling page, proof source, support step, or next workflow.

Eight support entity review dimensions

MIRENA checks whether every candidate belongs, adds value, and has a clear owner.

Main entity relevance

Does the candidate directly deepen the selected asset owner?

Local question fit

Does the entity help complete a specific section or component job?

Distinct support job

Can the entity function be stated without vague relatedness?

Reader value

Does the candidate improve understanding, comparison, trust, action, or continuation?

Source readiness

Is the identity, relationship, example, claim, or evidence approved and current?

Density and drift risk

Could the entity crowd the passage, repeat another role, or pull the asset off topic?

Cluster ownership

Does the current asset own the depth or should a sibling page lead it?

Production usefulness

Can the entity drive a section, format, example, proof block, link, or structured cue?

Eight support entity decisions

Each candidate receives a role, weight, placement, route, merge, removal, or hold decision.

Promote to a secondary entity

Use when the candidate deserves a major supporting section.

Keep as local support

Use the entity inside one paragraph, component, example, question, or process step.

Convert into an attribute

Treat a property, function, limit, or role as defining detail rather than a competing topic.

Keep as an evidence entity

Use the source, person, organization, record, screenshot, or dataset to support a claim.

Route to a sibling asset

Link to the approved page that owns the deeper entity or user task.

Merge a duplicate support role

Combine candidates that perform the same function or represent the same entity.

Remove the candidate

Delete entities that add no useful meaning, evidence, comparison, or route.

Hold for evidence or ownership review

Pause when the source, relationship, privacy, or canonical owner remains unresolved.

Examples

The stronger support network gives every entity a function, placement, and boundary.

Review targetEntity Salience asset

Loose support

Attributes, proximity, internal links, schema, density, and Information Gain appear as a related term list.

MIRENA selection

Attributes define the entity, proximity controls grouping, links extend the route, and markup supports visible identity.

Review targetProduct asset

Loose support

Company, founder, price, features, use cases, integrations, and reviews all compete near the top.

MIRENA selection

Identity, creator, functions, plan boundary, applications, and evidence receive separate support roles and sections.

Review targetProcess asset

Loose support

Tools, people, tasks, evidence, outputs, and risks appear without order.

MIRENA selection

Each support entity becomes an input, owner, stage, gate, blocker, output, or handoff.

Review targetOlder URL

Loose support

New concepts were added over time because they were generally related.

Main job

Places each support entity in the section where its role becomes useful.

Relationship

Turns selection into local placement and explanation.

Ownership and production decisions

MIRENA decides whether the candidate supports the current asset, another asset, or no approved asset.

Support the current asset

The entity performs a clear function around the selected page owner.

Support another section

The entity belongs on the asset but inside a different local question or component.

Route to another asset

An approved sibling already owns the deeper entity or task.

Reject or hold

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

Common mistakes

Weak support selection keeps every related concept, gives equal weight, or ignores ownership and evidence.

Using broad relatedness

A nearby concept does not belong unless it performs a clear job.

Selecting support before the owner

The network cannot be judged without one fixed main entity.

Giving every support entity a section

Some concepts belong in a sentence, example, link, or nowhere.

Repeating the same support role

Several entities can create redundant definitions, examples, or proof.

Ignoring cluster ownership

Deep support may belong on a sibling page and need a contextual route.

Ignoring source readiness

Unsupported identities, relationships, examples, claims, and data should remain blocked.

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

Review the route

Entity SEO routes

Move the approved support network into hierarchy, integration, depth, and production.

How does MIRENA prevent support entities from taking over?

MIRENA fixes the main entity first, assigns roles and weights, checks drift, and routes deeper topics elsewhere.

Can a support entity become a separate page?

Yes, when it has distinct intent, enough depth, low overlap, and clear cluster value.

What does MIRENA return?

MIRENA can return the candidate register, selection matrix, role assignments, section plan, route plan, and final handoff.

Next route

Give MIRENA the main entity, asset job, candidate support network, source context, internal inventory, and evidence. It returns the support roles, placements, routes, and handoff.

Use the Entity Led Brief when the support network is ready to control sections, examples, evidence, questions, internal links, and structured cues.

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