Main entity
The central subject the asset must explain, compare, support, or route.
Semantic page blueprint
Define the subject, support, attributes, and placement before drafting.
An entity led brief tells the writer what the asset is about at a semantic level. MIRENA defines the primary entity, supporting entities, attributes, relationships, salience priorities, placement, proof needs, internal routes, and concepts that must stay outside scope.
Four entity layersSix brief fieldsSix workflow stagesSchema cues only after approval
SubjectOne primary entityThe asset has a clear semantic center
SupportDirect relationships onlyRandom adjacent concepts stay out
SaliencePriority and placementImportant concepts appear where they matter
RouteMeaning bridges and later cuesLinks and schema cues follow approved content
Entity stack
The brief moves from subject to support, attributes, relationships, and placement.
Supporting entities
Concepts that directly clarify the primary entity and page job.
Attributes and relationships
Properties, constraints, processes, comparisons, and links that change understanding.
Salience and section mapping
What appears early, what supports later, what receives proof, and what stays outside scope.
Entity direction vs keyword direction
Queries describe the search space. Entities describe the meaning.
- Primary phrase
- Related phrases
- Target length
- Competitor URLs
- Loose headings
- Primary and supporting entities
- Attributes and relationships
- Salience priorities
- Section placement
- Proof, examples, internal routes, and boundaries
Entity led brief packet
The writer receives meaning, priority, placement, proof, and route direction.
Primary entityPreferred label, definition boundary, page role, dominant intent, and why the entity leads.
Supporting entitiesDirect support concepts, preferred labels, relationship to the primary entity, and concepts to reject.
Attributes and relationshipsProperties, constraints, process stages, comparisons, dependencies, examples, and proof requirements.
Salience prioritiesConcepts for the title, opening, major sections, examples, questions, summary, and later support.
Section placementWhere each entity appears, why it belongs there, expected depth, and the answer form required.
Internal routes and schema cuesMeaning bridges, authority support, next step links, and later structured data cues after approval.
Six stage entity workflow
Define what belongs before the draft decides by accident.
Name the primary entity
Identify the main thing the asset must explain, compare, support, or route.
Collect supporting entities
Keep only the concepts that directly clarify the primary entity and page job.
Map attributes and relationships
Record the properties, constraints, processes, comparisons, and links between concepts that change understanding.
Assign salience priorities
Decide what must appear early, what supports later sections, and what should remain outside scope.
Map entities into sections
Place concepts into the opening, H2 blocks, examples, questions, summary, and internal links.
Review coverage and drift
Confirm the asset remains focused, supported, useful, and aligned with the dominant intent.
Entity guardrails
Entity coverage is not a synonym list or a reason to add every related concept.
Random semantic expansion
Related concepts stay out when they do not support the page job, reader need, or approved scope.
Keyword stuffing by another name
Entities need relationships, purpose, placement, and support rather than repeated labels.
Unsupported attributes
Claims, examples, product details, and comparisons remain marked when proof is missing.
Schema before content approval
Structured data cues wait until visible content, page type, URLs, entities, and claims are approved.
Questions
Entity led briefing questions.
What is an entity led brief?
It is a content brief built around the main things the asset is about, their attributes, relationships, priority, placement, and support.
Does an entity led brief replace keyword research?
No. Query evidence helps identify demand and language. Entity direction controls meaning, coverage, and relationships inside the asset.
What is the primary entity?
It is the main subject the asset must explain, compare, support, or route. It should remain clear in the title, opening, major sections, and summary.
What are supporting entities?
They are concepts that directly clarify the primary entity. They are not a random list of synonyms or every related topic.
How does salience affect the brief?
Salience determines which concepts need stronger placement, proximity, repetition, and support based on the page job and source context.
Does the entity led brief create schema?
No. It can record entity and attribute cues. Structured data should wait until visible content, page type, entities, URLs, and claims are approved.
Next route
Give MIRENA the topic, query, source context, and page role. Receive the semantic page blueprint.
MIRENA extracts and prioritizes entities, maps attributes and relationships, assigns placement, records proof needs, and routes the approved brief into production.
Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.