Architecture du site

Silo structure, hub and spoke, and topic clusters comparé — what's en réalité différent, ce que Google recommends, and pourquoi lien internes beat URL folders.

Première publication : 26 juin 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues

Architecture du site is the définir of crawlable discovery and navigation paths entre votre pages, plus supporting entry points comme sitemaps — it's pas the même chose as votre URL folders. Silo, hub and spoke, and topic clusters are overlapping practitioner étiquettes pour que structure, pas documented Google categories — hub and spoke and topic clusters share the même underlying pattern plus que ils genuinely differ. Google's documented minimum is a crawlable lien to every page vous care à propos de; que supports discovery, it doesn't guarantee exploration, indexation, ranking, trafic, sitelinks, or AI citations. Aucun Google source exige banning liens entre topic areas — evaluate strict-silo rules contre utilisateur navigation and relevance, pas assumed authority mechanics. Ce que matters is contextual maillage interne, pas URL folders.

TL;DR — Silo, hub and spoke, and topic clusters are overlapping practitioner étiquettes, pas documented Google architecture categories — but ils converge on un structure Mueller has décrit favorably: a pyramid / top-down hierarchy. Hub and spoke and topic clusters share the même underlying pattern plus que ils genuinely differ — un comes from information architecture, the autre from HubSpot’s 2017 content-marketing rebrand. The partie of silo thinking worth keeping is topical concentration of lien internes; the partie to drop is the strict “no cross-silo links” rule — aucun Google source exige it, so judge cross-links by relevance and utilisateur navigation à la place. Ce que Google leans on is maillage interne and context, pas URL folder structure. Garder hierarchies reasonably shallow, lien connexe pages à travers clusters quand it’s relevant, and remember architecture enables outcomes comme topical authority and AI-search visibility — it doesn’t guarantee les, and it can’t rescue contenu pauvre.

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

Pourquoi SEOs argue à propos de ce at tout

Architecture du site is un of ceux topics où three communities invented overlapping vocabularies and alors spent fifteen années insisting leur word was the réel un. I’ve spent six-plus années at Ahrefs on the product side autour Site Audit, looking at ce que site structures en réalité regarder comme in explorer données à travers a huge number of sites — and the gap entre the dogma and ce que fonctionne is wide. So let me essayer to collapse the confusion.

Là are three named models:

  • Silo structure — content grouped into isolated thematic sections. The strict interpretation (popularized by Bruce Clay) prohibits cross-silo lien internes to garder chaque silo’s “link equity” concentrated.
  • Hub and spoke — a broad overview hub page liens out to detailed spoke pages, qui lien back. The hub is parfois appelé 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 étiquettes, and En pratique leur implementations overlap heavily. “Hub and spoke” is the older information-architecture term: a central overview page linking to detailed subtopic pages with reciprocal liens. “Topic clusters” is HubSpot’s 2017 content-marketing rebrand of essentially que même pattern — a pillar page plus interlinked cluster content. “Pillar page” is simplement the marketing word pour the hub. Appel les flatly identical overstates it — HubSpot’s framing leans plus on planned topical coverage as a content strategy, pendant que “hub and spoke” is older, plus general information-architecture vocabulary — but si you’re choosing how to structure liens, you’re solving the même problem soit façon: a central page, detailed subtopic pages, and reciprocal liens entre les.

And une fois vous autoriser cross-silo liens — qui nothing Google has publié indique vous pas to — a “silo” is a hub-and-spoke cluster En pratique. So the three noms mostly converge on un workable structure: grouped, hierarchical, internally lié, with sensible cross-links. Treat les as overlapping vocabulary pour que structure, pas as three competing systems to choisir entre.

Ce que Google en réalité 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 spécifique content pages live at the bottom. John Mueller put the pourquoi plainly: the top-down approach or pyramid structure “helps us a lot plus to comprendre the context of individual pages dans le site.” That’s the payoff — structure isn’t a ranking trick, it’s how Google figures out ce que chaque page is à propos de and how pages relate.

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

Lien internes beat Structure d’URL

Ce is the unique la plupart misunderstood partie of architecture. A lot of silo advice is really à propos de URL folders — putting /category-a/ pages sous un chemin and forbidding liens to /category-b/. But Google focuses on maillage interne signals, pas URL chemin segments. Mueller has repeatedly noted que some SEOs over-focus on Structure d’URL; Google fonctionne out hierarchy from how pages lien to chaque autre, pas from folder noms.

The implication is big: une page at /blog/technical-seo/site-architecture/ signals nothing to Google au-delà ce que its content and inbound liens dire à propos de it. Logical URLs are bon pour humans and pour managing le site — but ils aren’t the architecture. The lien graph is the architecture. Ce is aussi pourquoi “virtual silos” (concentrating liens by topic regardless of folder) fonctionner fine, and pourquoi strict “physical silos” (folder-based isolation with aucun cross-links) buy vous explorer and UX problems pour aucun offsetting benefit.

Google’s documentation is spécifique à propos de ce que counts as a lien it peut reliably follow: a standard <a href> element with a resolvable URL. Navigation construit seulement from JavaScript click handlers or non-standard markup doesn’t obtenir vous the même reliable discovery chemin, aucun matter how clean votre Structure d’URL semble. Obtenir the crawlable-link contract correct premier — folder naming is secondary.

Où strict silos go incorrect

The legitimate insight in silo thinking is topical concentration — grouping connexe content and linking generously dans a topic area genuinely helps readers navigate and helps Google comprendre ce que une page is à propos de. The échec mode is the strict rule: jamais lien entre silos. Aucun reviewed Google source exige que prohibition — so judge it on its propre terms, pas as an assumed authority mechanic:

  • it empêche natural, contextually relevant liens readers voudrait benefit from,
  • it hurts UX by dead-ending utilisateurs at artificial silo boundaries, and
  • une page peut encore be relevant to plus que un topic area, and a lien que helps a reader trouver it shouldn’t be blocked parce que it crosses a étiquette vous drew.

Shari Thurow has been making ce point pour années (“stop the silo madness”), and Ahrefs’ propre contrarian prendre (Joshua Hardwick’s “why it makes no sense”) lands in the même placer. Garder the concentration; drop the wall — and faire the appel fondé on si a lien genuinely sert the reader and the destination page, pas on unverified claims à propos de how strictly Google weighs isolation.

Flat vs. deep hierarchies

Two échec modes at the extremes:

  • Aussi flat — everything un click off the home page. Popularité des liens and topical signal obtenir diluted; the home page can’t meaningfully vouch pour hundreds of equal children, and vous lose the topical grouping que helps context.
  • Aussi deep — pages importantes nombreux clicks from home. Mueller’s framing: going aussi deep “rend it harder pour us to explorer and harder pour us to réussir the signals autour.” Deep pages tend to obtenir crawled moins and inherit moins internal authority. Google hasn’t publié a spécifique click-depth number; don’t treat quelconque fixed count as a requirement — the correct depth dépend on votre site’s size and how distinct its categories are, qui is its propre topic (voir the flat vs. deep and crawl-depth deep dives in ce cluster pour the fuller decision framework).

The target is a shallow hierarchy with strong contextual linking: garder pages importantes reachable in as few hops as votre site’s scale reasonably permet, grouped into hubs, with cross-links où topics genuinely relate. Ce is the même crawl-depth concern que montre up whenever you’re auditing how far bots have to travel to reach votre money pages.

Ce que maillage interne en réalité fait

Architecture’s réel job is shaping the lien interne graph. Three choses to obtenir correct:

  1. Linkability. Every important page devrait have a lien from au moins un autre page — ideally several. Google’s propre guidance is explicit à propos de ce minimum. Pages with aucun inlinks are harder to trouver and harder to rank, but a lien doesn’t guarantee soit outcome.
  2. Context. The words avant and après a lien, and the anchor text itself, peut aider personnes and Google comprendre ce que the target is à propos de. Ce is how a hub “explains” its spokes — it’s pas a promise of a spécifique ranking effect.
  3. Concentration. Linking densely dans a topic cluster puts relevance signals où ils belong — the kernel of truth silos were toujours reaching pour. Si que concentration translates into something practitioners appel “topical authority” isn’t something Google documents directement; treat it as a reasonable hypothesis worth testing on votre propre site, pas a guaranteed mechanism.

Ce site is a live exemple. patrickstox.com runs a pillar → cluster → article → sub-article hierarchy à travers a few hundred pages, en utilisant pillar, cluster, clusterSelf, subcluster, and subsubcluster taxonomy — and it deliberately cross-lists articles à travers clusters (the alsoIn pattern) plutôt que walling les off. That’s hub-and-spoke with intentional cross-linking: exactly the model I’m describing, pas a strict silo.

Quand to utiliser qui model

Honestly? Construire the hub-and-spoke / topic-cluster structure and arrêter worrying à propos de the étiquettes:

  • Pick a pillar/hub topic with réel breadth and search demand.
  • Identifier the subtopics que have leur propre demand — ceux become spokes.
  • Interlink hub ↔ spokes and spoke ↔ spoke où relevant.
  • Cross-link to autre clusters quand the context is genuinely connexe.

There’s aucun magic number of cluster pages per hub. The correct count is cependant nombreux distinct subtopics with réel demand exist — pas an arbitrary target of 5, 10, or 30. Wikipedia is the canonical exemple: broad overview pages linking deeply to detailed subtopic pages, tout densely interlinked, aucun silo walls anywhere.

AI Overviews and AI assistants utiliser requête fan-out — ils decompose a question into multiple connexe sub-queries. The reasonable hypothesis, pas a documented guarantee: a site with organized, interlinked coverage à travers a topic’s subtopics has a meilleur chance of surfacing à travers plus of ceux sub-queries, since plus of the subtopics are covered by a findable, crawlable page. I haven’t seen controlled evidence isolating architecture as the causer ici, so treat it as something to tester on votre propre content plutôt que an established mechanism. Gary Illyes’ public position is que AI search optimization nécessite normal SEO — well-structured, crawlable, high-quality content — pas a special architecture. The structure que déjà sert traditional search is the même un you’d construire pour AI search; there’s aucun separate playbook.

Auditing votre architecture

A practical réussir, mostly with explorer données:

  • Trouver orphans — pages with aucun lien internes in. Explorer le site (Ahrefs Site Audit, Screaming Frog) and regarder pour zero-inlink pages.
  • Trouver over-deep pages — important URLs buried nombreux clicks from home; aucun fixed number is the rule, but si explorer données montre les getting crawled moins, dig in.
  • Map topics and trouver hub candidates — clusters of connexe pages manquant a central overview.
  • Run an internal-link gap analysis — connexe pages que devrait lien to chaque autre but don’t.

The honest caveat

Architecture is infrastructure, pas a ranking shortcut. It enables exploration, contrôle how popularité des liens flows, and helps engines comprendre context — but a beautiful hub-and-spoke structure wrapped autour thin, low-value content encore won’t rank. Illyes has noted it’s rare to voir two results from un domain in a SERP; structure sert content quality and relevance, it doesn’t substitute pour les. Obtenir the structure correct so que bon content peut do its job — that’s the whole point.

The neighboring topics in ce cluster — how lien internes réussir signals, how explorer depth affecte discovery, and faceted navigation on grand sites — tout plug into the même architecture decisions covered ici.

Add an expert note

Pin an expert quote

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