Semantic planning model · Entity SEO

An entity map shows what an asset is about, what belongs around it, and how the pieces connect.

MIRENA builds the map before drafting. It extracts entities, assigns primary and supporting roles, attaches attributes, defines relationships, applies salience weights, maps section ownership, and connects the asset to the wider site through internal routes.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 map components6 MIRENA stages8 review dimensions8 map actions

CenterPrimary entityThe asset owner and the concept every section must support

NetworkEntities, attributes, relationshipsThe supporting meaning required for the page job

StructureWeights, sections, and routesWhere each item appears and which sibling owns deeper detail

OutputA map handoffBrief, topical map, internal links, rewrite, and schema cues

Definition and evidence boundary

An entity map is a relationship and ownership model, not a broad topic list.

MIRENA uses the map to keep one clear asset center while making the supporting entities, attributes, sections, links, and downstream outputs explicit.

Entity analysis

Detected entities still need editorial roles

Automated analysis can identify entities and mentions, while MIRENA decides which ones lead, support, route, or leave.

Structured representation

Types and properties can formalize visible relationships

Schema.org provides a flexible type and property model, but the visible content and asset role come first.

MIRENA rule

Every map node needs a reason and destination

An entity belongs because it defines, supports, compares, proves, routes, or structures the page job.

Evidence boundary: Entity detection and structured data can represent names, types, mentions, properties, and relationships. They do not choose the editorial hierarchy or guarantee Google Search outcomes. MIRENA uses source context, query intent, reader value, and site ownership to turn those inputs into a controlled map.

Google Cloud analyzing entities Google Cloud Entity reference Google link best practices Google structured data introduction Schema.org data model

MIRENA internal workflow

MIRENA turns entity evidence into an asset and cluster map through six wide workflow stages.

The workflow prevents term piles, equal weighting, missing attributes, implied relationships, orphaned sections, and maps that never reach the brief.

Confirm the asset job and source context

MIRENA fixes the query, audience, primary task, completion event, allowed topic lanes, protected pages, and downstream workflow.

Extract the candidate entity network

People, organizations, products, concepts, processes, attributes, evidence sources, and related pages are collected.

Assign entity roles and weights

Each item becomes primary, secondary, supporting, attribute, evidence, routed, blocked, rejected, or review needed.

Define attributes and relationships

MIRENA states what defines each entity and how the important entities connect, compare, depend, produce, or route.

Map sections and internal routes

Entities receive heading, section, example, proof, comparison, question, anchor, target, and ownership positions.

Export the map into production

The approved network becomes an Entity Led Brief, topical map row, rewrite instruction, link plan, and schema ready cue set.

Eight entity map components

A useful map connects entity roles to attributes, relationships, sections, and routes.

Primary entity

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

Secondary entities

The closest concepts that define, compare, or expand the primary entity.

Supporting entities

Examples, tools, processes, evidence, and adjacent concepts that add depth without taking control.

Attribute network

The properties, functions, limits, inputs, outputs, use cases, and descriptors that define the entities.

Relationship network

The explicit links between entities, including type, part, cause, use, ownership, comparison, and workflow.

Salience weights

The relative priority that controls prominence, section order, repetition, and placement.

Section assignments

The title, opening, headings, comparison, process, example, question, proof, and summary roles.

Internal routes

The hub, sibling, proof, support, conversion, and next workflow paths tied to the entity network.

Eight entity map review dimensions

MIRENA checks whether every map item has a role, evidence basis, place, and route.

Page job relevance

Does the entity directly support the query and completion event?

Role clarity

Is the item primary, secondary, supporting, attribute, evidence, or routed?

Relationship clarity

Is the connection explicit, directional, and useful?

Source support

Is the entity or relationship approved, observed, documented, or otherwise grounded?

Salience balance

Do weights protect one clear center and prevent support entities from taking over?

Section fit

Does each item appear where its role is actually explained?

Cluster ownership

Does the current asset own the depth or should it route to a sibling?

Downstream usefulness

Can the map drive the brief, links, rewrite, topical map, and schema cues?

Eight entity map actions

Every map problem becomes a network, section, ownership, or route decision.

Remove an irrelevant node

Delete entities that do not support the query, page job, or source context.

Merge duplicate concepts

Combine labels that represent the same entity or intent.

Elevate the primary entity

Strengthen its weight, opening, section path, and routing role.

Add a missing attribute

Define the property, function, limit, input, output, or use case the map lacks.

State a missing relationship

Explain how two entities connect instead of leaving the association implied.

Assign the correct section

Move an entity into the definition, comparison, process, example, evidence, or question block where it belongs.

Add an internal route

Link to the approved asset that owns deeper explanation, proof, or the next task.

Send a branch to topical planning

Separate a distinct intent or entity job that should not live inside the current asset.

Examples

The stronger map explains role, relationship, placement, and the next workflow.

Review target Entity Salience asset

Loose list

Entity salience, attributes, internal links, schema, semantic SEO, and headings appear as equal keywords.

MIRENA map

Entity salience leads; attributes, hierarchy, placement, links, and markup receive supporting roles and section assignments.

Review target Software product asset

Loose list

Product features, price, audience, use cases, founder, company, and integrations are mixed together.

MIRENA map

The product leads; brand, creator, functions, limits, use cases, pricing, and support routes receive distinct roles.

Review target Process asset

Loose list

Tools, tasks, team roles, evidence, outputs, and risks appear without direction.

MIRENA map

The process leads; inputs, owners, gates, blockers, outputs, and handoffs become explicit relationships.

Review target Site cluster

Loose list

Related concepts are assigned pages without a hub, hierarchy, or route logic.

Main job

Turns the map into section roles, evidence notes, formats, links, and writer instructions.

Relationship

Acts as the execution handoff.

Ownership and production decisions

MIRENA decides whether each entity belongs in the current asset, a linked sibling, or the wider site plan.

Keep inside the current asset

The entity supports the same user task and needs a section or component.

Route to an existing sibling

Another approved asset already owns the deeper entity or relationship.

Create a sibling candidate

The entity has distinct intent, enough depth, low overlap, and cluster value.

Reject or hold

The entity is irrelevant, unsupported, duplicated, private, or outside source context.

Common mistakes

Weak entity maps become keyword lists, equal weight networks, or diagrams with no production use.

Treating the map like a term list

A map needs roles, relationships, weights, placements, and routes.

Adding every adjacent topic

More nodes can dilute the page job and create overlap.

Ignoring attributes

Named entities remain vague without the details that define them.

Ignoring weights

Equal treatment leaves the writer and reader without a clear center.

Leaving relationships implied

A connection should be explained in the content and reflected in routes where useful.

Failing to export the map

The work is incomplete until the brief, links, rewrite, map row, or schema cues change.

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

Review the route

Entity SEO routes

Move from the local entity map into hierarchy, relationships, site architecture, and execution.

Does every entity on the map belong in the visible copy?

No. Some entities belong in links, evidence, structured data, another asset, a hold state, or nowhere.

Can MIRENA use an entity map for rewriting?

Yes. It can compare the approved network with a live URL and repair hierarchy, attributes, relationships, sections, and routes.

What does MIRENA return?

MIRENA can return the source record, role matrix, relationship network, salience plan, brief insertions, and final handoff.

Next route

Give MIRENA the asset job, query, source context, entity evidence, result pages, and site inventory. It returns the entity network, weights, sections, routes, and handoff.

Use the Entity Led Brief when the map is approved, or send distinct branches into topical planning when they need separate page 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