How to Build a Silo Structure: A Practical Guide

A step-by-step build guide for a topic silo — define boundaries with keyword research, wire the hub-and-spoke internal link matrix, cross-link sensibly, and audit that link concentration actually landed where you meant it to.

First published: Jul 3, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #7 in Website Structure#85 in Technical SEO#113 on the site

Building a silo structure isn't a URL-folder trick — it's a build process. Define silo boundaries with real keyword data (distinct search demand per subtopic, not an arbitrary page quota). Mirror the silo in folders for CMS sanity if you want, but the internal link graph is the actual architecture. Wire the matrix: hub links to every spoke, spokes link back to the hub and to relevant siblings. Cross-link to other topics when a reader would genuinely follow the link — and never nofollow a cross-silo link (PageRank sculpting has been dead since 2009; the equity just evaporates). Then audit with a crawl (Screaming Frog visualisations, Ahrefs Site Audit orphan/link reports, or a spreadsheet link-matrix) to confirm the links you planned actually exist.

TL;DR — This is the how, not the whether. Assume topical concentration plus sensible cross-linking is the goal (the model debate is settled in this cluster’s 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. article). Build order: (1) draw silo boundaries from real keyword dataSearch volume, difficulty, and related queries for what people type into search engines. — distinct search demand per subtopic, not a page quota; (2) mirror the silo in folders for CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. sanity if you like, but remember the link graph is the architecture, not the path; (3) wire the internal linkAn 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. matrix — hub to every spoke, spoke back to hub, spoke to relevant siblings; (4) cross-link to other topics when a reader would actually follow the link, and never nofollowrel=\"nofollow\" is a value of the HTML link rel attribute that tells search engines you don't vouch for a linked page and don't want to pass ranking signals to it. Since 2019–2020 Google treats it as a hint, not a directive — and it does not reliably block crawling or indexing. a cross-silo link; (5) avoid the classic mistakes — over-siloing, orphaning cross-topic content, boundaries drawn around your org chart instead of search intent; (6) audit with a crawl to confirm the links you planned actually exist.

Evidence for this claim Descriptive internal links help users and Google understand the linked page; Google does not require rigid topic-isolation silos. Scope: Current Google link guidance; the absence of a silo requirement is not a ranking-system claim. Confidence: high · Verified: Google Search Central: Link best practices Evidence for this claim Google recommends a logical site structure and linking important pages from other relevant pages. Scope: Current Google SEO Starter Guide. Confidence: high · Verified: Google Search Central: SEO Starter Guide

First, the debate this article is not having

If you came here asking “is siloing dead?” or “silo vs. topic cluster — which is right?”, that’s answered in full elsewhere in this cluster. This site’s site architecture article runs the whole silo vs. hub-and-spoke vs. topic-cluster comparison and lands where I land: keep the topical concentration silos were reaching for, drop the strict “never link between silos” rule, and stop shopping for the “correct” brand name. Go read that if you want the why.

One naming note, since “silo” gets used loosely across the industry: the term comes from Bruce Clay’s early-2000s SEO methodology, which described two variants — a physical silo (URL-folder isolation) and a virtual silo (the same isolation enforced through internal-link structure alone, without moving URLs) — paired with a strict no-cross-linking rule. Later frameworks (HubSpot’s topic clustersSite 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., the hub-and-spoke language this cluster uses) cover similar ground — group by topic, link deliberately — but they’re not the same named methodology, and none of them kept the isolation rule. This article uses “silo” the way most practitioners do today: loosely, to mean any topically concentrated hub-and-spoke structure, not Bruce Clay’s original method specifically.

This article assumes you’ve already accepted that a topically concentrated, sensibly cross-linked structure is the goal — and it answers the next question: how do you actually build one? Everything below is a build/audit SOP. Where a “why” question comes up, I’ll point back to the architecture piece rather than re-argue it.

Step 1 — Draw silo boundaries with keyword research

The single most underspecified step in every competing “how to silo” guide is where the boundaries go. Guides say “group by topic” and move on. The useful version is more specific: a subtopic earns its own spoke when it has demonstrated, distinct search demand — not when you need another page to hit a quota.

Practical signals that a subtopic is a real spoke and not a padding page:

  • It has its own search volume, separate from the parent term. If “welcome email sequence” gets meaningful searches independent of “email marketing,” it’s a spoke.
  • It shows up as its own cluster of related searches / People Also Ask. HubSpot’s own cluster-research mechanic is reusable here even though they don’t call it siloing: start from a seed term and read the People Also Ask boxes — those are the related questions Google already groups with your seed, and each is a candidate spoke.
  • Its SERP looks meaningfully different from the parent’s SERP — different intent, different result types, different competing pages. If the two SERPs are nearly identical, you don’t have two topics; you have one.

Ignore the “minimum pages per silo” numbers

You’ll see confident, specific numbers everywhere: 5 pages minimum, 4–8 silos per site, 10–20 cluster pages, HubSpot’s 20 to 30 supporting articles. Notice that they contradict each other and none are sourced to actual data. Treat them as evidence that there is no standard, not as guidance to follow. The real test is distinct demand per subtopic — the same “no magic number of cluster pages” position this cluster’s site-architecture article takes. If a subtopic can’t fill even two or three genuinely different pages, it isn’t a silo; merge it up into the hub.

Watch for cannibalization at the boundary

If two proposed spokes would both reasonably target the same query, the boundary is drawn wrong. That’s not a sign you need two competing pages — it’s a sign those two pages should be one. Drawing boundaries from real keyword clustering (shared SERP overlap, distinct volume, distinct intent) prevents this; drawing them from how your business thinks about its offering doesn’t.

Step 2 — URL structure is organization, not architecture

Here’s the one-line version, because this cluster’s site-architecture article already makes the full case: the link graph is the architecture, not the URL path. Google works out hierarchy from how your pages link to each other, not from your folder names. A page at /email-marketing/welcome-sequences/ signals nothing to Google beyond what its content and its inbound 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. say about it.

So what should you actually do with URLs? Mirror the silo in your folder structure if it helps you and your editors keep the site organized — that’s completely fine and normal. The mistake is believing the folder does the SEO work. And the worst version of that mistake is nofollowing links that cross a folder boundary because the boundary feels sacred (more on that in Step 4). Put pages wherever your CMS is happiest; then go do the actual linking work, which is Step 3.

This is the load-bearing step, and it’s the one competitors hand-wave. “Link related pages to each other” is not a procedure. Here’s a concrete one, modeled directly on Google’s own description of a topic hierarchy in its ecommerce docs — “add links from menus to category pages, from category pages to sub-category pages, and finally from sub-category pages to all product pages”. That’s Google describing a hub → spoke → sub-spoke link matrixAn internal linking strategy is the deliberate, planned process of deciding which pages on a site should link to which others — with what anchor text and in what priority order — before or while you build, rather than adding links ad hoc as you publish.. Adapt it:

  • Hub → every spoke. The hub links to every spoke in its silo — ideally in-context, where that subtopic is introduced in the hub’s body, not just dumped in a list at the bottom. A spoke the hub doesn’t link to is effectively outside the silo.
  • Spoke → hub. Every spoke links back to the hub. A “part of our [topic] guide” line, a breadcrumb, or a contextual back-link all work. In the practitioner PageRankPageRank 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.-flow model of internal linkingLinks between pages on the same site., this is the link that’s supposed to help the hub gather authority from its spokes — Google hasn’t published a formula confirming that, so treat it as a planning heuristic, not a guaranteed ranking effect.
  • Spoke → sibling spokes. Spokes link to each other where genuinely relevant to the reader — “for X, see also Y.” Not a forced link to every sibling; not zero either. Relevance is the filter.

The concrete deliverable nobody in the top results ships: a link-matrix spreadsheet. Rows = every page in the silo. Columns = every page in the silo. Each cell = a checkmark if the row page links to the column page. It looks like this:

links from ↓ / to →HubSpoke ASpoke BSpoke C
Hub
Spoke A
Spoke B
Spoke C

Fill it in twice. Once to plan the silo before you write — it makes gaps obvious at a glance (an empty row is a page that isn’t linking out; an empty column is a page nothing points to). Then again after you publish, filled from an actual crawl export instead of from memory, as your audit (Step 6). It’s the same artifact doing double duty, and it’s the single most practical tool in this whole guide.

Step 4 — Reasonable cross-linking rules of thumb

The strict-silo crowd treats every cross-topic link as a leak to be prevented. That instinct is wrong (again, the full argument is in the site-architecture article). Here’s the practical replacement — how to decide when to link out of the silo:

  • The “would this link exist anyway?” test. Would you add this link if silos didn’t exist at all — if it were just a helpful pointer for the reader? If yes, add it. If you’re only adding it to “connect the silos,” skip it; if you’re only avoiding it to “protect” the silo, add it.
  • Relevance beats direction. Don’t reserve cross-links for “sending equity out,” and don’t avoid them to “keep equity in.” A contextually justified link is good regardless of which silo it points to.
  • Volume matters. A handful of well-placed, genuinely relevant cross-links per page is healthy. A page that cross-links constantly to unrelated clusters is diluting its own topical focus — but that’s a content-focus problem, not a reason to reinstate silo walls.

This is the build-mechanics myth worth busting directly, because it’s the single most common bad advice in the competing SERP. Bruce Clay’s originating methodology literally recommends it — “If you absolutely had to link the creamy peanut butter page to the flavored jelly page, you would want to do it with a rel='nofollow' link attribute”. Don’t.

PageRankPageRank 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. sculpting via nofollowrel=\"nofollow\" is a value of the HTML link rel attribute that tells search engines you don't vouch for a linked page and don't want to pass ranking signals to it. Since 2019–2020 Google treats it as a hint, not a directive — and it does not reliably block crawling or indexing. has been broken since 2009. Before then, nofollowing a link redistributed its share to the page’s other links; Google changed that so the equity assigned to a nofollowed link now evaporates — it doesn’t get redirected or saved, it’s just gone. So nofollowing a cross-silo link doesn’t protect anything; it destroys the equity that link would have passed. This site’s internal links article covers the sculpting-is-dead history in full. The takeaway for silo-building: link normally when it’s relevant, follow included.

Step 5 — Common implementation mistakes

The four ways silo builds go wrong in practice:

  • Over-siloing. Creating more, thinner silos than the topic supports — padding to hit an arbitrary page count. The result is thin, redundant pages competing with each other (cannibalization) instead of pooling authority. Fix: draw boundaries from demand (Step 1), and merge subtopics that can’t stand alone up into the hub.
  • Orphaning genuinely cross-topic content. A piece that legitimately spans two silos — say, “email marketing for ecommerce” — gets forced into one silo and either never linked from the other, or awkwardly left out because it “doesn’t fit” the isolation model. Fix: let the page live in one place but be linked from both relevant hubs and spokes. That’s cross-listing, not duplication — this very site does it with an alsoIn pattern (described in the site-architecture article), where an article lists in more than one cluster instead of being walled into one.
  • Boundaries that match your org chart, not search intent. Drawing silo lines around how the business organizes its offering (by product line, by internal department) instead of how searchers group and phrase queries. Fix: validate every boundary against actual keyword/SERP clustering (Step 1), not an internal structure.
  • Trusting the folder instead of the link graph. You put the pages in the /topic/ folder, assume the silo is “built,” and never check whether the pages actually link to each other. The folder existing doesn’t mean the linking work got done — which is exactly why Step 6 exists.

You planned the matrix in Step 3. Now verify it landed. Three complementary tools: none of them, alone, proves the topics “worked” for a reader or a search engine — a visualization or a matrix fill rate is a proxy, not a score. Beyond hub↔spoke links, check whether every spoke is actually reachable by following links from the hub (not just present in a report), whether the cross-group edges to other silos are the ones you intended and not stray leftovers, and then walk the pages yourself the way a reader would — a crawl finds link edges, it doesn’t tell you whether the path makes sense to a person. Track discovery, crawl, and indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. status for the silo’s pages separately from any ranking change that follows; a rewired link graph can move all three, but that’s not evidence the rewiring caused a ranking or traffic change — too many other things move at once on a live site to claim that.

Screaming Frog crawl visualisations

Crawl the site and open the force-directed diagram or tree graph — a node-and-line renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. of the actual crawled link graph, colored by crawl depthCrawl depth usually means click depth — how many clicks it takes to reach a page from the homepage by following internal links. It can also mean a crawler setting that limits how many levels deep a crawl goes before it stops.. It’s the fastest way to see whether a topic’s pages visually cluster together or are scattered and disconnected. Use it as a communication and pattern-spotting tool, not a data source — Screaming Frog is explicit that “the crawl visualisations are useful when analysing site architecture, and internal linking”, but also warns they “don’t provide any more data than is already available in a crawl… don’t always tell the whole story.” Great for spotting a stranded spoke at a glance; not a substitute for the data-level checks below.

Ahrefs Site Audit

Three reports, in the same priority order this cluster’s internal-links article uses for any internal-link audit (orphans → broken links → link-equity opportunities):

  1. Orphan PagesAn orphan page is a page on your site that no other page links to internally. Because crawlers discover pages by following links, an orphan page is effectively invisible to search engines unless it's in an XML sitemap or linked from an external site. — zero-inlink pages. A silo build most commonly leaves behind the last spoke you added, so this catches the pages nothing in the silo points to.
  2. Internal Link Issues — broken internal links inside the silo. A hub linking to a spoke’s old URL is a link that isn’t doing its job.
  3. Link Opportunities“relevant internal linking suggestions” based on keyword overlap between pages, sortable by Page Rating so you can prioritize which high-authority pages should be doing the linking. I’ve written about using this for silo linking specifically in SEO Silo Structure: Why It Makes No Sense (And What to Do Instead)“the Link Opportunities tool… suggests where you should add internal links.”

The spreadsheet from Step 3, filled from reality. Crawl the silo’s URLs, export the outlinks (Screaming Frog’s outlinks export, or an Ahrefs crawled-pages export), and fill each cell from actual crawl data — not from what you think you linked. Empty rows = pages not doing their linking job. Empty columns = pages nothing in the silo points to (an orphan risk within the silo even if the page is linked from somewhere else on the site).

TIP Prioritize the missing links after the matrix audit

The score and visible reasons make a proposed link reviewable. They do not prove that the source passage supports the destination, so keep editorial relevance as the final gate.

Score supplied hub and spoke pages with my free Internal Link Cluster Visualizer Free

  1. Supply the silo pages with titles, URLs, and their current internal links.
  2. Review high-scoring pairs where the target has few or no supplied links.
  3. Add only links that fit the source passage, then refill the matrix from a new crawl.

When to re-run it

After the initial build, then every time you add a spoke to an existing silo. New pages are the most common point of failure — you’ll update the hub to link to the new spoke and forget the sibling cross-links, or forget to link the new spoke back to the hub. Re-running the matrix after each addition catches that in about five minutes.

FAQs

How many pages should a silo have? No fixed number. Competing guides cite 5, 8, 10–20, and 20–30 and contradict each other. Use distinct search demand per subtopic as the test, not a quota.

Should I nofollow links between silos? No. PageRank sculpting via nofollow has been broken since 2009 — the equity evaporates rather than being protected. Link normally when it’s relevant.

Does my 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. need to match my 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.? It can, for organizational convenience, but Google reads your internal link graph, not your folder names. See this cluster’s site-architecture article for the full case.

What tools audit a silo structure? Screaming Frog crawl visualisations, Ahrefs Site Audit (Orphan Pages, Internal Link Issues, Link Opportunities), or a manual link-matrix spreadsheet built from a crawl export.

Can a page belong to more than one silo? Yes — via cross-listing (linking it from multiple relevant hubs) rather than duplicating it or forcing it into one bucket. This site’s alsoIn pattern is a working example.

Add an expert note

Pin an expert quote

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