Brain Name: Content Brain
Document Type: Framework
Status: Active
Version: v2.1
Authority: HeadOffice
Applies To: Content Brain, Affiliate Brain, Data Brain, Conversion Brain, mwmscontentbrain.site operational topic planning, SEO authority architecture, hub page planning, spoke page planning, and future topic cluster planner development
Parent: Content Brain
Last Reviewed: 2026-05-08

Content Brain Topic Cluster And Hub Architecture Framework

Operational Copy Notice

This page is an operational copy used on mwmscontentbrain.site.

MCR remains the source of truth.

If this page conflicts with the MCR version, the MCR version overrides it.

This protects source-of-truth discipline.

Purpose

The Content Brain Topic Cluster And Hub Architecture Framework defines how MWMS structures content into interconnected topic clusters.

Its purpose is to:

build topical authority

improve rankings

enhance crawl efficiency

support internal linking systems

guide user navigation

support conversion pathways

support affiliate funnel education

support trust-building content paths

support content refresh and expansion planning

Search engines reward:

topical depth

structured relationships

intent alignment

internal linking coherence

useful information architecture

This framework ensures content is not created as isolated pages, but as part of a connected authority system.

Scope

This framework applies to:

topic cluster planning

hub page planning

spoke page planning

SEO content architecture

affiliate support content ecosystems

authority-building content systems

internal linking structure

URL structure planning

content expansion planning

content refresh planning

conversion support content paths

reader navigation structure

This framework governs how Content Brain organises groups of related pages into connected authority systems.

It does not govern:

individual article drafting by itself

offer approval

campaign approval

paid traffic decisions

conversion page architecture by itself

technical SEO implementation by itself

plugin implementation

Supabase implementation

formal experimentation decisions

Those remain governed by the relevant Brain, framework, protocol, standard, or implementation layer.

Core Principle

Authority is built through connected knowledge.

A single page cannot dominate a topic.

A structured cluster can.

Content should not be created as disconnected pages.

Every important content asset should have a role inside a wider content architecture.

Definition

Topic Cluster

A topic cluster is a group of related content pages covering a central theme.

A topic cluster helps MWMS build authority around a subject by covering the topic from multiple useful angles.

Hub Page

A hub page is a primary page that:

defines the core topic

aligns with dominant SERP intent

links to supporting pages

acts as authority anchor

guides reader navigation

connects the cluster together

supports conversion pathways where relevant

Spoke Pages

Spoke pages are supporting pages that:

target subtopics

match specific search intents

link back to the hub

link to relevant related spokes

deepen topical coverage

answer specific reader questions

support the authority of the hub

Cluster Types

Content Brain must distinguish between three cluster types.

Keyword Cluster

A keyword cluster is a group of related keyword variations.

Purpose:

identify search demand

understand search language

group related queries

avoid keyword cannibalisation

Topic Cluster

A topic cluster is a group of pages covering a theme.

Purpose:

build authority

support reader understanding

organise content around meaning

connect related content assets

URL Cluster

A URL cluster is the actual structure of pages and links.

Purpose:

control crawl signals

control ranking signals

support internal linking

support site navigation

show relationship between pages

Cluster Alignment Rule

These three must align:

Keyword Cluster

Topic Cluster

URL Cluster

Misalignment causes:

ranking instability

keyword cannibalisation

weak authority signals

poor crawl behaviour

confusing user journeys

fragmented content structure

Role Within MWMS

This framework supports:

Content Brain architecture

Affiliate Brain content ecosystems

Conversion Brain navigation clarity

Data Brain crawl efficiency

Research Brain topic signal translation

Ads Brain landing support content

It directly influences:

SEO rankings

topical authority

crawl behaviour

internal linking strength

reader navigation

conversion support

affiliate funnel education

trust-building journeys

Cluster Structure Model

Each important topic should follow this basic model:

Hub Page

Spoke Pages

Contextual Supporting Links

The structure should be easy for both users and search engines to understand.

Example Cluster

Hub:

Best Survival Water Solutions

Spokes:

How Water Contamination Happens

Emergency Water Storage Guide

Best Portable Water Filters

Water Purification Methods Explained

How To Store Water Safely

Signs Your Water May Not Be Safe

The hub explains the main topic.

The spokes deepen specific areas of understanding.

The internal links connect the cluster into a coherent authority system.

Linking Rules

The standard linking structure is:

Hub links to all major spokes.

Spokes link back to hub.

Spokes link to relevant related spokes.

Supporting pages should not exist as orphan pages.

Internal links should help the reader first.

Hub Page Requirements

Hub pages must:

match dominant SERP intent

provide structured overview

act as navigation layer

connect all supporting content

define the core topic clearly

guide the reader to next useful pages

support conversion pathways where relevant

avoid becoming a shallow doorway page

Hub pages should include:

summary of subtopics

clear navigation

contextual internal links

cluster overview

trust signals

conversion pathways where appropriate

links to key supporting pages

Hub pages must be useful on their own.

They must not only exist as link lists.

Spoke Page Requirements

Spoke pages must:

target a specific search intent

align with SERP expectations

provide detailed explanation

include information gain

answer a defined reader question

support the hub topic

avoid competing with the hub

Spoke pages should:

link back to hub

link to related spokes

reinforce topic depth

resolve a specific problem or question

support authority building

support reader progression

Information Gain Integration

Clusters must provide more value than competitors.

Each cluster should:

fill content gaps

improve clarity

add unique insights

include examples, tools, or data where useful

answer missing questions

make complex ideas easier to understand

support decision clarity

Information gain must exist at both:

page level

cluster level

A cluster that only repeats what competitors already cover will not create durable authority.

Entity Coverage Rule

Clusters must include:

primary entities

supporting entities

related concepts

topic-specific terms

contextual relationships

The purpose is to signal topical completeness.

Missing important entities can reduce:

relevance

ranking potential

topical completeness

reader usefulness

Entity coverage must be natural.

Do not stuff entities without improving reader understanding.

SERP Alignment Rule

Each page must match what Google is rewarding for the target query or topic.

Each page should align with:

dominant content type in SERP

expected depth

expected format

expected user intent

expected supporting sections

expected trust signals

Mismatch can result in:

ranking failure

poor engagement

wrong content format

reader dissatisfaction

SERP alignment does not mean copying competitors.

It means understanding what user need the SERP is satisfying.

Internal Linking Rules

Bidirectional Linking

Hub pages should link to relevant spoke pages.

Spoke pages should link back to the hub.

This helps establish topic relationships.

Contextual Linking

Spokes should link to related spokes when it genuinely helps the reader.

Contextual links should explain why the linked page is useful.

Modular Linking

For scaling, MWMS may later use:

Architecture Rules

Flat Architecture Rule

Important pages should be accessible within 2 to 3 clicks where possible.

Deeply buried content weakens discoverability.

Orphan Page Rule

Every important page must have internal links pointing to it.

Every important page should link to relevant related pages.

Orphan pages weaken authority and crawl efficiency.

Depth Control Rule

Avoid unnecessarily deep nested structures.

A topic cluster should be clear and usable, not hidden inside complex hierarchy.

Keyword Mapping Rule

Each page should have:

one primary keyword or primary topic

supporting keywords

defined search intent

defined page role

Pages must not compete for the same primary keyword or same exact intent.

Avoid keyword cannibalisation.

Navigation Clarity Rule

Users must:

understand where they are

easily navigate

find related content

move to the next useful page

Navigation must support the reader journey.

Conversion Integration Rule

Clusters must support conversion where appropriate.

Hub pages may:

guide toward CTA

connect content to offers

send readers to relevant support pages

build broad trust

Spoke pages may:

build trust

build understanding

answer objections

prepare users for action

support comparison

reduce uncertainty

Content Brain supports conversion pathways, but Conversion Brain owns conversion architecture.

Affiliate Integration Rule

Affiliate content should exist inside clusters.

It should not exist as standalone isolated pages.

Supported affiliate content improves:

reader trust

decision clarity

offer understanding

conversion performance

pre-sell effectiveness

Affiliate content must still respect Affiliate Brain authority and compliance requirements.

Content Brain must not approve offers.

Testing And Optimization

Clusters should be reviewed and improved over time.

Possible test variables:

internal linking structure

hub design

content depth

navigation flow

CTA placement

spoke expansion

FAQ sections

comparison sections

trust sections

Measurement metrics may include:

rankings

crawl frequency

engagement

conversion assist

internal link clicks

content refresh signals

topic growth

Where testing becomes formal, use Experimentation Brain discipline.

Content Brain should not over-interpret weak data.

Content Expansion Rule

Clusters are living systems.

Expand a cluster when:

new keywords appear

new content gaps are identified

SERP changes

reader questions repeat

new objections appear

offer education needs grow

product understanding needs grow

trust gaps become visible

content performance suggests opportunity

Expansion must be deliberate.

Do not add pages only to increase volume.

Cluster Planning Checklist

Before building a cluster, define:

Main topic:

Hub page:

Primary audience:

Search intent:

Business purpose:

Related offer if relevant:

Topic cluster role:

Primary keyword cluster:

URL structure:

Required spoke pages:

Internal linking plan:

Conversion pathway:

Trust support pages:

Information gain plan:

Entity coverage plan:

Refresh review point:

Feedback signal:

Hub Planning Checklist

Before creating a hub page, define:

Core topic:

Dominant SERP intent:

Hub purpose:

Target audience:

Required sections:

Spoke pages to link to:

Internal navigation structure:

Trust signals:

Conversion pathway:

Information gain angle:

Entity coverage:

CTA type where relevant:

Spoke Planning Checklist

Before creating a spoke page, define:

Specific subtopic:

Search intent:

Relationship to hub:

Reader question:

Primary keyword:

Supporting keywords:

Required sections:

Information gain:

Internal links to hub:

Internal links to related spokes:

Trust or proof needs:

Conversion support role:

Feedback signal:

Failure Modes Prevented

This framework prevents:

isolated content pages

weak SEO performance

poor internal linking

crawl inefficiency

keyword cannibalisation

incomplete topic coverage

weak authority signals

confusing user navigation

content duplication

random topic expansion

affiliate pages sitting outside useful content ecosystems

Relationship To Content Brain Topic Architecture Framework

The Topic Architecture Framework defines how topics should be selected and structured across the ecosystem.

This framework defines how related topics become connected clusters and hub systems.

Topic Architecture Framework equals topic selection and topic role.

Topic Cluster And Hub Architecture Framework equals connected page ecosystem.

Relationship To Content Brain SEO Content Brief Standard

The SEO Content Brief Standard defines how individual SEO content briefs are created.

This framework helps define the cluster, hub, and spoke context that each brief should fit into.

Relationship To Content Brain Internal Linking Strategy Framework

The Internal Linking Strategy Framework defines broader internal linking rules.

This framework applies those rules to topic clusters and hub systems.

Relationship To Data Brain

Data Brain supports cluster evaluation by measuring:

traffic

crawl behaviour

engagement

ranking movement

internal link clicks

conversion assist

Data Brain owns signal reliability.

Content Brain may use signals, but must not over-interpret weak data.

Relationship To Affiliate Brain

Affiliate Brain owns offer evaluation and testing readiness.

Content Brain may build clusters that support affiliate offers through:

educational content

comparison content

pre-sell content

trust content

FAQ content

review support content

Content Brain must not approve the offer itself.

Relationship To Conversion Brain

Conversion Brain owns conversion architecture.

Content Brain may support conversion through:

navigation clarity

trust-building pages

objection-handling spokes

message match support

CTA support pages

Content Brain must not replace Conversion Brain authority.

Relationship To Content Brain Copy Map

The Content Brain Copy Map classifies this page as:

Destination: Copy To Content Brain

Reason: Topic cluster and hub planning

Source Of Truth: MCR

Future Destination: mwmscontentbrain.site

Future Use: Topic cluster planning and hub architecture

Plugin Or UI Later: Possible hub and cluster planner

This operational copy follows that classification.

Future Plugin Or UI Candidate

This framework may later support:

Topic Cluster Planner

Hub Page Planner

Spoke Page Planner

Internal Linking Planner

Content Brief Generator

Content Refresh Queue

Content Operations Dashboard

These should not be built yet.

Manual topic cluster planning must prove operational need before plugin or UI development begins.

Drift Protection

The system must prevent:

standalone content pages

missing internal links

deep hierarchies

duplicate topic coverage

misaligned intent

keyword cannibalisation

hub pages without useful spokes

spokes without hub links

affiliate support pages disconnected from clusters

clusters without information gain

clusters without entity coverage

cluster pages being copied to mwmscontentbrain.site without Copy Map classification

plugin or UI cluster planners being built before manual use proves the structure

mwmscontentbrain.site replacing MCR source-of-truth authority

Architectural Intent

This framework ensures MWMS builds connected content ecosystems rather than isolated pages.

It transforms SEO from page optimisation into authority engineering.

The long-term intent is for Content Brain to build content structures that:

compound authority

improve internal linking

strengthen search visibility

support affiliate education

support conversion pathways

guide user navigation

produce measurable signals

support refresh and expansion over time

Manual cluster planning must work first.

Plugin or UI support can come later only when repeated use proves the need.

Final Rule

If content is not connected, it will not rank as well as it could.

If clusters are incomplete, authority will not build properly.

If hub, spoke, keyword, and URL structures are misaligned, the content system becomes unstable.

Every important content asset should belong to a clear topic structure, link structure, and reader journey.

Change Log

Version: v2.1
Date: 2026-05-08
Author: HeadOffice
Change: Created operational copy for mwmscontentbrain.site. Added Operational Copy Notice, Source Of Truth protection, Parent update for live site, expanded scope, cluster planning checklists, hub planning checklist, spoke planning checklist, cross-brain relationships, manual workflow before automation discipline, future plugin or UI boundaries, and drift protection against mwmscontentbrain.site replacing MCR authority.

Version: v2.0
Date: 2026-05-02
Author: HeadOffice
Change: Upgraded Topic Cluster Framework to include keyword vs topic vs URL cluster distinction, SERP alignment rules, entity coverage, information gain integration, and testing layer based on CXL SEO intelligence.

Change Impact Declaration

Pages Created:
Content Brain Topic Cluster And Hub Architecture Framework

Pages Updated:
None

Pages Deprecated:
None

Registries Requiring Update:
None

Canon Version Update Required:
No

Change Log Entry Required:
No

END CONTENT BRAIN TOPIC CLUSTER AND HUB ARCHITECTURE FRAMEWORK v2.1