Entity meaning and prominence

Define what the asset means before MIRENA strengthens where the entity appears.

Use 32 modules to define the primary entity, build its support model, repair salience and placement, resolve conflicts, plan support pages, align identity, and prepare later markup cues after the written content is approved.

Choose a starting route Search all 32 prompts

32 modules6 starting routes5 module groupsSchema only after approval

ModelDefinition and hierarchyPrimary, secondary, support, attribute, and optional roles

PlacementSalience and contextHeadings, opening, passages, proximity, and distance

ClusterConsistency and supportConflicts, gaps, pages, routes, and ownership

IdentityLater markup cuesVerified identity and schema planning after approval

Starting route

Start with the asset state already in front of you.

Each route keeps the entity layer separate from drafting, internal links, and final schema.

New page idea

Run

Entity Definition, then Entity Map

Stop condition

Stop until the primary entity and page role are clear.

Existing draft

Run

Entity Salience, Entity Context Windows, then Contextual Entity Integration

Stop condition

Do not add mentions without clarifying relationships.

Page cluster

Run

Entity Audit, Entity Consistency, then Entity Support Pages

Stop condition

Do not create support pages until ownership and overlap are resolved.

Keyword or candidate list

Run

Entity Prioritization, then Entity Cluster Design

Stop condition

Do not give every candidate equal weight.

Competitor evidence

Run

Entity Gap Audit, then Information Gain

Stop condition

Do not copy competitor entity lists or headings.

Approved draft

Run

Entity Markup Cues, then Schema Ready Entity Structure

Stop condition

Do not write final schema before visible content approval.

32 entity modules

Search, inspect, and copy one prompt at a time.

Every record keeps the purpose, full prompt, return fields, stop rule, and next routes together.

01Model and definition

Entity SEO

Build the broad entity layer for a page, cluster, or site section.

Copy full prompt

Short commandRun Entity SEO on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity SEO on the supplied asset.

Use the approved source context first.

Build the broad entity layer for a page, cluster, or site section.

Return:
– primary entity
– secondary entities
– support entities
– attributes
– relationships
– salience risks
– next workflow

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not move into drafting until the entity role is clear.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

primary entity
secondary entities
support entities
attributes
relationships
salience risks
next workflow

Stop rule

Do not move into drafting until the entity role is clear.

Possible routes

Content Briefs
Drafting and Rewriting

02Model and definition

Entity Definition

Define the main entity, its boundaries, nearby concepts, and terms to avoid.

Copy full prompt

Short commandRun Entity Definition on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Definition on the supplied asset.

Use the approved source context first.

Define the main entity, its boundaries, nearby concepts, and terms to avoid.

Return:
– direct definition
– defining attributes
– exclusions
– nearby concepts
– disambiguation notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not use a vague category label as the final definition.

Possible next routes:
– Content Briefs
– Entity Map

Do not run the routed workflow yet.

Return fields

direct definition
defining attributes
exclusions
nearby concepts
disambiguation notes

Stop rule

Do not use a vague category label as the final definition.

Possible routes

Content Briefs
Entity Map

03Model and definition

Entity Map

Build the primary, secondary, support, attribute, and relationship model.

Copy full prompt

Short commandRun Entity Map on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Map on the supplied asset.

Use the approved source context first.

Build the primary, secondary, support, attribute, and relationship model.

Return:
– entity hierarchy
– attributes
– relationships
– salience notes
– page role
– internal link notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not treat a list of names as a completed map.

Possible next routes:
– Topical Maps
– Content Briefs

Do not run the routed workflow yet.

Return fields

entity hierarchy
attributes
relationships
salience notes
page role
internal link notes

Stop rule

Do not treat a list of names as a completed map.

Possible routes

Topical Maps
Content Briefs

04Model and definition

Entity Attributes

Find the details that define, constrain, compare, or support the entity.

Copy full prompt

Short commandRun Entity Attributes on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Attributes on the supplied asset.

Use the approved source context first.

Find the details that define, constrain, compare, or support the entity.

Return:
– defining attributes
– functional attributes
– audience attributes
– missing attributes
– placement notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Keep only attributes that improve meaning or decisions.

Possible next routes:
– Content Briefs
– Information Gain

Do not run the routed workflow yet.

Return fields

defining attributes
functional attributes
audience attributes
missing attributes
placement notes

Stop rule

Keep only attributes that improve meaning or decisions.

Possible routes

Content Briefs
Information Gain

05Salience and placement

Entity Salience

Review how clearly and prominently the main entity appears inside a draft.

Copy full prompt

Short commandRun Entity Salience on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Salience on the supplied asset.

Use the approved source context first.

Review how clearly and prominently the main entity appears inside a draft.

Return:
– salience score
– heading review
– opening review
– co occurrence fixes
– dilution risks
– priority edits

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not increase mentions without increasing clarity.

Possible next routes:
– Drafting and Rewriting
– Final QA

Do not run the routed workflow yet.

Return fields

salience score
heading review
opening review
co occurrence fixes
dilution risks
priority edits

Stop rule

Do not increase mentions without increasing clarity.

Possible routes

Drafting and Rewriting
Final QA

06Consistency and gaps

Entity Audit

Inspect a page or cluster for weak support, drift, conflict, and missing entities.

Copy full prompt

Short commandRun Entity Audit on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Audit on the supplied asset.

Use the approved source context first.

Inspect a page or cluster for weak support, drift, conflict, and missing entities.

Return:
– entity inventory
– missing entities
– low value entities
– drift risks
– salience actions
– rewrite priorities

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not edit before the audit separates page and cluster problems.

Possible next routes:
– Topical Maps
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

entity inventory
missing entities
low value entities
drift risks
salience actions
rewrite priorities

Stop rule

Do not edit before the audit separates page and cluster problems.

Possible routes

Topical Maps
Drafting and Rewriting

07Salience and placement

Entity Placement

Decide where important entities should appear across metadata, headings, openings, sections, and links.

Copy full prompt

Short commandRun Entity Placement on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Placement on the supplied asset.

Use the approved source context first.

Decide where important entities should appear across metadata, headings, openings, sections, and links.

Return:
– metadata notes
– H1 notes
– heading notes
– opening notes
– paragraph placement
– later schema cue placement

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not place an entity where the surrounding passage cannot explain it.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

metadata notes
H1 notes
heading notes
opening notes
paragraph placement
later schema cue placement

Stop rule

Do not place an entity where the surrounding passage cannot explain it.

Possible routes

Content Briefs
Drafting and Rewriting

08Model and definition

Entity Prioritization

Separate primary, secondary, support, optional, and remove groups.

Copy full prompt

Short commandRun Entity Prioritization on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Prioritization on the supplied asset.

Use the approved source context first.

Separate primary, secondary, support, optional, and remove groups.

Return:
– primary entity
– secondary entities
– support entities
– optional entities
– entities to remove
– reason

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not give every candidate equal weight.

Possible next routes:
– Entity Map
– Content Briefs

Do not run the routed workflow yet.

Return fields

primary entity
secondary entities
support entities
optional entities
entities to remove
reason

Stop rule

Do not give every candidate equal weight.

Possible routes

Entity Map
Content Briefs

09Consistency and gaps

Entity Support Depth

Find supporting entities that need more explanation, examples, attributes, or links.

Copy full prompt

Short commandRun Entity Support Depth on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Support Depth on the supplied asset.

Use the approved source context first.

Find supporting entities that need more explanation, examples, attributes, or links.

Return:
– support entity
– current depth
– needed depth
– section recommendation
– link target

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not expand a support entity until it competes with the page owner.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

support entity
current depth
needed depth
section recommendation
link target

Stop rule

Do not expand a support entity until it competes with the page owner.

Possible routes

Content Briefs
Drafting and Rewriting

10Cluster and sections

Entity Support Pages

Identify support pages the cluster needs when one URL cannot carry the full entity model.

Copy full prompt

Short commandRun Entity Support Pages on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Support Pages on the supplied asset.

Use the approved source context first.

Identify support pages the cluster needs when one URL cannot carry the full entity model.

Return:
– support page
– support entity
– page role
– parent page
– link target
– priority

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not create a new URL when a section can handle the job.

Possible next routes:
– Topical Maps
– Internal Linking

Do not run the routed workflow yet.

Return fields

support page
support entity
page role
parent page
link target
priority

Stop rule

Do not create a new URL when a section can handle the job.

Possible routes

Topical Maps
Internal Linking

11Consistency and gaps

Entity Consistency

Find naming, definition, and attribute conflicts across a page set.

Copy full prompt

Short commandRun Entity Consistency on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Consistency on the supplied asset.

Use the approved source context first.

Find naming, definition, and attribute conflicts across a page set.

Return:
– inconsistent terms
– conflicting definitions
– page locations
– preferred wording
– update notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not normalize language that represents a genuine distinction.

Possible next routes:
– Drafting and Rewriting
– Entity Identity Across Pages

Do not run the routed workflow yet.

Return fields

inconsistent terms
conflicting definitions
page locations
preferred wording
update notes

Stop rule

Do not normalize language that represents a genuine distinction.

Possible routes

Drafting and Rewriting
Entity Identity Across Pages

12Consistency and gaps

Entity Conflict Resolution

Resolve competing entity roles, mixed meanings, and overlapping page ownership.

Copy full prompt

Short commandRun Entity Conflict Resolution on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Conflict Resolution on the supplied asset.

Use the approved source context first.

Resolve competing entity roles, mixed meanings, and overlapping page ownership.

Return:
– conflict type
– affected pages
– preferred entity role
– merge, split, rewrite, or clarify action
– link note

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not preserve two pages that claim the same entity job without a reason.

Possible next routes:
– Topical Maps
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

conflict type
affected pages
preferred entity role
merge, split, rewrite, or clarify action
link note

Stop rule

Do not preserve two pages that claim the same entity job without a reason.

Possible routes

Topical Maps
Drafting and Rewriting

13Consistency and gaps

Entity Gap Audit

Find missing entities, attributes, relationships, and support page opportunities.

Copy full prompt

Short commandRun Entity Gap Audit on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Gap Audit on the supplied asset.

Use the approved source context first.

Find missing entities, attributes, relationships, and support page opportunities.

Return:
– missing entity
– related primary entity
– missing attribute
– page or section target
– priority
– next workflow

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not copy competitor entity lists without source context.

Possible next routes:
– Information Gain
– Topical Maps

Do not run the routed workflow yet.

Return fields

missing entity
related primary entity
missing attribute
page or section target
priority
next workflow

Stop rule

Do not copy competitor entity lists without source context.

Possible routes

Information Gain
Topical Maps

14Cluster and sections

Entity Cluster Design

Turn an approved entity model into a hub, support page, role, and route plan.

Copy full prompt

Short commandRun Entity Cluster Design on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Cluster Design on the supplied asset.

Use the approved source context first.

Turn an approved entity model into a hub, support page, role, and route plan.

Return:
– hub entity
– support entities
– page roles
– link paths
– publishing order

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not build the cluster before ownership and overlap are resolved.

Possible next routes:
– Topical Maps
– Internal Linking

Do not run the routed workflow yet.

Return fields

hub entity
support entities
page roles
link paths
publishing order

Stop rule

Do not build the cluster before ownership and overlap are resolved.

Possible routes

Topical Maps
Internal Linking

15Cluster and sections

Entity Led Sections

Rebuild section order around the entity job of each passage.

Copy full prompt

Short commandRun Entity Led Sections on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Led Sections on the supplied asset.

Use the approved source context first.

Rebuild section order around the entity job of each passage.

Return:
– section heading
– target entity
– support entity
– attribute
– link target

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not make headings into an entity list.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

section heading
target entity
support entity
attribute
link target

Stop rule

Do not make headings into an entity list.

Possible routes

Content Briefs
Drafting and Rewriting

16Salience and placement

Entity Rich Intro

Strengthen the opening definition and early entity placement.

Copy full prompt

Short commandRun Entity Rich Intro on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Rich Intro on the supplied asset.

Use the approved source context first.

Strengthen the opening definition and early entity placement.

Return:
– revised opening
– main entity placement
– support entity placement
– answer block notes
– salience notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not overload the opening with every support concept.

Possible next routes:
– Drafting and Rewriting
– SERP Feature Planning

Do not run the routed workflow yet.

Return fields

revised opening
main entity placement
support entity placement
answer block notes
salience notes

Stop rule

Do not overload the opening with every support concept.

Possible routes

Drafting and Rewriting
SERP Feature Planning

17Salience and placement

Entity Context Windows

Improve the words, attributes, and relationships around entity mentions.

Copy full prompt

Short commandRun Entity Context Windows on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Context Windows on the supplied asset.

Use the approved source context first.

Improve the words, attributes, and relationships around entity mentions.

Return:
– entity mention
– current context
– improved context
– attribute to add
– relationship to clarify

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not insert loose entity names without explanatory context.

Possible next routes:
– Drafting and Rewriting
– Internal Linking

Do not run the routed workflow yet.

Return fields

entity mention
current context
improved context
attribute to add
relationship to clarify

Stop rule

Do not insert loose entity names without explanatory context.

Possible routes

Drafting and Rewriting
Internal Linking

18Model and definition

Entity Disambiguation

Clarify overloaded terms, acronyms, product names, and broad concepts.

Copy full prompt

Short commandRun Entity Disambiguation on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Disambiguation on the supplied asset.

Use the approved source context first.

Clarify overloaded terms, acronyms, product names, and broad concepts.

Return:
– ambiguous entity
– possible meanings
– chosen meaning
– disambiguation copy
– terms to avoid

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not proceed while the same term can point to several entity identities.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

ambiguous entity
possible meanings
chosen meaning
disambiguation copy
terms to avoid

Stop rule

Do not proceed while the same term can point to several entity identities.

Possible routes

Content Briefs
Drafting and Rewriting

19Salience and placement

Entity Density vs Clarity

Balance entity coverage with readable explanation.

Copy full prompt

Short commandRun Entity Density vs Clarity on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Density vs Clarity on the supplied asset.

Use the approved source context first.

Balance entity coverage with readable explanation.

Return:
– density risk
– clarity risk
– keep list
– reduce list
– remove list
– rewrite notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not reward repetition as depth.

Possible next routes:
– Drafting and Rewriting
– Final QA

Do not run the routed workflow yet.

Return fields

density risk
clarity risk
keep list
reduce list
remove list
rewrite notes

Stop rule

Do not reward repetition as depth.

Possible routes

Drafting and Rewriting
Final QA

20Salience and placement

Entity Proximity

Move related entities and attributes closer where the passage needs reinforcement.

Copy full prompt

Short commandRun Entity Proximity on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Proximity on the supplied asset.

Use the approved source context first.

Move related entities and attributes closer where the passage needs reinforcement.

Return:
– entity pair
– attribute pair
– distance issue
– movement
– revised section

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not force co location when the relationship belongs elsewhere.

Possible next routes:
– Drafting and Rewriting
– Internal Linking

Do not run the routed workflow yet.

Return fields

entity pair
attribute pair
distance issue
movement
revised section

Stop rule

Do not force co location when the relationship belongs elsewhere.

Possible routes

Drafting and Rewriting
Internal Linking

21Salience and placement

Entity Distance

Find page level distance problems between related concepts.

Copy full prompt

Short commandRun Entity Distance on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Distance on the supplied asset.

Use the approved source context first.

Find page level distance problems between related concepts.

Return:
– distance issue
– affected entity
– related attribute
– section move
– revised order

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not scatter support concepts across unrelated sections.

Possible next routes:
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Return fields

distance issue
affected entity
related attribute
section move
revised order

Stop rule

Do not scatter support concepts across unrelated sections.

Possible routes

Content Briefs
Drafting and Rewriting

22Model and definition

Entity Hierarchy

Give each entity a role, placement priority, section target, and link target.

Copy full prompt

Short commandRun Entity Hierarchy on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Hierarchy on the supplied asset.

Use the approved source context first.

Give each entity a role, placement priority, section target, and link target.

Return:
– hierarchy
– role
– placement priority
– section target
– link target

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not let optional entities compete with the primary entity.

Possible next routes:
– Content Briefs
– Entity Map

Do not run the routed workflow yet.

Return fields

hierarchy
role
placement priority
section target
link target

Stop rule

Do not let optional entities compete with the primary entity.

Possible routes

Content Briefs
Entity Map

23Salience and placement

Entity Co Occurrence

Identify entity pairs that should appear together and explain why.

Copy full prompt

Short commandRun Entity Co Occurrence on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Co Occurrence on the supplied asset.

Use the approved source context first.

Identify entity pairs that should appear together and explain why.

Return:
– entity pair
– reason
– target section
– attribute
– link note

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not use co occurrence as a keyword stuffing rule.

Possible next routes:
– Drafting and Rewriting
– Internal Linking

Do not run the routed workflow yet.

Return fields

entity pair
reason
target section
attribute
link note

Stop rule

Do not use co occurrence as a keyword stuffing rule.

Possible routes

Drafting and Rewriting
Internal Linking

24Model and definition

Entity Relationships

Explain how entities connect through clear relationship types and passages.

Copy full prompt

Short commandRun Entity Relationships on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Relationships on the supplied asset.

Use the approved source context first.

Explain how entities connect through clear relationship types and passages.

Return:
– entity A
– entity B
– relationship type
– sentence or section recommendation
– link target

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not leave the relationship implicit when it changes meaning.

Possible next routes:
– Content Briefs
– Internal Linking

Do not run the routed workflow yet.

Return fields

entity A
entity B
relationship type
sentence or section recommendation
link target

Stop rule

Do not leave the relationship implicit when it changes meaning.

Possible routes

Content Briefs
Internal Linking

25Salience and placement

Contextual Entity Integration

Work approved entities into the copy without awkward insertion or flow damage.

Copy full prompt

Short commandRun Contextual Entity Integration on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Contextual Entity Integration on the supplied asset.

Use the approved source context first.

Work approved entities into the copy without awkward insertion or flow damage.

Return:
– entity to add
– entity to move
– entity to reduce
– revised wording
– section target

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not add entities that the page cannot explain.

Possible next routes:
– Drafting and Rewriting
– Final QA

Do not run the routed workflow yet.

Return fields

entity to add
entity to move
entity to reduce
revised wording
section target

Stop rule

Do not add entities that the page cannot explain.

Possible routes

Drafting and Rewriting
Final QA

26Identity and markup

Entity Markup Cues

Prepare visible content notes that can support structured data after approval.

Copy full prompt

Short commandRun Entity Markup Cues on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Markup Cues on the supplied asset.

Use the approved source context first.

Prepare visible content notes that can support structured data after approval.

Return:
– entity type
– schema cue
– attribute cue
– relationship cue
– validation note

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not write final schema before visible content is stable.

Possible next routes:
– Schema Cues after approval

Do not run the routed workflow yet.

Return fields

entity type
schema cue
attribute cue
relationship cue
validation note

Stop rule

Do not write final schema before visible content is stable.

Possible routes

Schema Cues after approval

27Identity and markup

Entity Markup

Prepare JSON LD planning notes and entity relationships for an approved page.

Copy full prompt

Short commandRun Entity Markup on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Markup on the supplied asset.

Use the approved source context first.

Prepare JSON LD planning notes and entity relationships for an approved page.

Return:
– schema type
– main entity
– supporting entities
– relationships
– sameAs notes
– validation steps

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Schema must reflect the approved content and URLs.

Possible next routes:
– Schema Planning
– Final QA

Do not run the routed workflow yet.

Return fields

schema type
main entity
supporting entities
relationships
sameAs notes
validation steps

Stop rule

Schema must reflect the approved content and URLs.

Possible routes

Schema Planning
Final QA

28Identity and markup

sameAs and Entity Identity

Review external identity candidates, confidence, risk, and validation needs.

Copy full prompt

Short commandRun sameAs and Entity Identity on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run sameAs and Entity Identity on the supplied asset.

Use the approved source context first.

Review external identity candidates, confidence, risk, and validation needs.

Return:
– entity name
– possible sameAs target
– confidence
– risk
– schema cue

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not add an identity URL without verification.

Possible next routes:
– Schema Planning
– Final QA

Do not run the routed workflow yet.

Return fields

entity name
possible sameAs target
confidence
risk
schema cue

Stop rule

Do not add an identity URL without verification.

Possible routes

Schema Planning
Final QA

29Identity and markup

Entity Identity Across Pages

Align naming, definitions, attributes, and identity cues across a page set.

Copy full prompt

Short commandRun Entity Identity Across Pages on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Identity Across Pages on the supplied asset.

Use the approved source context first.

Align naming, definitions, attributes, and identity cues across a page set.

Return:
– naming rule
– definition rule
– page conflicts
– fix list
– schema cue

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not erase real product or audience distinctions.

Possible next routes:
– Drafting and Rewriting
– Schema Planning

Do not run the routed workflow yet.

Return fields

naming rule
definition rule
page conflicts
fix list
schema cue

Stop rule

Do not erase real product or audience distinctions.

Possible routes

Drafting and Rewriting
Schema Planning

30Identity and markup

Knowledge Panel Support

Prepare clearer entity summaries, attributes, relationships, identity cues, and support pages.

Copy full prompt

Short commandRun Knowledge Panel Support on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Knowledge Panel Support on the supplied asset.

Use the approved source context first.

Prepare clearer entity summaries, attributes, relationships, identity cues, and support pages.

Return:
– entity summary
– attributes
– authority signals
– related entities
– sameAs candidates
– support pages

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– This is not a promise of a knowledge panel.

Possible next routes:
– Topical Maps
– Schema Planning

Do not run the routed workflow yet.

Return fields

entity summary
attributes
authority signals
related entities
sameAs candidates
support pages

Stop rule

This is not a promise of a knowledge panel.

Possible routes

Topical Maps
Schema Planning

31Identity and markup

Knowledge Panel Entity Support

Strengthen identity facts, support pages, internal routes, trust notes, and later schema cues.

Copy full prompt

Short commandRun Knowledge Panel Entity Support on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Knowledge Panel Entity Support on the supplied asset.

Use the approved source context first.

Strengthen identity facts, support pages, internal routes, trust notes, and later schema cues.

Return:
– identity fixes
– supporting facts
– internal links
– schema cues
– trust notes

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not publish unsupported identity facts.

Possible next routes:
– Internal Linking
– Schema Planning

Do not run the routed workflow yet.

Return fields

identity fixes
supporting facts
internal links
schema cues
trust notes

Stop rule

Do not publish unsupported identity facts.

Possible routes

Internal Linking
Schema Planning

32Identity and markup

Schema Ready Entity Structure

Package entity types, attributes, relationships, and validation notes after draft approval.

Copy full prompt

Short commandRun Schema Ready Entity Structure on the supplied asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Schema Ready Entity Structure on the supplied asset.

Use the approved source context first.

Package entity types, attributes, relationships, and validation notes after draft approval.

Return:
– main entity
– entity type
– attributes
– relationships
– schema cue
– validation note

Rules:
– Keep one clear primary entity.
– Mark missing evidence, uncertainty, conflicts, and review needs.
– Do not create code until the final written claims and URLs are approved.

Possible next routes:
– Schema Cues after approval
– Developer Handoff

Do not run the routed workflow yet.

Return fields

main entity
entity type
attributes
relationships
schema cue
validation note

Stop rule

Do not create code until the final written claims and URLs are approved.

Possible routes

Schema Cues after approval
Developer Handoff

Entity handoff

Every accepted entity decision moves into a named workflow.

Brief

Entity led writer plan

Primary entity, support set, attributes, relationships, section roles, and link targets.

Rewrite

Salience repair

Placement, context windows, density, proximity, distance, and integration instructions.

Map

Cluster ownership

Hub, support pages, page roles, publishing order, and route logic.

Links

Relationship routes

Source page, target page, entity relationship, placement, and anchor purpose.

Identity

Consistency fixes

Naming, definitions, attributes, support facts, and verified external identity candidates.

Schema

Approved cues only

Entity types, properties, relationships, URLs, and validation notes after approval.

Questions

Entity SEO and Salience questions.

What is the first entity module to run?

Use Entity Definition when the idea is unclear, Entity Map when the topic is known but unstructured, and Entity Salience when a draft already exists.

What is the difference between Entity Map and Entity Salience?

Entity Map defines the entity model. Entity Salience checks how clearly that model appears inside the content.

When should Entity Gap Audit run?

Run it when a page or cluster has clear missing entities, attributes, relationships, or support page needs.

Can entity work support internal links?

Yes. Entity relationships, support pages, hierarchy, proximity, and context windows can all produce internal link routes.

When do markup cues run?

Only after the visible draft is approved. Markup cues prepare the later schema handoff rather than replacing content approval.

Does entity optimization guarantee a knowledge panel?

No. The identity modules help prepare clearer entity signals and verified support, but they do not guarantee a knowledge panel.

Next route

Give MIRENA the asset and source context, then run the smallest useful entity module.

Move the approved result into the brief, rewrite, topical map, internal link plan, or later schema handoff.

Open MIRENA Review the workflow