Content Architecture and Internal Linking
Content architecture determines how your pages connect to each other and how search engines understand the topical relationships between them. A site without content architecture is a collection of disconnected pages. A site with content architecture is a structured knowledge base that demonstrates expertise through the relationships between its pages.
Hub-and-spoke architecture mirrors how search engines evaluate topical authority. A hub page about "plumbing services" links to spoke pages about "boiler installation", "pipe repair", and "emergency plumber". Each spoke links back to the hub. Google sees a site that covers plumbing in depth — not a single page that mentions it once.
Hub-and-Spoke Structure
Every hub-and-spoke cluster follows the same structural rules. The hub page sits at the top of the cluster and targets the broadest keyword. It provides a comprehensive overview of the topic and links contextually to every spoke page in the cluster. Each spoke page targets a more specific keyword, covers that subtopic in depth, and links back to its hub page.
The critical element that most sites miss is sibling linking — spoke pages linking to other spoke pages within the same cluster. If your hub is "kitchen renovation" and your spokes are "kitchen worktops", "kitchen flooring", and "kitchen lighting", then the worktops page should link to flooring and lighting because a person reading about worktops is likely also interested in those related topics. These sibling links keep users within the cluster and reinforce the topical connection for search engines.
Cross-hub linking is used sparingly where two clusters share genuine semantic overlap. If you have a "bathroom renovation" hub and a "plumbing services" hub, there are natural connection points — a spoke about "bathroom plumbing" in the renovation cluster can link to the plumbing hub, and a spoke about "bathroom installation" in the plumbing cluster can link to the renovation hub. These cross-links must be editorially justified, not forced.
Internal Linking Rules
Internal links are not navigation — they are editorial signals that tell search engines which pages are related and how they relate. We follow strict rules for internal linking:
- Every spoke links to its hub with anchor text derived from the hub page's primary keyword. This is a mandatory upward link that reinforces the cluster structure.
- Every hub links to all its spokes with anchor text derived from each spoke's primary keyword. These links appear within the body content, not in a sidebar widget or footer list.
- Spokes link to at least two siblings within the same cluster. The linked siblings are chosen based on semantic proximity — the most closely related subtopics, not random selections.
- Anchor text matches the target page keyword or a close semantic variant. We never use "click here" or "read more" as anchor text because those phrases carry no topical signal for search engines.
- No orphan pages — every page on the site is reachable through at least one contextual in-content link in addition to any navigation menu links. Pages that only appear in navigation are effectively invisible to crawlers following content-level link signals.
How Content Architecture Ranks
- Step 1: Identify topic clusters from keyword data. Using the keyword research output, we group semantically related terms into clusters. Each cluster represents a topic your site will cover in full — the goal is to own the entire topic, not just individual keywords.
- Step 2: Designate hub and spoke pages. The broadest keyword in each cluster becomes the hub page target. The remaining keywords become spoke page targets. Hub pages provide comprehensive coverage of the topic; spoke pages go deep on specific subtopics.
- Step 3: Define the internal linking blueprint. We map every internal link the site needs: hub-to-spoke links, spoke-to-hub links, sibling links between spokes in the same cluster, and cross-hub links where two clusters share semantic overlap. Every link has a defined anchor text derived from the target page keyword.
- Step 4: Implement and validate. The architecture is built into the site with contextual in-content links (not just navigation menus). We validate the link structure by crawling the site and confirming that every page is reachable within 3 clicks of the homepage and that no orphan pages exist.
Authority is built through connections, not volume. Sites with proper content architecture consistently outrank larger competitors who have more pages but no structural organisation. Search engines crawl every page efficiently, understand the topical relationships between pages, and evaluate your site's depth of coverage on each topic.
Frequently Asked Questions
Hub-and-spoke architecture organises your site into topic clusters. Each cluster has one hub page targeting a broad keyword and several spoke pages targeting related long-tail keywords. The hub links down to every spoke, every spoke links back up to the hub, and spokes link sideways to their siblings. This creates a closed topical loop that signals depth and authority to search engines.
A 15-page site typically has 2-3 hubs with 4-5 spokes each. A 50-page site may have 5-8 hubs with varying spoke counts depending on keyword data. The number is determined by keyword research — we create as many clusters as the data supports, no more. Padding a site with thin spoke pages to inflate the page count damages authority rather than building it.
Yes, but it requires restructuring the URL hierarchy, rewriting internal links, and potentially consolidating or splitting existing pages to match the cluster model. We audit the existing content, map it against keyword data, identify gaps and overlaps, and produce a migration plan that preserves existing ranking equity while establishing the hub-and-spoke structure.
Related Services
SEO Website Build
A complete SEO-optimised website built from keyword research through to deployment. 15-50 pages with topical authority architecture.
Keyword Research
50-200 keywords clustered by intent and mapped into a hub-and-spoke architecture that builds topical authority from day one.
Schema Markup
Per-page JSON-LD with entity-interconnected @graph. Every schema node cross-references via @id for maximum search engine comprehension.