A Field Guide / 2026 № 01
The Methodology Behind Owned Categories

Content
Hubs.

A curated collection of pages on a single topic, anchored by a pillar, branched into spokes, and linked into a structure that compounds in authority faster than scattered articles ever could.

↓ Scroll
§ 01 — Definition

What a hub
is, and what it isn't.

A content hub sits between a website and a blog. Smaller than the first, larger than the second. It occupies a dedicated section, organized around a central topic, with intentional curation rather than chronological accumulation.

↗ A Hub Is

  • Curated — every page is intentional
  • Topic-specific — one hub, one topic
  • Pillar-anchored — one overview defines the topic
  • Interlinked — pages reference each other
  • Searchable — readers jump to subtopics directly
  • Mission-driven — exists to hit a measurable goal

↘ A Hub Is Not

  • A blog — chronological, unfiltered
  • A resource dump — every PDF in one folder
  • A homepage section — mixed-intent conversion
  • One long article — pillar without spokes
  • A cluster without a center — spokes without a pillar
  • An e-commerce category page — that's a product catalog
The order is non-negotiable. Strategy first, model second, structure third, content last. Reverse it and you produce a blog with relabeled navigation.
— First Principle of Hub Design
§ 02 — Architecture

The four
hub models.

Every hub commits to one of four structural models. Mixing models within a single hub fragments the reader's mental map and dilutes search authority. Choose deliberately.

A.

Hub-and-Spoke

One pillar. Multiple spokes. The default.

A central pillar page covers the topic at overview level. Spoke pages radiate outward, each going deep on one subtopic. Optional sub-spokes branch off spokes for further depth.

Best for
Educational guides, evergreen explainers, category definition
Page count
5–20 spokes per pillar
Pillar role
Comprehensive overview with table of contents
Failure mode
Pillar grows into a 10K-word monster trying to replace spokes
Model A — Hub-and-Spoke spoke spoke spoke spoke spoke spoke Pillar topic overview
B.

Content Library

Three tiers. Multiple topic areas. One umbrella.

A library root lists several topic areas. Each topic has its own index page. Each index lists subtopic pages. The structure handles loosely related topics that share a common purpose.

Best for
Help centers, knowledge bases, multi-product docs
Page count
3–8 topic indexes × 5–15 subtopic pages
Pillar role
Library root navigates; topic indexes mini-pillar
Failure mode
Topic indexes become thin link-lists with no context
Model B — Content Library subtopic pages topic A topic B topic C Library Root navigation
C.

Topic Gateway

Wiki-style entries. Cross-referenced. Self-contained.

Each page is a wiki-style entry: short summary at the top, depth below, links to related entries. A gateway index lists everything. Readers arrive from search and want quick orientation before going deeper.

Best for
Glossaries, comparison pages, alternatives, country / city pages
Page count
20–100+ entries
Pillar role
Gateway index lists or filters all entries
Failure mode
Entries become near-duplicates with no unique angle
Model C — Topic Gateway entry entry entry entry Gateway index
D.

Content Database

Filterable. Structured. Schema-driven.

A filterable, searchable collection of structured items. Each record shares the same schema. The landing page exposes filters, sort, and search. Each record has its own detail page.

Best for
Tool directories, alternatives, templates, integrations
Page count
50–500+ records
Pillar role
Database landing is a UI, not an article
Failure mode
Inconsistent record quality, synthetic data filling gaps
Model D — Content Database filters category price tags rating sort by name structured records · same schema — filterable · searchable —
§ 03 — Operating Principles

Eight rules that
hold every hub together.

Regardless of model. Regardless of topic. Regardless of audience. These are the structural commitments that distinguish a hub from a folder full of articles.

01

One topic, one hub

If a topic splits into two distinct audiences or two intents, that's two hubs. Topical drift — accepting adjacent content because it "kind of fits" — is the most common failure mode.

02

Pillar = overview

The pillar defines the topic. It is comprehensive and primarily educational. Product positioning appears in structured formats and stays at or below 30% of total volume.

03

Spokes = depth

Each spoke covers one subtopic in depth. A spoke is not a summary of the pillar — it is a specialized treatment of a narrower question.

04

Rabbit-hole linking

Every page offers at least two next destinations within the hub. No dead ends. No orphans. The reader stays in the cluster as long as they're learning.

05

Searchability

The reader can jump straight to the subtopic without reading the pillar first. Implementation varies by model — table of contents, filters, gateway index — but the requirement holds.

06

Mission with a metric

Every hub has a one-sentence mission with a measurable target and a timeframe. Without this, you have a content folder, not a hub.

07

CTA matches stage

Primary CTA matches the page's funnel stage. Secondary CTAs may sit one stage deeper, in FAQ or late-page positions, for readers who arrive already warm.

08

Strategy first

Mission, model, structure, then content. Reverse this order and you produce a blog with new navigation — not a hub. The order is non-negotiable.

§ 04 — Linking Anatomy

The rabbit-hole:
good vs broken.

A healthy hub keeps readers moving inside it. Every page is reachable from multiple directions and offers multiple exits — all leading deeper into the topic. An unhealthy hub leaks readers back to search results.

↗ Healthy pillar 2+ inbound · 2+ outbound · no dead ends
↘ Broken orphan → exit pillar no siblings · orphan node · readers leak out
§ 05 — Anti-Patterns

Failures that
look like hubs.

Most "content hubs" in the wild are blogs with new branding, or single articles overpromising as clusters, or pages so heavily product-pitched they read as landing pages. The patterns are familiar.

The Renamed Blog
Symptom"Hub" is just chronological articles with new navigation. No pillar. No mission. No curation.
FixDefine a topic and mission. Deprecate off-topic posts. Write a pillar. Then call it a hub.
The Pillar That Sells
SymptomSales-leaning copy in every section. Customer logos above the educational content. Demo CTA in the first scroll.
FixEducational answer first. Product positioning as one structured callout, capped at 30% of volume.
The Orphan Spoke
SymptomA new spoke ships. Pillar links to it. Nothing else does. Thirty days later, it still has only one inbound link.
FixSchedule a cross-linking pass within 30 days of every spoke launch. Update 2–3 siblings to reference it.
The Pillar Without Spokes
SymptomOne long article called a hub. No subtopic pages, no depth, no expansion path.
FixEither accept it as an article and strip the "hub" branding, or commit to writing five spokes within the next quarter.
Topical Drift
SymptomHub on Topic A starts accepting articles on Topic B because "they're related." Authority for both topics dilutes.
FixNarrow back to Topic A, or split into two hubs with separate pillars.
Synthetic Records
SymptomDatabase fields filled with plausible-sounding but fabricated values when real data is missing. Looks fine until someone fact-checks.
FixShow a "data unavailable" indicator. Missing data is more trustworthy than fabricated data.
Mixed Models
SymptomHub uses both database filters and pillar-and-spoke structure for the same content. Reader's mental map fragments.
FixPick one model and refactor. If the content genuinely needs both, you have two hubs.
Strategy Last
SymptomArticles written first, grouped into "hub" navigation later. Mission written after the fact. Model implicit.
FixStop adding pages. Define mission, model, structure. Audit existing pages against the structure. Refactor.
§ 06 — Choosing a Model

How to pick
the right model.

Walk through these questions in order. Stop at the first match. The questions are deliberately ordered so that the first matching answer is the most structurally appropriate model for the use case.

1.
Are you organizing many records that share the same schema and need filtering or sorting?
→ Model D · Database
2.
Are you building many short, wiki-style entries each deserving their own page, with cross-references between them?
→ Model C · Gateway
3.
Do you have several loosely related topic areas under one umbrella, each needing its own index?
→ Model B · Library
4.
Do you have one central topic that branches into natural subtopics?
→ Model A · Hub-and-Spoke
5.
Does the topic have less than five spokes worth of depth?
→ Not a hub yet
§ 07 — In Summary

A hub is
a discipline,
not a folder.

The methodology is simple. Define the topic. Pick the model. Anchor the pillar. Branch the spokes. Link the rabbit-hole. Match the CTA to the funnel stage. Hold the discipline over time, and the hub compounds. Drop any of these, and you have a blog.