Internal Linking as Architecture, Not Decoration

It is easy to treat internal linking as the last thing added to a page, a courtesy pass to make sure nothing is an orphan before publishing. That treatment misses what internal links actually do in a GSO context. Every link is a structural claim: this page relates to that page, in this specific way. Pillar-to-spoke links claim membership in a silo. Spoke-to-spoke links claim a relationship between two resolved needs. Cross-silo links claim a connection between otherwise separate topics. Generative systems read these claims the same way they read the entity relationships covered in Chapter 6.2, as signals of how a domain's knowledge actually connects, not as UI elements to route a reader from one page to another.

What Internal Links Communicate Structurally, Beyond Navigation

An internal link is a claim of relationship. When one page links to another, it asserts that the two pages connect in some specific way, whether that connection is “this page is part of the silo this pillar frames” or “this specific need is naturally related to the one you’re reading about now.” That claim carries information independent of whatever click-through behavior the link produces.

This reframing matters because it changes what counts as a good link. A link judged purely on navigational usefulness might be justified by “this seemed like a reasonable place to send the reader.” A link judged as a structural claim has to be justified by a genuine, specific relationship: what exactly connects these two pages, and does the link communicate that relationship clearly through its anchor text and placement, or does it just point somewhere without explaining why. The anchor text guidance already established in this framework’s writing standards, using the actual name of the destination topic rather than “click here” or “read more,” is not just a readability preference in this context. It is what makes the relationship claim legible rather than opaque.

Pillar-to-Spoke and Spoke-to-Spoke Linking Patterns

Pillar-to-spoke links, covered from the pillar’s side in Chapter 8.2, claim silo membership: this spoke is part of the topic the pillar frames, and the link should communicate specifically what question that spoke resolves, not just that it exists.

Spoke-to-spoke links, covered from the spoke’s side in Chapter 8.3, claim a narrower and often more valuable relationship: two specific resolved needs that a reader is plausibly weighing together, or a natural sequence where one need leads to the next. These two link types are not interchangeable, and a silo that only implements pillar-to-spoke links while leaving spoke-to-spoke relationships unlinked is missing real structural signal. A reader who has just resolved one specific need and has a closely related next question benefits far more from a direct spoke-to-spoke link than from being routed back through the pillar to make a second selection, and the same directness benefits a retrieval system trying to understand how the domain’s specific resolved needs relate to each other.

Linking Across Silos Without Diluting Silo Boundaries

Cross-silo linking, connecting a page in one semantic silo to a page in a genuinely different one, is possible without undermining the silo boundaries established in Chapter 8.1, provided it is used deliberately rather than as a routine practice applied to every plausible tangent.

The test is the same specificity test that applies within a silo: does a genuine, describable relationship exist between these two pages, even though they belong to different topical boundaries. A page about choosing running shoes and a page about training plans for a first marathon belong to different silos but have a real relationship a reader might benefit from. Linking them deliberately, with anchor text that explains the connection, is different from a site that cross-links liberally across every silo out of a vague sense that everything on the domain is somewhat related. The latter pattern dilutes the topical coherence signal silos exist to send in the first place, since a generative system reading heavy, undifferentiated cross-silo linking has a harder time inferring where one coherent topic boundary actually ends and another begins.

Internal Linking as a Relationship Signal

Internal linking is one of the concrete mechanisms, alongside consistent naming and clear organizational attribution, that makes entity and topic relationships explicit rather than assumed, directly extending the entity relationship work established in Chapter 6.2.

Just as an unstated author-organization relationship reads as ambiguity to a generative system, an unstated relationship between two clearly related pieces of content reads the same way. A domain that has genuinely related content sitting in isolation, each page technically excellent but never linked to the other despite an obvious connection, is leaving a structural signal unmade that costs nothing to build and directly strengthens the topical coherence that source evaluation reads. This is why internal linking belongs in an architecture chapter rather than being treated purely as a technical SEO checklist item: the links themselves are part of what makes a domain’s knowledge structure legible to the systems this framework is built around.

Auditing Link Structure for Architectural Gaps

An internal link audit in the GSO context looks for something different than a standard technical SEO audit, which typically checks for broken links and orphaned pages. This audit looks for architectural gaps: genuine relationships between pages that exist conceptually but have never been made explicit through an actual link.

The practical method starts from the silo and intent cluster structure established earlier in this chapter: for each pillar, verify every relevant spoke is linked with specific, descriptive anchor text. For each spoke, check whether genuinely related spokes, within the silo or, deliberately, across silo boundaries, are linked to each other. Look specifically for content pairs that address related decisions or sequential needs but currently have no link connecting them at all. This audit is worth running as a distinct exercise from ordinary broken-link maintenance, since a link that works perfectly can still represent a missing architectural signal if it points to the wrong relationship, or if an important relationship has no link representing it whatsoever.

Maintaining Link Integrity as Content Grows

Link structure that was correct at publication does not stay correct automatically as a silo grows. New spokes get added that should connect to existing content but don’t yet. Content gets restructured or consolidated, and links built for an earlier structure can point to pages that have moved, merged, or been retired.

Maintaining this over time requires the same governance discipline established for entity coherence in Chapter 6.3: a standing practice, not a one-time cleanup. When a new spoke is published, the pillar and any genuinely related existing spokes should be updated to link to it, not left to accumulate as an isolated addition to the silo. When content is restructured, an internal link audit should be part of that restructuring process, not an afterthought discovered later when a reader or a routine crawl surfaces a broken or orphaned page. This maintenance is unglamorous in exactly the way the entity coherence work in Chapter 6 is unglamorous, and it accumulates as debt in the same way when skipped.

Building Link Structure That Carries Real Signal

Michael Rubinstein treats internal linking as one of the cheapest, most consistently underused structural signals available to a GSO practitioner, precisely because it costs nothing beyond the discipline of actually building it deliberately, and because most sites already have the content that would justify the links, just not the links themselves.

ScribePress builds pillar-to-spoke and spoke-to-spoke link structure as part of its default publishing process rather than as a separate pass performed after content is finished, so the relationship signals this chapter describes exist by construction across every silo it produces.

Learn more about the work behind this framework at michael-rubinstein.com.

Put the framework to work