Visible entity positioning · Entity SEO

Entity placement puts the primary entity and its support in the zones where their roles are clearest.

MIRENA ranks the entity stack first, then assigns the page owner to the title, H1, opening, heading path, summary, and key routes. Secondary and supporting entities move into the sections, examples, comparisons, questions, evidence, and links they actually support.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 placement zones6 MIRENA stages8 review dimensions8 repair actions

PrimaryHigh value placementTitle, H1, opening, early heading, summary, and key anchors

SecondaryMajor section placementH2, H3, comparison, process, table, and question blocks

SupportingLocal context placementExamples, evidence, checklists, explanations, and contextual links

OutputA zone handoffMove, group, demote, link, rewrite, or hold

Definition and evidence boundary

Entity placement turns an abstract hierarchy into a visible page structure.

MIRENA places entities by role and section need. It does not force every entity into the opening or repeat the primary entity in every heading.

Primary entity

The page owner belongs in the highest value zones

The title, H1, opening answer, early headings, summary, and key anchors should agree.

Supporting entities

Support belongs near the point it explains

Attributes, examples, comparisons, evidence, questions, and links should sit inside their owning sections.

MIRENA rule

Placement follows hierarchy and page job

Every entity receives a role, zone, proximity need, repetition rule, route, and owner.

Evidence boundary: Google Search guidance recommends clear titles, helpful content, descriptive links, and structured data that matches visible content. It does not prescribe a fixed entity placement formula. MIRENA uses placement as an editorial and structural model tied to the asset job, entity hierarchy, section purpose, and reader journey.

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

MIRENA internal workflow

MIRENA assigns entities to visible zones through six wide workflow stages.

The workflow prevents buried page owners, overloaded openings, scattered support, generic headings, distant attributes, and links that appear without a local reason.

Confirm the page job and entity hierarchy

MIRENA fixes the query, audience, completion event, primary entity, support roles, source context, and protected pages.

Define the high value and section zones

Title, H1, opening, H2, H3, body, comparison, process, example, evidence, question, summary, and anchors are mapped.

Assign entities by role

Primary, secondary, supporting, attribute, evidence, and routed entities receive the zones that match their function.

Check proximity, timing, and repetition

MIRENA reviews whether the entity appears early enough, close enough to support, and only as often as needed.

Detect placement conflict and drift

Buried primary entities, competing support, generic headings, mixed sections, distant examples, and random links are marked.

Create the placement handoff

The approved zones become heading notes, section instructions, bridge copy, examples, anchors, rewrite actions, and hold states.

Eight placement zones

Different entity roles belong in different attention and explanation zones.

Title and metadata zone

The primary entity and page job need one consistent, visible identity.

H1 and opening zone

The page owner should be defined or answered before broad context expands.

Early heading zone

Secondary entities should develop the closest attributes, comparisons, or process roles.

Body explanation zone

Supporting entities belong where their function and relationship are explained.

Comparison and table zone

Entities that shape fit, criteria, limits, and tradeoffs need a scanable structure.

Example and evidence zone

Proof entities and grounded examples should appear beside the claim they support.

Question and summary zone

Follow up entities and the primary conclusion should reinforce the same page center.

Internal link and structured zone

Routes and structured identity should support the visible entity model.

Eight placement review dimensions

MIRENA checks whether each entity appears in the right zone, at the right time, with enough context.

Role alignment

Does the placement reflect the entity priority and function?

Opening prominence

Is the page owner clear before the asset expands into support?

Section ownership

Does the entity appear inside the section that actually explains it?

Proximity

Are the defining attributes, relationship, example, and evidence nearby?

Timing

Does the entity appear after enough context and before the reader needs it?

Repetition value

Does each repeat add a new role or merely echo the label?

Flow and drift

Does the placement keep the page centered and the section sequence coherent?

Link and markup consistency

Do internal routes and structured data match the visible entity placement?

Eight placement repair actions

Each misplaced entity receives a move, group, demotion, explanation, link, or hold action.

Move the primary entity higher

Clarify the title, H1, opening answer, and early heading path.

Move support into its owning section

Place the entity where its relationship and function are explained.

Group attributes around the entity

Keep properties, limits, examples, and evidence close enough to form one unit.

Add a local explanation

State why the entity appears and what role it plays in the section.

Demote or compress a competing entity

Reduce prominence when support begins to take control of the asset.

Change the format

Use a comparison, table, process, checklist, example, question, or evidence block.

Add or reposition an internal route

Link to the deeper entity at the moment the reader needs it.

Hold for hierarchy or ownership review

Stop when the entity role, page owner, source, or canonical route is unresolved.

Examples

The stronger version places each entity where its role becomes clear and useful.

Review target Definition asset

Weak placement

The primary entity appears in the title but the opening uses broad SEO language and defines it later.

MIRENA placement

Define the primary entity in the opening, then place attributes and related concepts in the next sections.

Review target Comparison asset

Weak placement

Products, features, pricing, audience, and recommendations all appear in the intro.

MIRENA placement

Lead with the comparison job, then place products, criteria, fit, limits, and decisions in dedicated zones.

Review target Process asset

Weak placement

Tools, owners, evidence, outputs, and links appear before the ordered steps.

MIRENA placement

Assign each entity as input, stage, gate, blocker, output, or handoff inside the relevant step.

Review target Older URL

Weak placement

Years of additions leave the page owner buried and support entities scattered.

Main job

Checks live title, opening, hierarchy, support, placement, links, and structured consistency.

Relationship

Verifies the finished placement model and routes repairs.

Ownership and production decisions

MIRENA decides whether the entity belongs in the current zone, another section, a sibling asset, or a hold state.

Keep in the current zone

The placement matches the entity role and section job.

Move within the asset

The entity belongs on the page but in another section or component.

Route to a sibling asset

Another approved page owns the deeper entity or user task.

Remove or hold

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

Common mistakes

Weak placement front loads everything, buries the page owner, scatters support, or repeats labels without new work.

Putting every entity in the opening

The first block should establish the page owner and only the support needed for the answer.

Using headings without entity roles

Generic headings hide what each section is meant to develop.

Separating attributes from the entity

Defining details lose value when they appear far away.

Repeating the primary entity mechanically

Contextual continuity matters more than forced phrase repetition.

Adding links before the need appears

The route should arrive when the reader is ready for the deeper task.

Treating structured data as a placement repair

Markup supports visible content but does not fix a scattered asset.

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

Review the route

Entity SEO routes

Move from placement into prioritization, integration, briefing, and live asset repair.

How is placement different from prioritization?

Prioritization decides role and weight. Placement assigns the visible location.

Can MIRENA repair entity placement on an older URL?

Yes. It can move the page owner higher, regroup support, rebuild headings, and repair links and structured consistency.

What does MIRENA return?

MIRENA can return the role record, zone inventory, placement matrix, heading plan, route cues, and final handoff.

Next route

Give MIRENA the asset, entity hierarchy, source context, section outline, internal inventory, and evidence. It returns the zone plan, entity moves, headings, routes, and handoff.

Use the Entity Led Brief before drafting, or send the placement plan into rewriting when a live asset already has buried, scattered, or competing entities.

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