Content Marketing · Advanced · 13 min read
Topical Map Example: How to Build a Hub-and-Spoke Cluster for Espresso Machines
See a real topical map before/after for a coffee blog targeting espresso machines for home. Learn hub-and-spoke structure, entity coverage, and cluster planning for SEO authority.
For: SEO strategists, content managers, bloggers, niche site owners, affiliate marketers
The scenario
A food and beverage blogger runs a coffee-focused site with 40 published posts and a domain rating of 28. The site ranks inconsistently — some posts hit page one, most plateau at positions 12–20. An SEO audit reveals the root cause: the content covers coffee broadly with no topical depth in any sub-niche. Google has not established the site as an authority on any specific coffee topic. The blogger wants to build topical authority around 'espresso machines for home' — a cluster with high purchase intent and strong affiliate revenue potential. Their first attempt at a topic list looks like a flat collection of keywords with no hierarchical structure or entity coverage.
Original draft → Optimized version
Original draft
Espresso machines for home Best espresso machines Espresso machine reviews How to make espresso Espresso vs coffee Coffee grinder for espresso Espresso machine cleaning Best espresso beans How to use an espresso machine Semi-automatic vs automatic espresso machines Budget espresso machines
Optimized version
TOPICAL MAP: Espresso Machines for Home Site: [Coffee Blog] | DR: 28 | Cluster Goal: Topical authority + affiliate revenue HUB PAGE (Pillar): Title: The Complete Guide to Espresso Machines for Home (2026) URL: /espresso-machines-for-home Target keyword: espresso machines for home (8,100 searches/mo) Purpose: Ranks for the primary cluster keyword, links to all spoke pages, captures mid-funnel readers comparing options Content type: Comparison guide + buyer framework PRIMARY CLUSTER — Machine Types (spoke pages that define the topic space): 1. Semi-automatic espresso machines for home — /semi-automatic-espresso-machines (comparative guide) 2. Super-automatic espresso machine review — /super-automatic-espresso-machines (review roundup) 3. Manual lever espresso machines for beginners — /manual-lever-espresso-machines (explainer + picks) 4. Pod vs. manual espresso machines: which is better? — /pod-vs-manual-espresso (comparison) 5. Best budget espresso machines under $200 — /budget-espresso-machines (affiliate roundup) SECONDARY CLUSTER — Grind & Extraction (entity coverage: process knowledge): 6. Best espresso grinders for home use — /espresso-grinders-for-home 7. Grind size for espresso: the complete guide — /espresso-grind-size-guide 8. Espresso extraction explained: channeling, pressure, and taste — /espresso-extraction-guide 9. How to dial in an espresso shot — /how-to-dial-in-espresso SECONDARY CLUSTER — Beans & Roasts (entity coverage: input quality): 10. Best espresso beans for home machines — /best-espresso-beans 11. Light roast vs. dark roast for espresso — /light-vs-dark-roast-espresso 12. Single origin espresso: is it worth it at home? — /single-origin-espresso SECONDARY CLUSTER — Maintenance & Longevity: 13. How to clean an espresso machine (step-by-step) — /how-to-clean-espresso-machine 14. Espresso machine descaling guide — /descaling-espresso-machine 15. Common espresso machine problems and fixes — /espresso-machine-troubleshooting SUPPORTING CONTENT (informational, links to cluster): 16. Espresso vs. coffee: what's the actual difference? — /espresso-vs-coffee 17. How to make a latte at home without a steamer — /how-to-make-latte-at-home 18. The best espresso accessories for home baristas — /espresso-accessories ENTITY COVERAGE CHECKLIST: [x] Machine types (semi-auto, super-auto, manual, pod) [x] Grind process (grinder, grind size, extraction) [x] Input quality (beans, roast level, origin) [x] Maintenance (cleaning, descaling, troubleshooting) [x] Drinks (latte, espresso, comparison to drip) [ ] Water quality (target for cluster v2) [ ] Milk steaming (target for cluster v2) INTERNAL LINK ARCHITECTURE: - Hub page links to all 18 spokes - Each spoke links back to hub + 2–3 sibling spokes - Supporting content links to hub + nearest-intent spoke CLUSTER BUILD ORDER (priority sequence): Phase 1 (weeks 1–4): Hub page + primary cluster (posts 1–5) Phase 2 (weeks 5–8): Grind & extraction cluster (posts 6–9) Phase 3 (weeks 9–12): Beans + maintenance clusters (posts 10–15) Phase 4 (weeks 13–16): Supporting content + entity gap coverage (posts 16–18)
What changed: The original list has no hierarchy, no hub page, no entity coverage analysis, and no build order. It is a keyword list, not a topical map. The optimized map defines a pillar page, organizes spokes into thematic sub-clusters, identifies entity coverage gaps with a checklist, specifies internal link architecture, and phases the build to maximize early topical signal. A site that publishes the optimized map in sequence will see cluster pages begin to rank within 60–90 days of phase 2 completion. The original approach would produce 11 disconnected posts that Google treats as general-interest articles rather than a topical authority cluster.
Explanation
A topical map is the structural plan that separates sites with genuine topical authority from sites with a collection of loosely related articles. Google's ability to evaluate topical authority has improved dramatically since the Helpful Content updates — sites that demonstrate deep coverage of a semantic space (all the entities, sub-topics, and related questions that a topic contains) outrank sites with higher domain ratings but thinner coverage. The hub-and-spoke model is the most reliable architecture for building this authority: one pillar page covers the broad topic comprehensively, and spoke pages cover sub-topics in depth with internal links back to the hub.
For a coffee blog targeting espresso machines, the entity space includes machine types, grind process, bean quality, maintenance, output drinks, water quality, and accessories. A topical map that covers five of these eight entity areas with dedicated spoke pages and proper internal linking will signal authority to Google more reliably than 30 posts that mention all eight entities superficially. The build order matters as much as the content: publishing the hub page first and the primary cluster before supporting content ensures Google can crawl and index the cluster architecture before indexing the peripheral content.
Why it works
The hub page collects PageRank from all spokes and concentrates it on the primary keyword. Without a hub, internal link equity is distributed randomly across the site. A pillar page that ranks for the broad term (espresso machines for home) lifts all spoke pages because they share topical context.
Grouping spokes into thematic sub-clusters (grind, beans, maintenance) tells Google that the site covers the full semantic space of a topic, not just the most-searched keywords. Sites with complete entity coverage consistently outrank sites that target only high-volume terms.
Publishing the hub and primary cluster first creates an internal link architecture before supporting content exists. Google can establish the topic structure from week one, which means cluster spokes begin ranking faster than if they were published in random order.
The coverage checklist turns an intuitive process into a systematic one. Content managers who use an entity checklist publish clusters with fewer gaps, which means less remedial content creation later and faster topical authority recognition.
More variations
Entity coverage checklist only
Original draft
Topics covered: machines, cleaning, beans, how to make espresso
Optimized version
ENTITY COVERAGE CHECKLIST — Espresso Machines for Home: [x] Machine types: semi-auto, super-auto, manual lever, pod [x] Grind process: grinder selection, grind size, extraction theory [x] Input quality: bean selection, roast level, single origin [x] Maintenance: cleaning routine, descaling, troubleshooting [x] Output drinks: espresso, latte, comparison to drip coffee [ ] Water quality: TDS, filtration, impact on taste (cluster v2) [ ] Milk steaming: technique, equipment, temperature (cluster v2) [ ] Accessories: tampers, scales, knock boxes (cluster v2) COVERAGE SCORE: 5 of 8 entity areas covered. Sufficient for phase 1 authority signal. Schedule v2 entities after first 15 posts index and rank.
What changed: Entity coverage analysis is the difference between a topical map and a keyword list. The checklist format forces the content planner to identify which semantic areas are covered, which are missing, and which to defer. Google's entity graph for 'espresso machines' includes water quality and milk steaming — sites that cover these entities consistently outperform sites that don't, even at similar domain ratings.
Common mistakes (and how to fix them)
Mistake
Publishing spoke pages before the hub page exists. Spokes link to a hub that doesn't rank yet, which means they can't pass topical context through the cluster.
Fix
Publish the hub page first, even if it's a minimum viable version. Spoke pages should go live with a live hub page already indexed.
Mistake
Creating a topical map that only targets high-volume keywords. This leaves entity gaps that competitors with lower domain ratings can exploit.
Fix
Use the entity coverage checklist to identify semantic areas regardless of search volume. Low-volume supporting pages are often the ones that complete the entity graph and lift the whole cluster.
Mistake
Internal linking only from spokes to hub. A hub-only link structure passes equity upward but doesn't distribute it laterally, leaving sibling spoke pages without topical context from each other.
Fix
Every spoke page should link to the hub AND to 2–3 topically nearest sibling spokes. This lateral linking strengthens the sub-cluster signal.
Mistake
Publishing the entire cluster at once rather than in phases. Google needs time to crawl and index hub-and-spoke architecture. Publishing 18 posts in one day reduces the signal strength of the internal link structure.
Fix
Phase the build: hub + primary cluster first (4 weeks), then secondary clusters in order of entity priority. Allow 2–3 weeks between phases for indexing.
Mistake
Confusing a topical map with a content calendar. A topical map is an architecture document — it defines structure and relationships. A content calendar is a scheduling document. Merging them creates a plan that is too rigid for scheduling and too loose for architecture.
Fix
Keep the topical map as the structural reference document and derive the content calendar from it separately. The map should be updatable as you discover new entity gaps; the calendar should be revisable based on publishing capacity.
Step-by-step workflow
- 1
Define the cluster topic and goal
Choose a sub-niche broad enough to support 15–20 posts but specific enough to have a single defining keyword. Pair the topic with a business goal (affiliate revenue, trial signups, brand awareness) before doing any keyword research.
- 2
Map the entity space
List every semantic entity area related to the topic — not keywords, but concept categories. For espresso machines: machine types, grind, beans, maintenance, drinks, water, accessories. These entity areas become sub-cluster groups.
- 3
Design the hub page
Define the pillar page: its title, URL, target keyword, content type (buyer guide, comparison, explainer), and its role in the internal link architecture. The hub page should target the broadest keyword in the cluster.
- 4
Assign spoke pages to entity areas
For each entity area, create 2–4 spoke pages. Assign one primary keyword per spoke. Map the internal link from each spoke back to the hub and to 2–3 nearest sibling spokes.
- 5
Run the entity coverage checklist
Check each entity area against your spoke list. Mark covered areas and defer uncovered areas to a cluster v2 phase. Aim for at least five of eight entity areas covered before phase 1 publication.
- 6
Set the build order
Phase the publication: hub first, primary cluster (machine types + top-intent pages) second, secondary clusters third. Allow 2–3 weeks between phases for crawling and indexing.
- 7
Brief each spoke with cluster context
Every spoke page brief should reference the hub URL, list the 2–3 sibling spokes it must link to, and name the entity it owns. This ensures the published cluster has consistent internal link architecture across all posts.
Workflow notes
Topical maps are built before any individual post is briefed — they are the prerequisite to the brief, not the output of one. Once the map is complete, each spoke page gets its own content brief (see the content brief example) with the cluster context baked in: the brief references the hub page, names the sibling spokes for internal linking, and specifies which entity the spoke is responsible for covering. For existing sites with published content, the topical map process begins with a content audit — identifying which published posts can be repositioned as cluster spokes, which need to be consolidated, and which need to be created from scratch. A site with 40 published posts often has 8–10 posts that can be repositioned into a cluster with minimal editing, which reduces the total content creation required for authority by 40–50%.
Tool used in this example
Generate a comprehensive topical map for any niche — including hub page, core subtopic pages, long-tail supporting pages, topical gap analysis, internal linking architecture, and content priority order. The complete content strategy framework for building topical authority.
Open Topical Map GeneratorFrequently asked questions
Most niches require 12–20 posts covering the core entity space before Google begins treating the site as a topical authority. The minimum viable cluster is 1 hub page + 4–5 primary spoke pages. Below this threshold, the internal link architecture is too thin to signal depth. Quality matters more than quantity — five thorough spoke pages outperform fifteen shallow ones.
A topical map is a structural architecture document that defines relationships between pages. A content calendar is a scheduling document. The topical map is the input to the content calendar — you build the map first, then schedule publication from it. Mixing them creates a plan that tries to do two different jobs and does neither well.
Ideally yes, but pragmatically no. High-value, conversion-intent posts should always belong to a cluster. Topical news, trend commentary, and brand content can exist outside the cluster architecture without hurting authority — as long as they are not competing with cluster pages for similar keywords.
Search for your cluster's primary keyword and analyze the top 5 ranking pages. Identify the semantic entities they all cover. Then check your map against that list. Any entity covered by 3 or more of the top 5 results is a required entity for your cluster. Any entity covered by only 1–2 results is an opportunity to differentiate.
Yes, but the build timeline is longer. A new site in a new niche typically takes 6–9 months to see significant authority signals, versus 3–5 months for an established site adding a new cluster to existing domain authority. The process is the same — hub, entity coverage, build order — but the ranking timeline requires more patience.
Related examples
Content Marketing
Before/after content brief example for a SaaS feature launch. See how to turn a vague topic + keyword into a brief writers actually use to produce on-target drafts.
Content Marketing
See a real before/after blog intro rewrite for a how-to guide. Learn why story-led, problem-aware openings outperform generic filler every time.
Content Marketing
Three real landing page CTA rewrites for SaaS. See why "Sign up," "Get started," and "Learn more" underperform — and the specific replacements that increase clicks.