The Anchor and the Chain: On the Subtle Tyranny of the 'Relevant' Internal Link
There is a piece of advice so common in our trade that it has calcified into unquestionable doctrine: every internal link must be contextually relevant. We are told to weave our site’s architecture with threads of pure semantic connection, tethering articles only to their closest conceptual cousins. A recipe for sponge cake should link to another for buttercream frosting, not to a meditation on the history of sugar. This seems logical, even elegant. But in our pursuit of this pristine relevance, I fear we are building not a web, but a series of very short, very predictable chains.
The dogma of relevance is, at its heart, a doctrine of limitation. It assumes a user’s curiosity is a linear path, a single train of thought moving neatly from one station to the next. It presumes we can anticipate the entirety of a reader’s journey based on the single keyword they are currently consuming. This is a profound misunderstanding of how human curiosity actually functions. Curiosity is not linear; it is associative, digressive, and wonderfully unpredictable. A reader engrossed in a technical analysis of vintage watch movements might, in a moment of mental respite, be delighted by a link to an article on the decline of mechanical drafting tools. The connection is not direct, but it is human.
By forbidding these lateral leaps, we sterilize the experience of discovery. We create a site that feels less like a library full of surprising connections and more like a meticulously organized filing cabinet, where the only thing you can find is what you already knew was there. The 'relevant' link confirms a user’s existing trajectory. The 'irrelevant' one—or rather, the unexpectedly associative one—can launch them on a new one. It is the difference between a hallway that only leads to the next room and one that contains a hidden door to a garden you never knew existed.
This is not an argument for spammy or entirely random linking. The anchor text must still honestly describe its destination. The link must not feel like a non-sequitur that breaks the reader’s flow. The artistry lies in finding those subtle, thematic bridges—the shared notion of craftsmanship between watchmaking and drafting, the shared history between two seemingly disparate technologies, the philosophical thread connecting two different eras. This is how you build a domain with depth and personality, a place that rewards exploration rather than just navigation.
Relevance is a good servant but a terrible master. Our internal linking strategy should aspire to be more than a utility for passing authority or guiding users along a pre-determined funnel. It should be an editorial voice, a curator’s subtle hand on the shoulder, pointing not only to what is obviously next, but to what is surprisingly adjacent. Break the short chains of pure relevance. Plant seeds of curiosity that might grow into unpredictable and far more engaging journeys.
Notes & further reading
A few pages I came back to while writing this:
- a practical rundown
- The Broken Thread: On the Practical Ritual of the Dead-End Audit
- Little Rock, AR
- The Hollow Core: On the Tyranny of Exquisite Site Structure
- Gilbert, AZ
- The Alexandria Model: On the Perils of a Single Canonical Address
- Peoria, AZ
- Surprise, AZ
- Elk Grove, CA
- Pasadena, CA
- New Haven, CT
- Stamford, CT
- Washington, DC