Entity quality review · Entity SEO

An entity audit finds where the entity system inside an asset is unclear, shallow, misplaced, or disconnected.

MIRENA reviews the title, H1, opening, entity hierarchy, attributes, relationships, section placements, support depth, internal links, and structured consistency. Every issue becomes a repair priority, owner, evidence need, and next workflow.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

8 issue types6 MIRENA stages8 audit dimensions8 repair actions

CenterPrimary entity clarityTitle, H1, opening answer, and heading path

NetworkAttributes and relationshipsThe support required to explain and distinguish the entity

StructurePlacement, links, and markupHow the entity system appears across the asset and site

OutputA prioritized repair planKeep, fix, move, deepen, link, route, split, or hold

Definition and evidence boundary

An entity audit reviews the semantic operating system of a live asset.

MIRENA does not stop at finding weak entities. It ranks the issue, chooses the repair, assigns ownership, and routes the asset into briefing, rewriting, linking, schema, or planning.

Live asset

The audit starts from the visible page

MIRENA checks the content, structure, links, and structured data that actually exist.

Approved model

The page is compared with a controlled entity plan

The primary entity, hierarchy, attributes, relationships, placements, and routes provide the expected state.

MIRENA rule

Every issue needs severity and treatment

The audit ends in a keep, repair, route, split, reject, review, or hold decision.

Evidence boundary: Entity analysis, structured data, and link guidance can support an audit, but none provides one complete Google Search entity score. MIRENA treats the audit as an editorial, semantic, technical, and site architecture review tied to visible content and approved source evidence.

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

MIRENA internal workflow

MIRENA runs the entity audit through six wide workflow stages.

The workflow prevents checklist only reviews, equal severity findings, vague recommendations, and audit notes that never change the live asset.

Confirm the asset job and expected entity model

MIRENA fixes the query, audience, completion event, source context, primary entity, hierarchy, and approved route.

Capture the live entity state

The title, H1, opening, headings, entities, attributes, relationships, placements, links, and JSON LD are recorded.

Compare expected and live states

Every entity layer becomes clear, weak, vague, buried, missing, duplicated, competing, unsupported, or misrouted.

Score severity and impact

MIRENA rates entity centrality, reader impact, query fit, evidence risk, cluster risk, and production effort.

Choose repair and ownership

The issue becomes keep, clarify, move, deepen, link, align markup, route, split, reject, review, or hold.

Create the entity audit handoff

The prioritized actions receive an owner, source need, section target, format, link route, review condition, and next workflow.

Eight entity audit issue types

Entity weakness can appear in the center, hierarchy, support, placement, links, or structured consistency.

Unclear primary entity

The title, opening, and section path do not establish one stable subject.

Hierarchy conflict

Several entities compete for control or support roles are not distinguished.

Missing attributes

The asset names the entity without the properties, functions, limits, examples, or use cases needed.

Weak relationships

Related concepts appear without an explicit connection, direction, or reader value.

Placement problem

Primary or supporting entities appear too late, too far away, or inside the wrong section.

Shallow support depth

The page lacks enough context, examples, comparison, evidence, or continuation.

Internal route problem

The hub, sibling, proof, support, or next workflow links are missing or poorly placed.

Structured mismatch

The visible content, canonical identity, author, organization, product, and JSON LD do not align.

Eight entity audit dimensions

MIRENA checks the asset from primary entity clarity through site and schema consistency.

Primary entity clarity

Can the page owner be named in one clear phrase?

Salience and hierarchy

Do prominence and role order protect one stable center?

Attribute completeness

Does the asset cover the defining properties, functions, limits, and use cases?

Relationship quality

Are important connections explicit, directional, supported, and useful?

Placement and proximity

Do entities appear in the right zones with their defining support nearby?

Support depth and drift

Does the asset deepen the topic without opening unrelated lanes?

Internal link reinforcement

Do the hub, siblings, proof, support, and next workflow routes reinforce the entity path?

Structured consistency

Do titles, visible facts, canonicals, authorship, organization, product, and JSON LD agree?

Eight entity audit repair actions

The audit ends when every finding has a specific repair and owner.

Clarify the primary entity

Rewrite the title, H1, opening answer, and summary around one stable page owner.

Rebuild the hierarchy

Assign primary, secondary, supporting, attribute, evidence, and routed roles.

Add missing attributes

Supply the properties, functions, limits, examples, and use cases the asset needs.

Explain weak relationships

State how entities connect, in which direction, and why the relationship matters.

Move misplaced support

Put entities, attributes, examples, and evidence inside the sections that own them.

Deepen or compress support

Add useful context where the asset is thin and remove repetition or drift elsewhere.

Repair internal routes

Add or reposition the hub, sibling, proof, support, and next workflow links.

Align structured data

Make JSON LD describe the same visible entity, author, organization, product, and asset role.

Examples

A useful audit names the entity failure, evidence, repair, owner, and next workflow.

Review target Definition asset

Audit finding

The primary entity is in the H1 but the opening stays vague and the headings drift into broad SEO.

MIRENA repair

Replace the opening, rebuild the heading path, and route side concepts to their owning pages.

Review target Product asset

Audit finding

The product is prominent but attributes, plan limits, creator, organization, and use cases are inconsistent.

MIRENA repair

Align visible facts, entity relationships, product sections, pricing route, and structured data.

Review target Process asset

Audit finding

Tools and tasks appear, but owners, inputs, outputs, gates, and handoffs are unclear.

MIRENA repair

Rebuild the entity relationships around the ordered process and assign each workflow role.

Review target Older URL

Audit finding

Several updates added duplicated entities, distant attributes, random links, and stale markup.

Main job

Uses structured data types and properties to support visible facts.

Relationship

Repairs structured consistency after the content is clear.

Ownership and production decisions

MIRENA routes each audit issue into the smallest workflow that can repair it.

Repair the current block

The entity model is correct but one section needs clarity, support, placement, or a link.

Rebuild the asset structure

Several issues affect the full hierarchy, heading path, and section order.

Route to another workflow

The issue belongs to topical planning, briefing, internal linking, schema, or evidence review.

Split, reject, or hold

The asset contains separate page jobs, unsupported claims, private data, or unresolved ownership.

Common mistakes

Weak entity audits list observations, score everything equally, or recommend more mentions instead of repairs.

Checking term presence only

The audit must review roles, attributes, relationships, placement, support, and routes.

Using one generic score

Different issue types need evidence, severity, impact, effort, and ownership notes.

Ignoring the expected model

A live asset needs an approved primary entity, hierarchy, and route for comparison.

Recommending more mentions

Repetition does not fix hierarchy, proximity, support, or relationship problems.

Skipping internal links and markup

The entity system extends across the site and into visible structured consistency.

Stopping at the report

The audit is unfinished until the repair enters briefing, rewriting, links, schema, planning, or hold.

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

Review the route

Entity SEO routes

Move each audit finding into prioritization, rewriting, internal links, or structured data.

Can MIRENA audit an older URL?

Yes. It can compare the live asset with the approved entity model and route each repair.

Does an entity audit guarantee rankings?

No. It improves semantic, editorial, structural, linking, and markup discipline without promising search outcomes.

What does MIRENA return?

MIRENA can return the expected model, live audit record, issue register, priority plan, brief or rewrite handoff, and final routing record.

Next route

Give MIRENA the live asset, query, source context, expected entity model, internal routes, and JSON LD. It returns the issue register, priorities, repairs, owners, and handoff.

Use drafting and rewriting when the asset already exists, or use the Entity Led Brief when the entity model should control a new draft before production begins.

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