§ Executor · The entity layer of your site
HubForge.
Auto-creates and maintains entity hub pages for the people, places, organizations, products or topics you cover. Cross-linked from every article that mentions them. Maintained on schedule, never stale.
01 What it does
HubForge gives every entity on your site a canonical home. Each artist, brand, person, topic or product gets a hub page with a real biography, validated identity links, cross-references to every article that mentions them, and the structured-data signals search engines and LLMs use to decide who is authoritative.
Topical authority is the single biggest organic-growth lever in 2026. Sites that build entity hubs out-compete sites that don't, in both classical search and AI-search. HubForge is the platform that builds and operates them at the rate your editorial output demands, without a landing-page sprint.
Reactive hub creation
When a new piece of content mentions an entity that doesn't have a hub yet, HubForge generates one — researched, written, and published — without an editorial brief.
Biography re-sync
A standing cadence re-validates every hub against authoritative sources. Biographies refresh when facts change; outdated framings get rewritten.
Identity-link health
External identity links (sameAs references — official sites, Wikipedia, Wikidata, domain-specific registries) are checked weekly. Broken or hijacked links are surfaced before they degrade authority.
Cross-linking on publish
Every new article that mentions an entity gets an automatic link to its hub. Every hub gets a back-reference. Internal-link graph grows on its own.
02 How it works
HubForge runs four durable workflows side by side. One reacts to new content; three maintain what's already live.
Detect. On every publish, HubForge scans the article body for entity references. New entities (no hub yet) get queued for creation; known entities trigger the cross-link routine.
Research. For a new entity, HubForge pulls validated facts from the authoritative sources for your domain — Wikipedia, Wikidata, your industry's registries, your own internal data — with a strict name-equality check that refuses fuzzy matches.
Compose. A purpose-built writer drafts the hub: biography, key facts, identity links, structured-data block. The draft includes narrative evidence — claims tied to sources, not free invention.
Publish & link. The hub lands as a real page on your site, schema-validated by SchemaForge, with cross-links to every existing article that mentions the entity. New articles auto-link going forward.
Maintain. Three standing crons run weekly — biography re-sync, identity-link healthcheck, freshness sweep. Drift surfaces in the Atlas brief; fixes ship through the same pipeline.
03 What it replaces
HubForge collapses the work of building and maintaining topical authority — usually a six-figure SEO contract or a missing capability entirely — into one operated layer.
04 Live receipts
HubForge currently operates the entity layer of a live reference deployment — an editorial publishing platform under Umbra Group. Receipts below are verifiable on the live site and in the audit log.
Reference deployment — sustained since 2026-05
- 240+ entity hubs live, each with biography, identity links, and full cross-link graph back to articles that mention them.
- Reactive creation on every publish — articles mentioning a new artist trigger hub generation in the same cycle.
- Three maintenance crons running weekly — biography re-sync, identity-link healthcheck, freshness sweep.
- Name-equality verification prevents the import-the-wrong-entity failure mode. Any near-match the registry returns under a different canonical name is rejected before it pollutes the hub.
- Schema cross-poll live with SchemaForge — every hub emits the schema variant the entity needs (Person, Organization, Product, Place, MusicGroup, etc.) with canonical identity links.
Source — Live site + internal observatory · 2026-05
05 Pairs with
HubForge is the entity backbone the rest of the stack draws on.
SchemaForge
Hub canonical IDs flow into every article's schema so entities resolve consistently site-wide.
Pairs with — on-pageOnPage Doctor
Audit findings about missing entity links or thin hub pages route directly into the HubForge maintenance pipeline.
Operated by — cockpitAtlas
New-hub events, identity-link failures and biography drift surface in the Atlas morning brief.
Pairs with — discoveryPulseRadar
PulseRadar finds new entities your market is talking about; HubForge gives them a home before competitors do.
06 Deploy in your org
HubForge is deployed during a Lighthouse Sprint that scopes your entity model — what counts as a hub-able entity in your domain (people? products? clinics? properties? legal cases?) and what authoritative sources we draw from.
Entity scoping (Pulso). We catalogue the entities your content references today, identify which ones already have pages and which don't, and define the hub template per entity class.
Source binding (Sprint). Authoritative sources are wired — Wikidata for general entities, the right registry for each industry (medical, legal, financial, music, etc.), and your own internal data where you have it. Name-equality guards are configured per source.
Backfill & activate (Watch). A one-time backfill pass creates hubs for the entities already mentioned across your existing content. From there, every publish is reactive. Maintenance crons go live behind Atlas.
07 Pricing line
HubForge is included as an executor in any Lighthouse Sprint that targets topical authority or entity coverage. Operating cost is bundled into your Lighthouse Watch tier and scales with hub count.
Standalone deployment (HubForge without other SEO executors) is available from the base Sprint tier. Detailed pricing in the Sprint framework.
08 Engage
See 240+ live hubs running on autopilot.
We walk you through the live reference deployment: reactive hub creation triggered by a fresh publish, the weekly biography re-sync catching a stale fact, and identity-link healthcheck flagging a broken sameAs.