Orient
Learn the language, page roles, evidence rules, and first route.
Main category hub · Entity constellation
Move through Entity SEO from first principles to governed practice.
The Entity SEO hub gives every important concept a stable identity, role, hierarchy, attribute set, relationship network, placement plan, page owner, and route through the wider site.
The hub is the main node for 27 complete assets. It gives beginners a clear first route, gives practitioners a production path, and gives advanced operators the controls needed to govern ownership, evidence, approval, maintenance, and scale.
27 complete assets
5 learning levels
5 entry states
One main category node
Beginner route
Learn what an entity is and how a main entity differs from support.
Start with language, ownership, and the first useful decision.
Practitioner route
Turn approved decisions into a working output
Build only after the input, scope, and owner are clear.
Advanced route
Govern consistency, disambiguation, conflict, cluster ownership, support depth, audits, and cross page identity.
Govern evidence, dependencies, and long term quality.
Hub rule
Every asset earns a clear role and route
No child asset sits as an unowned archive item.
Start from the current state
Choose the route that matches the decision already in front of you.
The route selector moves a beginner, practitioner, or advanced operator into the smallest asset that can own the next decision. Every route remains visible without relying on fragile tabs.
I need the foundations
Recommended route
Start with What Is an Entity, Main Entity Selection, Support Entity Selection, and Entity Hierarchy.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need a page entity plan
Recommended route
Use Entity Map, Attributes, Relationships, Placement, and Salience.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetThe page feels crowded or scattered
Recommended route
Use Density vs Clarity, Distance, Proximity, Context Windows, and Support Depth.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetThe site has conflicting identity signals
Recommended route
Use Consistency, Disambiguation, Conflict Resolution, and Entity Audit.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need cluster level entity support
Recommended route
Use Cluster Design, Support Pages, Gap Audit, and Entity Led Internal Links.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetBeginner through advanced
The journey grows from orientation into system governance.
The levels are not credentials. They describe the complexity of the decision, the amount of evidence required, and the number of connected assets that must be controlled.
Frame
Choose ownership, intent, scope, inputs, and the correct workflow.
Build
Create the map, brief, draft, format, link route, or implementation.
Refine
Audit overlap, gaps, weak answers, structure, proof, and performance.
Govern
Control approvals, ownership, maintenance, refresh, policy, and scale.
Visual semantics · Entity constellation
The interface mirrors the way the category is meant to be understood.
Entity constellation is more than decoration.
The visual system gives the category one stable mental model. The hero shows the category center, the route selector shows the current state, the journey rail shows progression, the complete index shows every owned asset, and the connected hub section shows where the work moves next.
Color carries stage and category meaning. Repeated card geometry signals comparable choices. Larger nodes indicate parent ownership. Lines, rings, grids, or layers express relationships, sequence, evidence, and handoff without asking the reader to decode a decorative illustration.
The copy follows the same grammar. Every block names the job, the input, the decision, the output, and the route. The result is a page that can orient a beginner without flattening the system for an experienced operator.
CenterEntity SEO
EntryLearn what an entity is and how a main entity differs from support.
DepthGovern consistency, disambiguation, conflict, cluster ownership, support depth, audits, and cross page identity.
MetaphorEntity constellation
Asset count27
Next routeEvidence decides
Complete child asset index
All 27 assets remain visible from the main node.
Search by title, task, stage, or concept. Filter by learning level without hiding the full category architecture from users or search systems.
Entity Support Pages
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Consistency
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Conflict Resolution
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Gap Audit
Diagnose the current asset, record evidence and severity, and route each failure into the smallest useful repair.
Open the assetEntity Cluster Design
Shape page ownership, parent and child relationships, overlap controls, routes, dependencies, and build order.
Open the assetEntity Led Internal Links
Plan or review a route that connects meaning, page roles, user state, proof needs, and the next useful action.
Open the assetEntity Led Sections
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Rich Intros
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Context Windows
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Disambiguation
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetSupport Entity Selection
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetMain Entity Selection
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Density vs Clarity
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Proximity
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Distance
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Hierarchy
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Support Depth
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Placement
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Prioritization
Rank the available work by ownership, value, weakness, evidence, effort, risk, and dependency.
Open the assetEntity Audit
Diagnose the current asset, record evidence and severity, and route each failure into the smallest useful repair.
Open the assetContextual Entity Integration
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Relationships
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Co Occurrence
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Map
Shape page ownership, parent and child relationships, overlap controls, routes, dependencies, and build order.
Open the assetEntity Attributes
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetEntity Salience
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetWhat Is an Entity
Start with a direct definition of an Entity and see how it connects to the wider Entity SEO system.
Open the assetOperator field guide
Read the entity constellation as a working system.
The visual metaphor creates a memory structure for the category. Each part of the model represents a decision the operator must make, not a decorative label.
Name the identity
The constellation begins with one stable identity and the canonical page that owns it.
A beginner should be able to state the current job in one sentence before opening a deeper asset. That sentence becomes the reference point for scope, evidence, page ownership, and the next route.
Assign the node roles
Support nodes earn their place through attributes, relationships, examples, proof, page roles, and routes.
The edge marks the point where a related topic stops supporting the current job and needs another page, block, workflow, policy, or hold state. This boundary prevents the hub from becoming a catch all archive.
Connect the graph
The graph becomes readable when hierarchy, distance, proximity, context windows, internal links, and structured identity agree.
The route should make the next action obvious to a beginner while preserving the evidence, dependencies, exclusions, and review burden an advanced operator needs.
Resolve conflict
Audits, conflict resolution, disambiguation, and maintenance stop the constellation from splitting into competing versions.
A completed handoff records what was accepted, what remains uncertain, who owns the next action, which trigger reopens the decision, and when the system should be reviewed again.
Worked progression
The same hub supports five levels of decision maturity.
The route becomes more connected as the operator gains context. The advanced path does not replace the beginner path; it adds evidence, dependencies, ownership, review, and maintenance.
Start with Entity Support Pages, Entity Consistency, Entity Conflict Resolution. The aim is to learn the category language, recognise the main asset roles, and avoid solving a structural problem with an unstructured content request.
Move into Entity Support Pages, Entity Consistency, Entity Conflict Resolution. At this level the operator defines what belongs in the current asset, what belongs elsewhere, which inputs are approved, and which decision must be completed before production begins.
Use Entity Support Pages, Entity Consistency, Entity Conflict Resolution. The practitioner produces a map, brief, block, rewrite, link route, answer form, schema graph, comparison, template, or policy action while keeping the approved boundary visible.
Review Entity Support Pages, Entity Consistency, Entity Conflict Resolution. Advanced work separates symptoms from causes, keeps alternative explanations visible, ranks repair priorities, and avoids changing strong parts of the system without evidence.
Use Entity Support Pages, Entity Consistency, Entity Conflict Resolution. Governance adds owners, approvals, versions, refresh triggers, exception rules, change records, measurement, and a safe route when the evidence no longer supports the existing model.
Why the main node exists
The hub holds the broad journey while child assets own focused depth.
The hub is a semantic and behavioral contract.
The parent node defines Entity SEO, shows the complete branch system, and explains how the parts connect. It does not absorb every child lesson. The child assets earn their own URLs by owning a narrower reader task, decision, process, comparison, audit, template, policy, or production stage.
That split creates a cleaner journey. A beginner can understand the category without reading every guide. A practitioner can jump to the owned task without losing the parent context. An advanced operator can inspect dependencies, overlap, evidence, and governance without turning the hub into an unstructured knowledge dump.
The internal links follow the same model. The hub links down to every core child. Children link back to the hub. Close siblings link across when the reader has reached the point where the relationship becomes useful. Connected category hubs receive the work when the next job changes discipline.
Six rules protect the hub and ring.
- One parent topic. The H1, opening, route selector, journey, and index stay centered on Entity SEO.
- Complete visibility. All 27 child assets remain accessible from the main node and are not hidden behind a shortened archive.
- Distinct ownership. Every child earns a focused job that the hub should not carry in full.
- Progressive depth. Beginner, guided, practitioner, advanced, and operator routes use the same system at different levels of decision complexity.
- Evidence before expansion. New pages, blocks, routes, claims, and policies require enough approved material and a clear owner.
- Maintenance after release. Live signals, product changes, platform changes, legal updates, and user feedback can reopen the model through a recorded review route.
Advanced operating controls
A complete hub is maintained as a system, not published as a one time archive.
Advanced use adds ownership, evidence, change records, review triggers, and route quality. These controls keep the category useful as the site, product, search environment, and user needs change.
Ownership
Every query, entity, page, block, link, policy, and output has one accountable home.
Evidence
Claims, examples, product facts, links, and search observations retain their source and confidence.
Boundary
Related work stays outside the asset when it changes the page job or exceeds the approved scope.
Approval
Pass, revise, hold, and block states remain visible through the production handoff.
Maintenance
Owners, dates, triggers, versions, and refresh actions keep the hub and child assets current.
Measurement
Live signals can support or challenge the plan, but one metric does not prove the cause.
Connected category hubs
Move across the operating system when the current category exposes the next job.
The connection is based on workflow dependency and user progression rather than topical similarity alone.
Semantic SEO
The Semantic SEO hub explains how meaning is built through entities, intent, context, passage structure, coverage, retrieval, and relationships rather than phrase repetition.
Open the Semantic SEO HubSchema Markup
The Schema hub turns approved visible content and stable entity ownership into a maintained graph with accurate types, properties, identifiers, page roles, validation, and current search feature boundaries.
Open the Schema Markup HubContent Briefs
The Content Briefs hub turns approved site and page decisions into a writer ready operating plan with page job, intent, entities, section roles, evidence, answer formats, internal links, exclusions, and approval controls.
Open the Content Briefs HubInternal Linking
The Internal Linking hub connects pages by meaning, page role, journey stage, proof need, support need, and next useful action rather than by loose keyword mention.
Open the Internal Linking HubQuestions
Entity SEO Hub questions.
What is the first entity decision?
Choose the main entity and the page that owns it.
Does every related concept belong on the page?
No. Support entities must clarify, compare, prove, sequence, or route the main job.
How do entity pages connect to schema?
Visible identity and relationships come first. Schema expresses approved entities and properties through stable identifiers.
What does an entity audit return?
It returns identity, hierarchy, support, placement, conflict, ownership, link, and next workflow actions.
Next route
Start with the current state, choose the owned asset, and move only when the evidence supports the next stage.
MIRENA connects the category decision to source context, planning, production, review, internal routes, and the final handoff. The hub remains the main node as the category grows.
Founder access is €20 for each 30 day subscription period excluding VAT, with one seat and one active MIRENA instance. OpenAI account rules, plan charges, model access, availability, and usage limits remain separate.