Entity role structure · Entity SEO

Entity hierarchy gives one entity ownership and puts every supporting concept in the right level.

MIRENA selects the primary entity, classifies secondary and supporting entities, separates attributes and evidence, routes adjacent concepts to their owners, and turns the ordered stack into headings, sections, internal links, and structured cues.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

6 hierarchy levels6 MIRENA stages8 review dimensions8 hierarchy actions

PrimaryOne asset ownerThe entity the title, opening, headings, and summary must reinforce

SecondaryMajor support branchesThe closest concepts that define, compare, or develop the page owner

SupportingAttributes, evidence, and examplesThe local detail that gives sections depth

OutputAn ordered handoffHeading path, section roles, links, brief, rewrite, or split

Definition and evidence boundary

Entity hierarchy is the ordered role system that keeps the asset centered and the support useful.

MIRENA separates primary, secondary, supporting, attribute, evidence, and routed roles before it assigns prominence, placement, links, and structured cues.

Page owner

One primary entity should survive every simplification test

If removing an entity destroys the asset identity, that entity is a strong primary candidate.

Support roles

Secondary and supporting entities perform different jobs

Major sections develop secondary entities while examples, attributes, evidence, and questions provide local support.

MIRENA rule

Hierarchy must appear in the visible asset

The role system controls title, opening, headings, section order, repetition, links, and summary.

Evidence boundary: Google Search guidance emphasizes clear titles, helpful content, descriptive links, and structured data that represents visible content. It does not prescribe one fixed primary, secondary, and supporting entity template. MIRENA uses hierarchy as an editorial planning model tied to the query, asset job, source context, and site ownership.

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

MIRENA internal workflow

MIRENA builds entity hierarchy through six wide workflow stages.

The workflow prevents multiple page owners, equal weight entity lists, generic headings, attributes treated as topics, and supporting concepts trapped on the wrong asset.

Confirm the page job and candidate entity set

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

Choose the primary entity

One entity receives asset ownership based on query centrality, user task, canonical role, and site plan.

Classify secondary and supporting roles

Close concepts, attributes, evidence, examples, processes, and routed entities receive distinct functions.

Order the section path

MIRENA maps which secondary entity each major section develops and where local support belongs.

Check salience, placement, overlap, and ownership

The hierarchy is tested against title, opening, headings, proximity, repetition, internal routes, and sibling pages.

Create the hierarchy handoff

The approved role order becomes a heading plan, entity placements, support blocks, links, brief instructions, rewrite actions, or split decisions.

Six hierarchy levels

A useful hierarchy distinguishes the asset owner from major branches, local support, evidence, and routed depth.

Primary entity

The one concept the asset is built to own and explain.

Secondary entity

A close concept that deserves a major section because it defines or develops the primary entity.

Supporting entity

A concept, tool, example, process, or use case that adds local context.

Attribute entity or detail

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

Evidence entity

A source, person, organization, record, screenshot, dataset, or example that supports a claim.

Routed entity

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

Eight hierarchy review dimensions

MIRENA checks whether the role order is clear, stable, useful, supported, and visible.

Page ownership clarity

Can one entity be named as the asset owner?

Query alignment

Does the primary entity match the first user task and answer?

Secondary entity necessity

Does each major branch deserve a section and develop the page owner?

Supporting role fit

Do examples, tools, processes, and questions add depth without taking control?

Attribute distinction

Are properties and functions treated as defining details rather than competing topics?

Section order

Does the heading path move from the page owner into the closest support logically?

Placement and proximity

Do roles appear in the correct zones with their defining support nearby?

Cluster ownership

Do routed entities leave the asset before they create overlap or drift?

Eight hierarchy repair actions

Every role conflict becomes an elevation, demotion, regrouping, route, split, removal, or hold decision.

Select one primary entity

Choose the page owner and align the title, H1, opening, and summary.

Promote a secondary entity

Give a major supporting concept its own section and clear relationship to the primary entity.

Demote a competing entity

Move a related concept lower or route it elsewhere when it fights for control.

Convert a concept into an attribute

Treat a property, function, or limit as defining detail instead of a separate page topic.

Group local support

Keep examples, evidence, questions, and use cases inside the section they strengthen.

Reorder the heading path

Move from primary definition into secondary development and local support without drift.

Add or repair the internal route

Link routed entities to the approved assets that own deeper coverage.

Split, reject, or hold

Separate distinct page jobs and pause unsupported or unresolved entities.

Examples

The stronger hierarchy gives one entity ownership and turns the rest into bounded support roles.

Review target Entity salience asset

Flat hierarchy

Salience, hierarchy, attributes, placement, links, and schema appear as equal topic lanes.

MIRENA hierarchy

Salience leads; hierarchy, placement, attributes, links, and markup explain how that center is built and reinforced.

Review target Product asset

Flat hierarchy

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

MIRENA hierarchy

The product leads; brand and organization support identity, attributes support function, and pricing and use cases receive bounded sections or routes.

Review target Process asset

Flat hierarchy

Tasks, tools, evidence, owners, outputs, and links are mixed without role or order.

MIRENA hierarchy

The process leads; steps are secondary and inputs, owners, evidence, blockers, and outputs support each stage.

Review target Older URL

Flat hierarchy

Years of additions create several strong topics and no stable page owner.

Main job

Checks whether the live asset follows the approved role order.

Relationship

Finds competing, missing, overpromoted, or misrouted entities.

Ownership and production decisions

MIRENA decides whether each entity leads, supports, routes elsewhere, or leaves the hierarchy.

Lead the current asset

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

Support the current asset

The entity defines, develops, demonstrates, proves, or routes the page owner.

Route to another asset

Another approved page owns the entity or deeper user task.

Reject or hold

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

Common mistakes

Weak hierarchy gives every concept equal weight, confuses attributes with topics, or ignores page ownership.

Using a flat entity list

A list does not tell the writer which concept owns the asset.

Letting two entities lead

A single page needs one stable owner unless the page job is an explicit comparison.

Treating attributes as major topics

Properties and functions often belong near the entity they define.

Promoting every relevant concept

Broad relevance does not justify equal prominence.

Ignoring section order

Hierarchy should control how the explanation develops from top to bottom.

Ignoring cluster ownership

Some entities should leave through contextual links rather than remain on the page.

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

Review the route

Entity SEO routes

Move from hierarchy into prioritization, salience, placement, and execution.

How is hierarchy different from placement?

Hierarchy says what level the entity belongs to. Placement says where that level appears.

Can MIRENA repair hierarchy on an older page?

Yes. It can choose the page owner, reorder sections, demote or route side entities, and split distinct page jobs.

What does MIRENA return?

MIRENA can return the candidate register, hierarchy matrix, role plan, heading blueprint, brief insertions, and final handoff.

Next route

Give MIRENA the page job, query, candidate entities, source context, internal inventory, and evidence. It returns the entity hierarchy, heading blueprint, placements, routes, and handoff.

Use the Entity Led Brief when the ordered roles are ready to control the draft, or route a live URL into rewriting when several entities already compete for ownership.

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