Site Architecture

Silo structure, hub and spoke, and topic clusters compared — what's actually different, what Google recommends, and why internal links beat URL folders.

First published: Jun 26, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #8 in Website Structure#94 in Technical SEO#125 on the site

Site architecture is the set of crawlable discovery and navigation paths between your pages, plus supporting entry points like sitemaps — it's not the same thing as your URL folders. Silo, hub and spoke, and topic clusters are overlapping practitioner labels for that structure, not documented Google categories — hub and spoke and topic clusters share the same underlying pattern more than they genuinely differ. Google's documented minimum is a crawlable link to every page you care about; that supports discovery, it doesn't guarantee crawling, indexing, ranking, traffic, sitelinks, or AI citations. No Google source requires banning links between topic areas — evaluate strict-silo rules against user navigation and relevance, not assumed authority mechanics. What matters is contextual internal linking, not URL folders.

TL;DR — Silo, hub and spoke, and topic clusters are overlapping practitioner labels, not documented Google architecture categories — but they converge on one structure Mueller has described favorably: a pyramid / top-down hierarchy. Hub and spoke and topic clusters share the same underlying pattern more than they genuinely differ — one comes from information architecture, the other from HubSpot’s 2017 content-marketing rebrand. The part of silo thinking worth keeping is topical concentration of internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them.; the part to drop is the strict “no cross-silo links” rule — no Google source requires it, so judge cross-links by relevance and user navigation instead. What Google leans on is internal linkingLinks between pages on the same site. and context, not URL folder structure. Keep hierarchies reasonably shallow, link related pages across clusters when it’s relevant, and remember architecture enables outcomes like topical authoritySemantic search is meaning-based retrieval — matching what a user means, not just the words they typed. Search engines detect entities, expand synonyms, infer intent, and rank by conceptual relevance, which is why keyword stuffing lost its power and topical depth gained it. and AI-search visibility — it doesn’t guarantee them, and it can’t rescue thin contentThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count..

Evidence for this claim Google uses links to discover pages and as a relevance signal, so crawlable internal navigation supports discovery and understanding. Scope: Current Google internal-link guidance. Confidence: high · Verified: Google Search Central: Link best practices Evidence for this claim Google recommends navigation paths from menus to categories and subcategories to products, with direct links to important pages. Scope: Current Google ecommerce site-structure guidance, broadly applicable to hierarchical sites. Confidence: high · Verified: Google Search Central: Ecommerce site structure

Why SEOs argue about this at all

Site architectureSite architecture is how a website's pages are organized, categorized, and interlinked. It controls how crawlers discover pages, how link equity flows, and how clearly search engines understand each page's topical context. Silo structure, hub and spoke, and topic clusters are the three common models. is one of those topics where three communities invented overlapping vocabularies and then spent fifteen years insisting their word was the real one. I’ve spent six-plus years at Ahrefs on the product side around Site Audit, looking at what site structuresWebsite structure (site architecture) is a site's visible hierarchy, navigation, breadcrumbs, and URL organization — how pages relate and how people and search engines move between them. Internal linking is the primary signal Google reads to understand that structure, not URL folders. actually look like in crawl data across a huge number of sites — and the gap between the dogma and what works is wide. So let me try to collapse the confusion.

There are three named models:

  • Silo structureA silo structure is a site organized by grouping related content into topic areas and concentrating internal links within each topic so a hub page and its supporting pages reinforce each other. Modern practice keeps the topical concentration and drops the old rule against cross-linking between topics. — content grouped into isolated thematic sections. The strict interpretation (popularized by Bruce Clay) prohibits cross-silo internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. to keep each silo’s “link equityPageRank is Google's original recursive link-graph algorithm: a page's score depends on the scores of the pages linking to it, and in the published model each page's score is split across its outbound links (the simplified version: links are weighted votes). Google says it's evolved since launch but still part of its core ranking systems.” concentrated.
  • Hub and spoke — a broad overview hub page links out to detailed spoke pages, which link back. The hub is sometimes called a pillar page.
  • Topic clusters — HubSpot’s 2017 framing: a pillar page targets a broad keyword, cluster pages target long-tail subtopics, everything interlinked.

The clarification I’ll plant my flag on

None of “silo,” “hub and spoke,” or “topic cluster” is a Google-documented architecture category. They’re practitioner labels, and in practice their implementations overlap heavily. “Hub and spoke” is the older information-architecture term: a central overview page linking to detailed subtopic pages with reciprocal links. “Topic clusters” is HubSpot’s 2017 content-marketing rebrand of essentially that same pattern — a pillar page plus interlinked cluster content. “Pillar page” is just the marketing word for the hub. Calling them flatly identical overstates it — HubSpot’s framing leans more on planned topical coverage as a content strategy, while “hub and spoke” is older, more general information-architecture vocabulary — but if you’re choosing how to structure links, you’re solving the same problem either way: a central page, detailed subtopic pages, and reciprocal links between them.

And once you allow cross-silo links — which nothing Google has published tells you not to — a “silo” is a hub-and-spoke cluster in practice. So the three names mostly converge on one workable structure: grouped, hierarchical, internally linked, with sensible cross-links. Treat them as overlapping vocabulary for that structure, not as three competing systems to choose between.

What Google actually recommends

Google’s recommendation is a pyramid / top-down hierarchy: the home page covers the broadest topic, category/hub pages sit in the middle, and specific content pages live at the bottom. John Mueller put the why plainly: the top-down approach or pyramid structure “helps us a lot more to understand the context of individual pages within the site.” That’s the payoff — structure isn’t a ranking trick, it’s how Google figures out what each page is about and how pages relate.

Worth noting: Google uses the term “hub page” in its own documentation — describing how “a hub page, such as a category page, links to a new blog post” for discovery. So the hub-and-spoke framing isn’t an SEO invention; it’s Google’s own language.

This is the single most misunderstood part of architecture. A lot of silo advice is really about URL folders — putting /category-a/ pages under one path and forbidding links to /category-b/. But Google focuses on internal linking signals, not URL path segments. Mueller has repeatedly noted that some SEOs over-focus on URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.; Google works out hierarchy from how pages link to each other, not from folder names.

The implication is big: a page at /blog/technical-seo/site-architecture/ signals nothing to Google beyond what its content and inbound links say about it. Logical URLs are good for humans and for managing the site — but they aren’t the architecture. The link graph is the architecture. This is also why “virtual silos” (concentrating links by topic regardless of folder) work fine, and why strict “physical silos” (folder-based isolation with no cross-links) buy you crawl and UX problems for no offsetting benefit.

Google’s documentation is specific about what counts as a link it can reliably follow: a standard <a href> element with a resolvable URL. Navigation built only from JavaScript click handlers or non-standard markup doesn’t get you the same reliable discovery path, no matter how clean your URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. looks. Get the crawlable-link contract right first — folder naming is secondary.

Where strict silos go wrong

The legitimate insight in silo thinking is topical concentration — grouping related content and linking generously within a topic area genuinely helps readers navigate and helps Google understand what a page is about. The failure mode is the strict rule: never link between silos. No reviewed Google source requires that prohibition — so judge it on its own terms, not as an assumed authority mechanic:

  • it prevents natural, contextually relevant links readers would benefit from,
  • it hurts UX by dead-ending users at artificial silo boundaries, and
  • a page can still be relevant to more than one topic area, and a link that helps a reader find it shouldn’t be blocked because it crosses a label you drew.

Shari Thurow has been making this point for years (“stop the silo madness”), and Ahrefs’ own contrarian take (Joshua Hardwick’s “why it makes no sense”) lands in the same place. Keep the concentration; drop the wall — and make the call based on whether a link genuinely serves the reader and the destination page, not on unverified claims about how strictly Google weighs isolation.

Flat vs. deep hierarchies

Two failure modes at the extremes:

  • Too flat — everything one click off the home page. Link equity and topical signal get diluted; the home page can’t meaningfully vouch for hundreds of equal children, and you lose the topical grouping that helps context.
  • Too deep — important pages many clicks from home. Mueller’s framing: going too deep “makes it harder for us to crawl and harder for us to pass the signals around.” Deep pages tend to get crawled less and inherit less internal authority. Google hasn’t published a specific click-depth number; don’t treat any fixed count as a requirement — the right depth depends on your site’s size and how distinct its categories are, which is its own topic (see the flat vs. deep and crawl-depth deep dives in this cluster for the fuller decision framework).

The target is a shallow hierarchy with strong contextual linking: keep important pages reachable in as few hops as your site’s scale reasonably allows, grouped into hubs, with cross-links where topics genuinely relate. This is the same crawl-depth concern that shows up whenever you’re auditing how far botsA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. have to travel to reach your money pages.

What internal linking actually does

Architecture’s real job is shaping the internal link graph. Three things to get right:

  1. Linkability. Every important page should have a link from at least one other page — ideally several. Google’s own guidance is explicit about this minimum. Pages with no inlinks are harder to find and harder to rank, but a link doesn’t guarantee either outcome.
  2. Context. The words before and after a link, and the anchor textAnchor text is the visible, clickable text of a hyperlink. It tells readers what they'll find on the other end and gives search engines context about the linked page. itself, can help people and Google understand what the target is about. This is how a hub “explains” its spokes — it’s not a promise of a specific ranking effect.
  3. Concentration. Linking densely within a topic cluster puts relevance signals where they belong — the kernel of truth silos were always reaching for. Whether that concentration translates into something practitioners call “topical authority” isn’t something Google documents directly; treat it as a reasonable hypothesis worth testing on your own site, not a guaranteed mechanism.

This site is a live example. patrickstox.com runs a pillar → cluster → article → sub-article hierarchy across a few hundred pages, using pillar, cluster, clusterSelf, subcluster, and subsubcluster taxonomy — and it deliberately cross-lists articles across clusters (the alsoIn pattern) rather than walling them off. That’s hub-and-spoke with intentional cross-linking: exactly the model I’m describing, not a strict silo.

When to use which model

Honestly? Build the hub-and-spoke / topic-cluster structure and stop worrying about the labels:

  • Pick a pillar/hub topic with real breadth and search demand.
  • Identify the subtopics that have their own demand — those become spokes.
  • Interlink hub ↔ spokes and spoke ↔ spoke where relevant.
  • Cross-link to other clusters when the context is genuinely related.

There’s no magic number of cluster pages per hub. The right count is however many distinct subtopics with real demand exist — not an arbitrary target of 5, 10, or 30. Wikipedia is the canonical example: broad overview pages linking deeply to detailed subtopic pages, all densely interlinked, no silo walls anywhere.

AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. and AI assistants use query fan-outQuery fan-out is the technique where an AI search system breaks a single user question into multiple related sub-queries, runs those searches concurrently, and synthesizes the retrieved results into one answer. Google confirms AI Overviews and AI Mode 'may use a query fan-out technique' issuing multiple related searches across subtopics. — they decompose a question into multiple related sub-queries. The reasonable hypothesis, not a documented guarantee: a site with organized, interlinked coverage across a topic’s subtopics has a better chance of surfacing across more of those sub-queries, since more of the subtopics are covered by a findable, crawlable page. I haven’t seen controlled evidence isolating architecture as the cause here, so treat it as something to test on your own content rather than an established mechanism. Gary Illyes’ public position is that AI search optimizationAI search optimization is the practice of making your brand and content visible, citable, and accurately represented across AI-powered search — Google AI Overviews, ChatGPT, Perplexity, Copilot. It's built on traditional SEO plus a heavier emphasis on off-site brand mentions and content AI systems can cite. needs normal SEO — well-structured, crawlable, high-quality content — not a special architecture. The structure that already serves traditional search is the same one you’d build for AI searchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity.; there’s no separate playbook.

Auditing your architecture

A practical pass, mostly with crawl data:

  • Find orphans — pages with no internal links in. Crawl the site (Ahrefs Site Audit, Screaming Frog) and look for zero-inlink pages.
  • Find over-deep pages — important URLs buried many clicks from home; no fixed number is the rule, but if crawl data shows them getting crawled less, dig in.
  • Map topics and find hub candidates — clusters of related pages missing a central overview.
  • Run an internal-link gap analysis — related pages that should link to each other but don’t.
TIP Turn an internal-link gap analysis into a reviewable queue

Candidate scores surface related pages and explain why they were paired. They do not establish the right architecture or replace a crawl-based orphan and depth audit.

Prioritize supplied-page connections with my free Internal Link Cluster Visualizer Free

  1. Supply a representative hub, its spokes, and their current internal links.
  2. Review high-scoring pairs whose targets have few supplied inlinks.
  3. Approve only contextually useful links, then recrawl to verify the resulting graph and click depth.

The honest caveat

Architecture is infrastructure, not a ranking shortcut. It enables crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., controls how link equity flows, and helps engines understand context — but a beautiful hub-and-spoke structure wrapped around thin, low-value content still won’t rank. Illyes has noted it’s rare to see two results from one domain in a SERP; structure serves content quality and relevance, it doesn’t substitute for them. Get the structure right so that good content can do its job — that’s the whole point.

The neighboring topics in this cluster — how internal links pass signals, how crawl depth affects discovery, and faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. on large sites — all plug into the same architecture decisions covered here.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.