Topic clusters are an information architecture, not a ranking hack. A hub helps people and crawlers navigate a coherent subject; supporting pages solve distinct sub-tasks. “Compounding” is a business hypothesis and must be measured, not promised.

// concept

Define the Subject Boundary

Create a map:

// prompt — copy me8 lines

hub purpose and audience
subtasks/questions
existing URLs and performance
gaps, overlaps, outdated pages
distinct evidence per page
internal link relationships
conversion/support path
owner and maintenance cadence

The hub should summarize and route, not repeat every supporting page. Each child must stand alone and link back/contextually where useful. Avoid orphan pages and sitewide exact-match link blocks.

// concept

Consolidate Before Expanding

Audit current pages. Merge overlapping intent when one stronger page serves the task. Preserve valuable sections, links, and analytics context. Redirect removed URLs only to a genuinely equivalent destination; otherwise use an appropriate removal status.

Use breadcrumb and structured data only when visible and supported. XML sitemaps help discovery but do not replace navigation.

// worked_example

Worked Example

An agency builds an n8n for Pakistani businesses hub. Children cover cloud/self-hosted decision, webhook security, WhatsApp consent, invoice workflow controls, and client handover. Each has separate evidence and user task.

Two old posts both cover “n8n hosting.” The team consolidates them, updates official sources, redirects the weaker URL, repairs internal links, and tracks query/page data over comparable periods. The hub links to the paid service only after useful navigation. It does not create a child for every keyword synonym.

// failure_cases

Failure Cases to Diagnose

6 cases to diagnose

Pillar is 8,000 words by default
fit the navigation task.
Children overlap
merge or clarify intent.
All links use exact keyword
descriptive natural anchors.
Redirect irrelevant pages to hub
map only equivalents.
Cluster built without existing inventory
audit first.
Traffic growth called compounding proof
control for season/site changes.

// pakistan_angle

Pakistan Angle

Build clusters around real local workflows, not service + every city. City/province pages require distinct coverage, rules, team, evidence, or inventory. Otherwise one national/localized guide may be more useful.

For English/Urdu/Roman Urdu variants, define canonical/hreflang and editorial parity deliberately. Automatic duplicates can fragment maintenance and search signals.

Create a maintenance map alongside the cluster map. Give every page an owner, evidence-review date, update trigger, and retirement rule. If the team cannot maintain twelve proposed children, publish the two highest-value tasks first and learn from real use before expanding. A smaller accurate cluster is better than a large stale one.

// hands_on

Hands-On Exercise

5 steps

Inventory one subject’s URLs.
map hub/subtasks/overlaps.
choose update/merge/new/remove.
design contextual internal links.
define before/after measurement and maintenance.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

3 official sources — check every claim yourself