Contextual entity grouping · Entity SEO

Entity co occurrence works when related entities appear together inside one clear explanation.

MIRENA starts with one primary entity, selects only the support entities that fit the section job, states the relationship, keeps the explanation close, controls repeated mentions, and reinforces the same cluster through contextual internal links.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

6 co occurrence patterns6 MIRENA stages8 review dimensions8 repair actions

Primary entityOne stable section centerThe entity the explanation is built to support

Related entitiesOnly the concepts that belongAttributes, comparisons, processes, evidence, and routes

ConnectionThe relationship is explainedCause, part, type, use, contrast, sequence, or support

OutputA section integration planPlacement, bridge copy, examples, links, or removal

Definition and evidence boundary

Entity co occurrence is a contextual relationship pattern, not a standalone optimization lever.

MIRENA uses the concept to review whether related entities appear in the correct section with enough explanation, support, and routing.

Entity analysis

Systems can identify entities and mentions in text

Google Cloud documents entity analysis as detection of known entities and their mentions.

Search boundary

Detected co mentions do not disclose a Search ranking factor

MIRENA avoids claims that a simple list of related entities creates rankings.

MIRENA rule

The relationship must be visible

Every important co occurrence pair needs a section purpose, explanation, example, attribute, or route.

Evidence boundary: Google Cloud Natural Language documentation describes entity detection and mentions. It does not state that entity co occurrence is one standalone Google Search ranking factor. MIRENA uses co occurrence as a content structure and clarity review tied to helpfulness, contextual links, and visible relationships.

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

MIRENA internal workflow

MIRENA builds useful entity co occurrence through six wide workflow stages.

The workflow prevents term piles, mixed intent sections, repeated support entities, unexplained associations, and links that do not fit the paragraph.

Confirm the primary entity and section job

MIRENA fixes what the section must explain, compare, prove, or route before support entities are selected.

Select the related entity set

Only entities with a direct attribute, relationship, comparison, workflow, evidence, or route role are kept.

State the connection

MIRENA labels why the entities belong together, including type, part, cause, use, sequence, contrast, ownership, or support.

Assign the correct section and proximity

The entities appear where the relationship is explained, with the defining support close to the mention.

Audit repetition, drift, and balance

Repeated support entities, mixed intents, filler terms, distant explanations, and overpromoted concepts are marked.

Create the integration handoff

The approved pairs receive placement, bridge copy, attributes, examples, links, owner, and review instructions.

Six co occurrence patterns

Related entities can define, compare, explain, prove, sequence, or route the primary entity.

Definition pattern

The primary entity appears beside the attributes and close concepts that explain what it is.

Part and whole pattern

A component is explained inside the system, process, product, or cluster it belongs to.

Cause and effect pattern

The section shows how one entity changes, enables, limits, or produces another.

Comparison pattern

Related entities appear together because the reader needs criteria, fit, contrast, or tradeoffs.

Workflow pattern

Inputs, stages, owners, tools, outputs, and handoffs appear together inside an ordered process.

Evidence and route pattern

The entity appears beside the source, example, proof, sibling page, or next action that supports it.

Eight co occurrence review dimensions

MIRENA checks whether the entity pair belongs, connects, and improves the section.

Section fit

Do both entities support the same local question or task?

Relationship clarity

Does the copy explain why the entities belong together?

Proximity

Are the names, attributes, and explanation close enough to be understood as one unit?

Attribute support

Does the section explain what role each entity plays?

Repetition value

Does another mention add meaning or only repeat the same association?

Intent consistency

Do the entities serve the same page job and user state?

Link support

Does a contextual link extend the relationship at the right moment?

Drift risk

Could the supporting entity take the section into a different topic or page job?

Eight co occurrence repair actions

Each weak pair becomes an explanation, placement, link, split, removal, or hold action.

Explain the relationship

Add the sentence that states how the entities connect and why the reader needs the connection.

Move the pair into the right section

Place the entities where their shared role is being discussed.

Add a bridge statement

Connect the previous concept, entity pair, and next section without leaving the transition implied.

Add attributes or an example

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

Split a mixed intent section

Separate entities that belong to different user jobs or page roles.

Remove filler mentions

Delete related terms that add no explanation, evidence, comparison, or route.

Add a contextual internal link

Route the deeper entity or relationship to the approved sibling asset.

Hold for evidence or ownership review

Stop when the relationship is unsupported or another asset may own it.

Examples

The stronger version explains the relationship instead of placing related terms beside each other.

Review target Semantic SEO section

Loose mention

Search intent, entity salience, internal linking, structured data, and Information Gain appear in one list.

MIRENA integration

The section explains how intent controls the job, salience controls the center, links extend the route, and markup supports visible facts.

Review target Product section

Loose mention

Brand, founder, features, pricing, and use cases appear in one dense paragraph.

MIRENA integration

Identity, product function, commercial boundary, and use case entities receive separate but connected roles.

Review target Process section

Loose mention

Evidence, brief, writer, editor, draft, links, and schema appear without sequence.

MIRENA integration

The entities are ordered as inputs, owners, stages, outputs, and handoffs.

Review target Internal link block

Loose mention

Several sibling links appear because the topics are generally related.

Main job

Checks clarity, hierarchy, support, proximity, drift, links, and structured consistency.

Relationship

Verifies the finished relationship pattern.

Ownership and production decisions

MIRENA decides whether the related entity belongs in the current section, another section, a sibling asset, or nowhere.

Keep inside the current section

The relationship directly supports the local question and can be explained clearly.

Move to another section

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

Route to a sibling asset

The deeper entity or relationship already has an approved owner.

Remove or hold

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

Common mistakes

Weak co occurrence work stuffs terms, mixes intents, repeats associations, or leaves relationships implied.

Listing related terms

A list of associated words does not explain the topic or the relationships.

Mixing entities from different intents

One section should not serve unrelated user jobs.

Repeating support entities everywhere

A support entity needs a new role each time it returns.

Naming entities without attributes

The reader needs the function or relationship, not only the label.

Ignoring the site route

A relationship can need a contextual link to the approved sibling asset.

Claiming a simple ranking lever

Co occurrence is better treated as one content structure input inside a wider system.

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

Review the route

Entity SEO routes

Move from co occurrence into relationship definition, contextual placement, support depth, and site reinforcement.

How is co occurrence different from entity relationships?

Co occurrence shows contextual proximity. Relationships explain the connection and direction.

Can MIRENA repair weak co occurrence?

Yes. It can move entities, explain the relationship, add attributes or examples, remove filler, and route deeper concepts.

What does MIRENA return?

MIRENA can return the section record, pair matrix, explanation plan, placement plan, internal route plan, and final handoff.

Next route

Give MIRENA the asset, section jobs, entity map, source context, and internal inventory. It returns the related entity pairs, explanations, placements, routes, and handoff.

Use the Entity Led Brief when the entity pairs and section placements are ready to control the draft, or send a live URL into rewriting when mixed entities and drift already exist.

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