Orient
Learn the language, page roles, evidence rules, and first route.
Main category hub · Graph compiler
Move through Schema Markup from first principles to governed practice.
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.
The hub is the main node for 25 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.
25 complete assets
5 learning levels
5 entry states
One main category node
Beginner route
Understand JSON LD, page identity, site identity, breadcrumbs, and the difference between Schema.org and Google features.
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 entity identity, page role implementation, commercial fields, review integrity, debugging, validation, release, and maintenance.
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 foundation
Recommended route
Start with Schema for SEO, JSON LD Basics, WebSite, WebPage, and Breadcrumb Schema.
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 entity identity
Recommended route
Use Organization, Person, sameAs, Entity Markup, and Identity Across Pages.
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 page role markup
Recommended route
Choose Article, Product examples, SoftwareApplication, Service, Category, Comparison, or Use Case routes.
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 an implementation example
Recommended route
Use the Article, Organization, Product, and HowTo example references.
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 validation and governance
Recommended route
Use Prioritization, Debugging, Rich Results Test, Review Rules, and FAQ Schema.
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 · Graph compiler
The interface mirrors the way the category is meant to be understood.
Graph compiler 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.
CenterSchema Markup
EntryUnderstand JSON LD, page identity, site identity, breadcrumbs, and the difference between Schema.org and Google features.
DepthGovern entity identity, page role implementation, commercial fields, review integrity, debugging, validation, release, and maintenance.
MetaphorGraph compiler
Asset count25
Next routeEvidence decides
Complete child asset index
All 25 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 Identity Across Pages
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetUse Case Page Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetComparison Page Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetCategory Page Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetSchema Markup Prioritization
Rank the available work by ownership, value, weakness, evidence, effort, risk, and dependency.
Open the assetSchema Debugging
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetRich Results Test Guide
Use this Schema Markup asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetReview Snippet Rules
Use current search evidence to choose or review the visible answer form without promising a search presentation.
Open the assetSoftwareApplication Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetService Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetPerson Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetWebPage Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetWebSite Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetBreadcrumb Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetArticle Schema Examples
Inspect a worked model that shows how loose inputs become a structured and reviewable result.
Open the assetOrganization Schema Examples
Inspect a worked model that shows how loose inputs become a structured and reviewable result.
Open the assetProduct Schema Examples
Inspect a worked model that shows how loose inputs become a structured and reviewable result.
Open the assetHowTo Schema Examples
Inspect a worked model that shows how loose inputs become a structured and reviewable result.
Open the assetArticle Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetsameAs and Entity Identity
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetOrganization Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetEntity Markup
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetFAQ Schema
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetJSON LD Basics
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetSchema for SEO
Represent approved visible content and stable entities through accurate types, properties, identifiers, validation, and maintenance.
Open the assetOperator field guide
Read the graph compiler 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.
Anchor the identity
The graph compiler starts with visible content, canonical URLs, page roles, and stable entity identifiers.
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.
Select the type
Types and properties are added only when they truthfully describe the approved page and its relationships.
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.
Compile the graph
Organization, WebSite, WebPage, BreadcrumbList, people, products, services, articles, and collections connect through stable references.
The route should make the next action obvious to a beginner while preserving the evidence, dependencies, exclusions, and review burden an advanced operator needs.
Validate the release
Validation, debugging, feature support, commercial updates, review integrity, rendering, and template ownership keep the graph accurate.
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 Identity Across Pages, Use Case Page Schema, Comparison Page Schema. 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 Identity Across Pages, Use Case Page Schema, Comparison Page Schema. 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 Identity Across Pages, Use Case Page Schema, Comparison Page Schema. 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 Identity Across Pages, Use Case Page Schema, Comparison Page Schema. 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 Identity Across Pages, Use Case Page Schema, Comparison Page Schema. 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 Schema Markup, 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 Schema Markup.
- Complete visibility. All 25 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.
Entity SEO
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.
Open the Entity SEO HubSERP Features
The SERP Features hub observes current search presentations, chooses the answer form that fits the query, checks current eligibility and platform rules, and routes work into visible content, entity support, prioritization, or recovery.
Open the SERP Features HubDocs
The Docs hub is the operating manual for preparing inputs, selecting workflows, understanding outputs, reviewing approvals, and moving through MIRENA without losing the source context.
Open the Docs HubTopical Mapping
The Topical Mapping hub turns topics, URLs, queries, business goals, user states, and existing pages into a governed architecture with page roles, cluster homes, overlap controls, publishing order, and useful next routes.
Open the Topical Mapping HubQuestions
Schema Markup Hub questions.
Does more schema create a stronger graph?
No. The strongest implementation is the smallest complete graph that truthfully describes the visible asset.
What comes before schema type selection?
Visible content, page role, canonical entity ownership, and stable identifiers.
Does Schema.org support equal Google support?
No. Schema.org is a broad vocabulary. Google supports a smaller and changing set of search presentations.
When should final markup be generated?
After visible content, URLs, commercial fields, reviews, identities, and approval states are settled.
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.