Hub-and-Spoke Content Architecture for Law Firms

Hub-and-spoke is a content structure where a broad, authoritative core page (the hub) links to a cluster of narrower, specialized pages (the spokes), each addressing a specific scenario, location, or practice variant. The hub page answers the big question ('What is medical malpractice?'); the spokes answer narrower versions ('What are surgical errors?', 'When is hospital negligence actionable?', 'Medical malpractice in California vs. Texas'). Spokes link back to their parent hub and sideways to sibling spokes, creating a dense, cross-linked cluster that Google and AI search engines recognize as authoritative coverage of a topic.

This is not a new idea. Information architecture using hub-and-spoke dates back at least to the 2000s (Kaplan, 2012, studied its impact on organic search). But it is having a renaissance now because two forces have converged: (1) Google's emphasis on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) rewards sites with deep, interconnected coverage of a topic, and (2) AI search engines like ChatGPT, Gemini, and Claude use passage-level retrieval and favor semantically clustered content — pages where related concepts live near each other are easier for AI models to understand and cite.

For law firms specifically, hub-and-spoke is table-stakes. A flat site where every page is independent ('medical malpractice home', 'surgical errors home', 'birth injury home', all unlinked) sends a signal to search algorithms that you have shallow coverage. A clustered site where every spoke points to the medical-malpractice hub and the hub links to every spoke says: 'We own this topic.' The ranking difference is material — hub-and-spoke sites typically see 20–40% more organic traffic than flat sites covering the same topics, because the hub captures the head term and the spokes capture the long tail (Rand Fishkin, 2013, Moz research).

Additionally, hub-and-spoke is how AI models encounter your content. When a user asks Gemini 'What constitutes medical malpractice?', Gemini retrieves passages from multiple pages simultaneously. If your pages are siloed and unrelated, Gemini might pick one passage from your site and three from competitors. But if your spoke on surgical-error liability links to your hub and your hub links to all your spokes, Gemini can see the cluster, extract richer passages from multiple related pages, and cite your site multiple times in one answer — that is a citation multiplier.

Search engines and AI models crawl your site and estimate importance by following links. A link from an external site (an inbound backlink) is a vote of confidence. But internal links also matter: they direct crawl budget and distribute authority from high-authority pages to lower-authority pages within your site. Hub-and-spoke is designed to exploit this.

Here's the flow: Suppose your firm's homepage is a hub for 'personal injury law,' and you have three spokes: 'car accidents,' 'pedestrian accidents,' and 'motorcycle accidents.' When Google crawls your site, it discovers your homepage (likely one of your most authoritative pages, with the most inbound links). From the homepage, it follows the internal link to the personal-injury hub page. From the hub, it follows links to all three spokes. The crawl budget and authority flow cascades: homepage → hub → spokes. The hub captures traffic for the broad query ('personal injury lawyer'), concentrating authority. Spokes capture traffic for narrow, high-intent queries ('car accident lawyer', 'motorcycle accident attorney'), but they inherit authority from the hub via the internal link.

This matters for ranking. A spoke on 'motorcycle accident injury claims' might otherwise be a weak page with few inbound links. But because the hub links to it, and the hub has domain authority from external backlinks, the spoke inherits some of that authority. This 'link juice' flow is how a well-structured site helps pages rank that might otherwise be buried.

AI search engines work differently (they don't follow links in the traditional sense, but they do consider authority and links as signals), but the principle is similar. An AI model retrieving passages for a user's question will preferentially retrieve from pages that appear authoritative. Pages within a densely linked cluster appear more central and trustworthy than orphaned pages.

Before you create your first hub, you need a taxonomy — a structured list of what your hubs are and which pages belong to each. A taxonomy answers three questions: (1) What are my core practice areas? (2) What are the specific scenarios, locations, or variants within each practice area? (3) Are there any pages that don't fit a practice area (general resources, tools, blog posts)?

For a personal injury firm, your taxonomy might be: Hub 'Personal Injury' with spokes 'Car Accidents', 'Pedestrian Accidents', 'Motorcycle Accidents', 'Wrongful Death', and 'Workers Compensation'. Then, for each spoke, you might add nested spokes by location: 'Car Accidents in California', 'Car Accidents in Texas', etc. A divorce firm might have Hub 'Family Law' with spokes 'Divorce', 'Child Custody', 'Spousal Support', 'Property Division', each with location variants.

The key rule: each page belongs to exactly one hub. Never let a page belong to two hubs (e.g., a page about 'employment law in California' should not be in both an 'employment' hub and a 'California' hub; instead, it is in one or the other, and links to the other). This prevents duplication, confusion, and diffused authority.

A well-built taxonomy is the source of truth. It generates: your site's navigation menu, the hub-and-spoke internal linking structure, your XML sitemap, the breadcrumb schema on every page, and even the URL paths (e.g., /personal-injury/car-accidents, /personal-injury/motorcycle-accidents). Change the taxonomy once, and all downstream artifacts regenerate — this is why taxonomy, not hand-coded links, is the foundation.

The hub page is the workhouse of your cluster. It should be comprehensive, ranking-optimized, and link-rich. A well-built hub page typically: (1) opens with a direct, answer-first definition of the practice area ('Medical malpractice is the failure of a healthcare provider to meet the standard of care, resulting in injury or death'); (2) includes a table of contents showing all the subtopics (spokes) it covers; (3) has a long article (2,500–4,000+ words) covering the nuances, legal framework, common scenarios, damages, and defenses; (4) includes a 'Key Takeaways' card (TL;DR) with the most important points; (5) features an FAQ section answering the most common questions; (6) links down to every spoke in the hub at multiple points (in the TOC, in relevant paragraphs, and in a related-articles block at the bottom).

The hub page is where you earn the head term rank. For 'personal injury lawyer', your personal injury hub page is the primary target. The hub should have the most inbound links, the most content, and the most authority. This concentration of authority is intentional: you want the hub to rank well for the broad term, establish topical authority, and then distribute authority to spokes via internal links.

One critical rule: the hub page should be comprehensive and standalone. A reader who lands on the hub via the broad search term ('personal injury law') should not feel like they are missing something. They should get a complete overview. Spokes are for readers who want to go deeper on a specific scenario or location. If the hub is thin or generic, readers will bounce, and search engines will see it as weak. A strong hub is 2,500+ words, well-researched, and genuinely useful.

A spoke is a focused page that addresses a specific scenario, location, or variant within the hub's topic. Spokes should be: (1) specific — 'surgical errors in medical malpractice' is narrower and more useful than 'medical malpractice'; (2) self-contained — a reader landing on the spoke via a search result should understand the spoke's topic without visiting the hub; (3) linked to the hub — every spoke should link back to its parent hub in at least two places (top nav, closing paragraph, related-articles block); (4) linked to siblings — a spoke on 'surgical errors' should link to sibling spokes like 'anesthesia errors' and 'diagnostic errors'.

Spokes typically range from 1,500–2,500 words (deep, but not as comprehensive as the hub). A strong spoke structure is: direct answer + key takeaways (TL;DR) + 5–7 core sections each addressing a sub-question + 6–8 FAQs + references + a 'Related' block linking to the hub and siblings.

One common mistake: treating spokes like thin landing pages. If a spoke is only 300 words and just says 'We handle surgical errors in medical malpractice, contact us', it is not a spoke — it is a thin lead-generation page. AI models won't cite it, and Google won't rank it. A real spoke is genuinely useful: 'Here's what constitutes a surgical error, here's what the law says, here's what evidence matters, here are common defenses.' Thick spokes (1,500+ words) with real content rank better, are cited by AI, and generate more inbound links.

Mistake 1: Building a hub without a taxonomy. You end up with pages that should be in the same hub living in different clusters, or duplicate pages that both cover the same topic but link to different parents. Always start with a written taxonomy.

Mistake 2: Creating orphaned pages. A page on 'birth injury liability in Texas' that does not link to any hub or spoke, and is not linked to by any hub or spoke, is an orphan. It will never gain authority from internal links. Every page must belong to exactly one hub.

Mistake 3: Over-linking. Every paragraph does not need 3–5 internal links. A moderate linking density (1–2 links per 300 words) is sufficient. Over-linking looks spammy and dilutes link power.

Mistake 4: Duplicate content across spokes. If three location pages all copy-paste the same legal explanation with only the city name changed, they are duplicates. Google will penalize this. Instead, write unique content for each page, and link them to a shared resource (the hub) that has the deep legal explanation. The hub can be referenced; the spokes should add location-specific details.

Mistake 5: Ignoring AI citability. A page can rank well on Google but be poorly structured for AI extraction. Use passage-level structure (H2/H3 headings, short answer-first sections, comparison tables, lists) so AI models can extract and cite individual passages.

Mistake 6: Forgetting to link the hub from your top navigation and homepage. If the hub is not discoverable from your site's main navigation, users won't find it, and its authority will be isolated. Every hub should appear in your top nav or footer, so users always have a path to it.

Hub-and-spoke is one of the strongest signals you can send to AI search engines (a practice we call GEO — Generative Engine Optimization). Here's why: (1) Semantic clustering — when related pages are densely linked and cover a topic comprehensively, AI models can extract passages from multiple related pages and stitch them together into a more complete answer. A fragmented site where pages are unrelated means each page competes for citations independently, and AI often picks just one. (2) Passage-level retrieval — AI models split pages into passages (typically 100–200 word chunks) and retrieve the most relevant passages to user queries. A well-structured spoke with clear H2/H3 headings and answer-first sections yields more extractable passages than a wall-of-text page. (3) Entity clarity — when a hub and its spokes all address the same core topic (e.g., 'medical malpractice') but from different angles, the model's embeddings for that topic cluster together. The model learns 'this site owns medical malpractice.' This clustering increases the odds that when a user asks about any variant of the topic, the model retrieves from your cluster rather than from competitors.

Real-world example: a law firm with a strong medical-malpractice hub and ten specialized spokes (surgical errors, anesthesia errors, diagnostic errors, etc.) is more likely to be cited by AI search engines than an otherwise identical firm with a flat site structure. The clustered structure enables the AI model to extract passages from multiple related pages and recognize the firm as a comprehensive authority on the topic, multiplying citation opportunities across the cluster.