Entity weighting and roles · Entity SEO

Entity prioritization decides which entity leads the asset and how every supporting role should follow.

MIRENA extracts the candidate entity stack, fixes one primary entity, scores the support network against the page job, assigns role and weight, checks cluster ownership, and translates those decisions into titles, headings, sections, links, and structured cues.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

6 entity roles6 MIRENA stages8 ranking dimensions8 priority actions

PrimaryOne page ownerThe entity the asset cannot lose without losing its identity

SupportingRanked contextual rolesSecondary, attribute, evidence, example, and route entities

WeightProminence and placementTitle, opening, headings, sections, links, and summary

OutputA role handoffHierarchy, placement, brief, rewrite, link, or hold

Definition and evidence boundary

Entity prioritization chooses the page owner and ranks every supporting entity by function.

The strongest asset does not give every related concept equal weight. It keeps one clear center and uses the remaining entities to define, compare, prove, route, or support that center.

Page purpose

The primary entity follows the approved asset job

The query, audience, completion event, and source context determine what the page must own.

Entity function

Supporting entities receive roles rather than vague relevance

Some define the entity, some compare it, some prove it, and some move the reader forward.

MIRENA rule

Weight must become visible structure

Priority is expressed through title, opening, headings, section order, repetition, links, and markup cues.

Evidence boundary: Google Cloud documents entity salience as text centrality, while Google Search guidance emphasizes clear titles, helpful content, descriptive links, and structured data that matches visible content. MIRENA uses prioritization as an editorial planning model rather than a disclosed Google Search scoring formula.

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

MIRENA internal workflow

MIRENA ranks the entity stack through six wide workflow stages.

The workflow prevents equal weighting, multiple page owners, generic support, misplaced entities, and priority scores that never affect the brief.

Confirm the page job and candidate entity set

MIRENA fixes the query, audience, completion event, source context, protected pages, and all candidate entities.

Select one primary entity

The page owner is chosen from the asset job, title intent, user task, and canonical site role.

Classify supporting functions

Remaining entities become secondary, supporting, attribute, evidence, routed, blocked, rejected, or review needed.

Score relevance, centrality, and value

MIRENA checks necessity, reader value, query fit, source support, cluster ownership, overlap risk, and production use.

Translate weights into structure

Priority controls the title, H1, opening, heading order, section depth, repetition, links, and summary.

Create the prioritization handoff

The approved role matrix becomes hierarchy, placement, support, brief, rewrite, internal route, and hold instructions.

Six entity roles

The entity stack needs one owner and several clearly bounded support roles.

Primary entity

The one concept the asset is built to explain, compare, support, or convert around.

Secondary entity

A close concept that defines, compares, or develops a major part of the primary entity.

Supporting entity

A concept, example, tool, process, or use case that adds depth without controlling the page.

Attribute entity or detail

A property, function, limit, input, output, use case, or relationship that defines an entity.

Evidence entity

A person, organization, source, record, screenshot, dataset, or example that supports the content.

Routed entity

A related concept that another approved asset owns and the current page should link to.

Eight entity ranking dimensions

MIRENA scores whether an entity should lead, support, route, leave, or wait.

Page job fit

Does the entity directly support the approved user task and completion event?

Query centrality

How close is the entity to the main search need and answer?

Reader value

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

Definition necessity

Would removing the entity make the asset incomplete or unclear?

Source support

Is the entity, attribute, relationship, or claim approved and current?

Cluster ownership

Does the current asset own the entity or should another page lead it?

Overlap and drift risk

Could the entity blur the page or duplicate a sibling?

Production usefulness

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

Eight entity priority actions

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

Elevate to primary

Use when the entity clearly owns the asset job and should lead the title, opening, and structure.

Keep as secondary

Give the entity a major section role without letting it replace the page owner.

Keep as supporting

Use the entity for context, example, process, evidence, or a focused subpoint.

Convert into an attribute

Treat the detail as a property or role rather than a competing entity.

Demote or compress

Reduce prominence when the entity is useful but overrepresented.

Route to another asset

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

Remove or reject

Delete entities that do not support the query, page job, evidence, or site plan.

Hold for evidence or ownership review

Pause when the entity role, source, or canonical owner remains unresolved.

Examples

The stronger priority model keeps one page owner and gives every supporting entity a function.

Review target Entity Salience asset

Unranked stack

Salience, attributes, hierarchy, placement, links, and schema receive equal attention.

MIRENA priority

Entity salience leads; hierarchy, placement, support, links, and markup receive distinct support roles.

Review target Product asset

Unranked stack

Product, brand, founder, company, pricing, features, and use cases compete in the opening.

MIRENA priority

The product leads; identity, creator, functions, plan boundary, and use cases support the product job.

Review target Comparison asset

Unranked stack

Both products, all features, audience types, pricing, and implementation details receive equal weight.

MIRENA priority

The comparison job leads; products are secondary and criteria, fit, limits, evidence, and decision rules support it.

Review target Older URL

Unranked stack

New topics were added over time and several entities now compete for control.

Main job

Checks whether the finished asset reflects the approved priority model.

Relationship

Finds overpromoted, missing, competing, or misrouted entities.

Ownership and production decisions

MIRENA decides whether each entity leads the asset, supports it, routes elsewhere, or leaves the plan.

Lead the current asset

The entity owns the primary query, page job, and completion event.

Support the current asset

The entity defines, compares, proves, demonstrates, or routes the primary entity.

Route to another asset

Another approved page already owns the entity or deeper task.

Reject or hold

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

Common mistakes

Weak prioritization gives every entity equal weight, chooses the loudest term, or stops before placement.

Choosing by repetition

The most frequent term is not automatically the page owner.

Letting two entities lead

A single asset needs one primary entity and one page job.

Using broad relevance

A related entity can still belong lower, elsewhere, or nowhere.

Ignoring source context

The entity stack must fit the approved site, audience, offer, and topic lanes.

Scoring without structural change

Weights should control title, headings, sections, links, and summary.

Ignoring cluster ownership

A high value entity can still belong on another approved page.

Accepted, held, rejected, blocked, and review needed entities with owners and routes.

Review the route

Entity SEO routes

Move the priority model into hierarchy, salience, placement, briefing, and audit.

Can one page have two primary entities?

A single asset should normally have one page owner. Distinct primary jobs may need separate pages or a comparison frame.

How does MIRENA rank entities?

MIRENA checks page job fit, query centrality, reader value, necessity, source support, cluster ownership, drift risk, and production usefulness.

What does MIRENA return?

MIRENA can return the candidate register, priority matrix, role assignments, weight and placement plan, brief insertions, and final handoff.

Next route

Give MIRENA the query, asset job, candidate entities, source context, internal inventory, and evidence. It returns the page owner, ranked entity stack, placements, routes, and handoff.

Use the Entity Led Brief when the priority model is ready to control the title, opening, headings, section roles, examples, internal links, and schema 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