Asset ownership decision · Entity SEO

Main entity selection gives an asset one clear subject to own from the title through the final route.

MIRENA begins with the query, audience, asset job, completion event, source context, and site plan. It compares candidate entities, selects one owner, assigns the remaining concepts to support or route roles, and turns the decision into hierarchy, placement, links, and briefing instructions.

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

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

The selected entity should explain the primary user task, sustain the whole asset, and remain distinct from the entities owned by nearby pages.

Asset job

The owner follows the reader task rather than the loudest term

MIRENA checks what the asset must explain, compare, support, or help the reader complete.

Site ownership

A strong entity can still belong to another approved asset

Candidate selection includes the hub, sibling pages, protected URLs, and existing canonical routes.

MIRENA rule

One owner must survive the whole asset

The main entity should remain clear in the title, opening, headings, support network, summary, and internal routes.

Evidence boundary: Google Search guidance emphasizes clear titles, helpful content, descriptive links, and structured data that matches visible content. It does not publish one main entity selection formula. MIRENA uses selection as an editorial, semantic, and site ownership decision.

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

MIRENA internal workflow

MIRENA selects the main entity through six wide workflow stages.

The workflow prevents choosing by phrase frequency, mixing several page owners, copying a result set label, or approving an entity before site ownership is clear.

Confirm the asset job and source context

MIRENA fixes the query, audience, completion event, offer, topic lanes, protected pages, and intended workflow.

Build the candidate entity set

Candidate people, products, organizations, concepts, processes, categories, and comparison frames are collected.

Test each candidate against the whole asset

MIRENA checks whether the entity can control the title, opening answer, major sections, support network, and final route.

Compare candidates with cluster ownership

Existing hubs, siblings, support pages, and canonical destinations are checked before ownership is assigned.

Select the owner and classify the remainder

One entity becomes primary while the rest become secondary, supporting, attribute, evidence, routed, rejected, or held.

Create the selection handoff

The approved owner moves into hierarchy, salience, placement, content briefing, internal links, and structured cues.

Six main entity selection tests

The winning entity must fit the page job, sustain the asset, and have a clear site role.

Page purpose test

Can the entity own the first user question and the completion event?

Whole asset test

Can the entity organize the title, opening, major sections, examples, and summary?

Search language test

Does the entity match the intended query frame without relying on vague or overloaded wording?

Support network test

Does it have enough relevant attributes, relationships, examples, evidence, and routes?

Sibling distinction test

Can the asset own the entity without duplicating or conflicting with a nearby page?

Evidence and business fit test

Is the entity supported by approved sources and aligned with the site, offer, and user journey?

Eight selection review dimensions

MIRENA tests candidate ownership from user need through production usefulness.

User task ownership

Which candidate best represents what the reader needs to understand or complete?

Query centrality

Which entity sits closest to the main search intent and answer?

Definition clarity

Can the entity be defined precisely without relying on several competing concepts?

Section capacity

Can the candidate sustain a logical sequence of major sections without drift?

Support network quality

Are the necessary attributes, relationships, examples, evidence, and routes available?

Sibling overlap

Would selecting the entity duplicate an existing hub, sibling, or protected asset?

Source readiness

Are identity, facts, relationships, claims, and examples approved and current?

Production usefulness

Can the entity drive the brief, headings, links, rewrite actions, and structured cues?

Eight main entity decisions

Every candidate receives an owner, support, route, removal, split, or hold decision.

Select as the main entity

Use when the candidate clearly owns the asset job and can control the full structure.

Keep as a secondary entity

Give the candidate a major supporting section without allowing it to replace the owner.

Keep as a supporting entity

Use it for context, example, process, evidence, comparison, or a focused subpoint.

Convert into an attribute

Treat a property, function, limit, or role as defining detail rather than another page owner.

Route to an existing sibling

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

Create a separate asset candidate

Use when the entity has distinct intent, enough depth, low overlap, and clear cluster value.

Reject the candidate

Remove entities that do not support the query, source context, or site plan.

Hold for evidence or ownership review

Pause when identity, support, canonical ownership, or business fit remains unresolved.

Examples

The stronger selection gives one concept ownership and turns the rest into bounded support roles.

Review targetDefinition asset

Weak choice

The asset tries to own entity salience, semantic SEO, internal links, schema, and Information Gain at once.

MIRENA selection

Entity salience owns the asset while hierarchy, placement, links, and markup explain how that center is built.

Review targetProduct asset

Weak choice

The product, company, founder, pricing, use cases, and workflow compete in the opening.

MIRENA selection

The product owns the asset while organization, creator, price boundary, functions, and use cases support it.

Review targetComparison asset

Weak choice

Two products compete as separate page owners with no shared comparison frame.

MIRENA selection

The comparison task becomes the owner while both products and the criteria receive secondary roles.

Review targetOlder URL

Weak choice

Several strong concepts were added over time and the original page owner is no longer clear.

Main job

Turns the owner and support roles into headings, sections, evidence, links, and writer instructions.

Relationship

Acts as the production handoff.

Ownership and production decisions

MIRENA decides whether a candidate owns the current asset, supports it, routes elsewhere, or leaves the plan.

Own the current asset

The entity best represents the query, user task, section capacity, and canonical site role.

Support the current asset

The entity defines, compares, demonstrates, proves, or routes the selected owner.

Own another asset

A hub, sibling, support page, or new candidate should carry the deeper task.

Reject or hold

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

Common mistakes

Weak selection chooses the most repeated phrase, allows several owners, or ignores cluster ownership.

Choosing by frequency

The most repeated term is not automatically the asset owner.

Choosing a topic that is too broad

A broad area may contain several entities and user jobs that need clearer ownership.

Letting two entities lead

A single asset needs one stable center unless the owner is an explicit comparison task.

Ignoring the whole asset

A candidate that fits the intro may fail to organize the major sections and final route.

Ignoring existing ownership

A strong candidate may already belong to another approved asset.

Selecting before evidence is ready

Identity, relationships, claims, prices, and examples should remain blocked when unsupported.

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

Review the route

Entity SEO routes

Move the selected owner into hierarchy, support selection, salience, and cluster design.

How does MIRENA choose the owner?

MIRENA checks the user task, query centrality, definition clarity, section capacity, support network, overlap, evidence, and production use.

What happens to the other entities?

They become secondary, supporting, attribute, evidence, routed, rejected, or held entities.

What does MIRENA return?

MIRENA can return the candidate register, selection matrix, ownership decision, support classification, placement handoff, and final routing record.

Next route

Give MIRENA the query, asset job, candidate entities, source context, internal inventory, and evidence. It returns the asset owner, support roles, hierarchy, routes, and handoff.

Use the Entity Led Brief when the ownership decision is ready to control the title, opening, headings, section roles, examples, 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