Semantic connection model · Entity SEO

Entity relationships explain how the concepts around a topic connect, influence, compare, and route.

MIRENA starts with one primary entity, selects the supporting network, states each important connection, checks direction and evidence, places the explanation inside the correct section, and reinforces deeper relationships through contextual internal links.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 relationship types6 MIRENA stages8 review dimensions8 repair actions

NodesEntities with clear rolesPrimary, secondary, supporting, attribute, evidence, and routed entities

EdgesConnections with directionType, part, cause, use, comparison, source, ownership, and route

ContextThe relationship is explainedSection fit, proximity, evidence, example, and reader value

OutputA relationship handoffBridge copy, placement, links, brief, rewrite, or hold

Definition and evidence boundary

Entity relationships give a topic structure by making the connections between entities explicit.

The relationship must support the query and page job. A vague association or a list of nearby concepts is not enough.

Entity analysis

Systems can identify entities and mentions

Google Cloud documents entities, mention types, metadata, and salience inside text analysis.

Structured representation

Schema.org models entities through types and properties

The data model can represent visible relationships after the content and identity are clear.

MIRENA rule

Every important edge needs a visible explanation

The relationship receives a type, direction, source, section, example, link, and owner.

Evidence boundary: Google Cloud Natural Language and Schema.org documentation show ways to identify and represent entities, mentions, properties, and relationships. They do not disclose one standalone Google Search ranking factor for entity relationships. MIRENA uses the concept as a content structure, clarity, internal link, and structured consistency model.

Google Cloud analyzing entities Google Cloud Entity reference Google helpful content guidance Google link best practices Schema.org data model

MIRENA internal workflow

MIRENA identifies and explains entity relationships through six wide workflow stages.

The workflow prevents loose associations, directionless links, unsupported claims, mixed intent sections, and relationship notes that never reach the draft.

Confirm the page job and primary entity

MIRENA fixes the query, audience, asset role, source context, completion event, and one entity that must lead.

Extract the supporting entity network

Secondary, supporting, attribute, evidence, product, person, organization, process, and routed entities are collected.

Classify relationship type and direction

Each connection becomes type, property, part, cause, use, comparison, source, ownership, output, or route.

Check evidence and reader value

MIRENA confirms why the relationship is true, relevant, useful, and safe to publish.

Assign section, proximity, and internal route

The relationship receives the heading, paragraph, comparison, process, example, question, anchor, and target it needs.

Create the relationship handoff

The approved edges become bridge copy, source notes, formats, links, brief instructions, rewrite actions, or hold states.

Eight relationship types

Entity connections can define, contain, cause, enable, compare, source, own, or route.

Type and category

One entity is a type, class, instance, or category of another.

Property and attribute

A property, role, state, feature, or characteristic helps define the entity.

Part and whole

A component belongs inside a product, system, process, organization, or cluster.

Cause and enable

One entity changes, enables, limits, prevents, or produces another.

Use and workflow role

A person, product, tool, input, or process performs a role inside a task.

Comparison and contrast

Two entities need criteria, fit, tradeoffs, limits, or selection logic.

Source and output

An entity provides evidence, data, input, approval, result, or handoff material.

Ownership and route

A person, organization, page, hub, sibling, or workflow owns the deeper task.

Eight relationship review dimensions

MIRENA checks whether the connection is relevant, explicit, directional, supported, and correctly placed.

Page job relevance

Does the connection help the asset explain, compare, prove, decide, or route?

Relationship explicitness

Does the copy state the connection rather than leave it implied?

Direction

Is it clear which entity acts, owns, contains, enables, produces, or routes?

Source support

Is the relationship documented, visible, observed, or otherwise approved?

Proximity

Are the entities and explanation close enough to form one clear unit?

Reader value

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

Ownership

Does the current asset own the depth or should it route elsewhere?

Link and markup fit

Should the relationship be reinforced through a contextual link or visible structured data?

Eight relationship repair actions

Every weak edge becomes an explanation, placement, format, link, removal, or hold decision.

State the relationship directly

Add the sentence that names the connection and why it matters.

Add direction and role

Clarify who acts, what changes, what belongs, or where the output moves.

Move the entities closer

Place the names, attributes, and explanation inside one coherent section.

Add attributes or an example

Show what each entity contributes and how the relationship works in practice.

Use a comparison or process

Choose a format that makes contrast, sequence, dependency, or handoff clear.

Add a contextual internal link

Route deeper meaning to the approved asset that owns the relationship.

Remove a false or weak connection

Delete associations that do not support the query, evidence, or page job.

Hold for evidence or ownership review

Stop when the relationship is unverified, private, duplicated, or disputed.

Examples

The stronger version explains the relationship, direction, and production value.

Review target Entity salience and placement

Loose association

The concepts appear together because both relate to entities.

MIRENA relationship

Prioritization sets the weight, salience protects the center, and placement assigns the visible zones.

Review target Information gain and evidence

Loose association

The page mentions evidence as another Information Gain term.

MIRENA relationship

Evidence supports the claim or example that makes the useful difference defensible.

Review target Content brief and draft

Loose association

The two assets are listed as workflow pages.

MIRENA relationship

The approved brief supplies the section roles, evidence, formats, links, and constraints that govern drafting.

Review target Hub and sibling page

Loose association

Both pages sit in the same cluster.

Main job

Represents visible types and properties in structured data.

Relationship

Formalizes selected relationships after the content is clear.

Ownership and production decisions

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

Keep inside the current block

The relationship directly supports the local answer or decision.

Move to another section

The connection belongs to the same asset but a different section job.

Route to a sibling asset

Another approved page already owns the deeper entity connection.

Reject or hold

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

Common mistakes

Weak relationship work lists entities, hides direction, overstates evidence, or links without purpose.

Using proximity as proof

Two entities appearing together does not automatically establish a meaningful relationship.

Leaving direction unclear

The reader needs to know which entity acts, owns, contains, produces, or routes.

Adding every possible connection

More edges can dilute the primary entity and create topic drift.

Ignoring evidence

Identity, ownership, product, pricing, outcome, and causal relationships need support.

Using generic links

The anchor and placement should explain the relationship and next task.

Marking up what is not visible

Structured data should represent approved content rather than invent a relationship.

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

Review the route

Entity SEO routes

Move from relationship definition into mapping, contextual integration, linking, and structured representation.

Can internal links reinforce entity relationships?

Yes. A contextual link can extend a visible relationship into the approved page that owns deeper meaning.

Should every relationship be marked up?

No. Only visible, supported relationships that fit the asset and schema type should become structured data.

What does MIRENA return?

MIRENA can return the pair register, relationship matrix, explanation plan, placement plan, link and markup cues, and final handoff.

Next route

Give MIRENA the asset, entity map, query, source context, internal inventory, and evidence. It returns the relationship types, explanations, placements, routes, and handoff.

Use the Entity Led Brief when the approved relationships are ready to control the sections, examples, comparisons, 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