What is a content silo?

A content silo groups related website pages around a subject and defines how those pages connect. Some silo models restrict links between groups as well as organizing pages within them. When reviewing a silo proposal, identify its grouping and linking rules before deciding what the arrangement would mean for a reader.

A diagram can place a page neatly inside a category while leaving its visitor without a useful next step. Review what the page contains, where readers would look for it and which related resource they need. The group label alone does not answer those questions.

Read the rules behind the model

Bruce Clay's siloing newsletter describes arranging website content by themes. It calls grouping through internal links “virtual siloing” and grouping through URL directories “physical siloing.” These are the publisher's terms for its model.

The newsletter's virtual model restricts links across silo boundaries. That restriction is part of the described approach, rather than a universal instruction from Google. Ask what a proposed restriction would remove and why the team wants it before applying the rule to existing pages.

Separate the page group, the address and the route

A page's assigned group, its URL path and its incoming links describe different things. A plan may put a room-booking page in a “Room hire” group, but you still need to inspect the actual menu or contextual link that leads to it. A folder name does not create that connection.

Google's ecommerce site-structure guide says it generally analyzes links between pages, rather than URL structure, to work out site structure.

A fictional centre reviews a cross-group link

Fictional example: Oakwell Community Centre is reviewing a proposal with separate “Room hire” and “Visiting” groups. Its proposed page list contains the following resources.

Oakwell's proposed groups

  • Room hire: Room choices; Request a booking.
  • Visiting: Directions to the centre.

The proposed rule forbids a link from “Request a booking” to “Directions to the centre” because the pages belong to different groups. The editor identifies a concrete reason for that connection: someone arranging a room needs to know where participants should arrive.

The editor asks to retain a contextual link labelled “Directions to the centre” beside the relevant arrival information. That decision keeps the groups while allowing the useful route. Before publication, the team still needs to confirm that the destination actually provides the directions its label promises.

The group list and the link decision are separate records. The list explains where the resources sit in the proposal; checking the published page establishes whether the visitor can follow the intended route. Keep the required connection visible when revising the plan.

Site architecture concerns the wider organization of pages, navigation and discovery paths. A content hub gives visitors an entry point to a collection of resources. For a silo proposal, examine the particular grouping and boundary rules instead of assuming either label prescribes a single layout.

Topic-cluster plans also organize related coverage and links. Do not infer a universal strict-versus-loose distinction from the names alone. Read the actual plan: which resources belong together, how visitors reach them and which connections the proposal permits or prevents?

Choose links for the resource they reach

Google's link guidance recommends descriptive anchor text and relevant internal resources in context. It also says there is no ideal number of links for a page. Those recommendations provide a more concrete review question than a sibling-link quota: does this connection help the reader understand the page or reach a needed resource?

Check the destination and its label together. A route to an unrelated category page does not necessarily replace the specific guide a reader needs. If the plan removes a useful connection, record the lost task and examine an alternative before treating the diagram as finished.

Review a specific path before changing the site

Choose a reader task and follow the current route through the actual pages. Note where a relevant destination is missing, a label is unclear or an intermediate page adds no useful choice. Your internal-linking review can address that connection without turning every grouping decision into a URL migration.

Write the proposed change beside the affected page and the reason for it. In Oakwell's fictional plan, the required action is checking a directions link from the booking page. Keep the original arrangement recoverable and verify the revised route after the change.

Sources and example scope

Bruce Clay supplies the attributed silo model; Google's documentation supplies link and ecommerce-structure guidance. Oakwell and its proposed groups are fictional. The path-review questions are editorial recommendations.