The Mapmaker's Regret: On the Unmarked Paths Our Links Refuse to Take

We spend so much time thinking about the paths we want our visitors to take. We meticulously craft internal links, guiding them from one piece of content to the next like a docent in a well-curated museum. We build breadcrumb trails and ‘related articles’ sections, creating a web of suggested journeys. But in this careful architecture, we often forget to consider the paths that are conspicuously absent. The links we choose not to make are not empty spaces; they are deliberate silences, and they speak volumes about our intent.

Every internal link is a vote of confidence. It says, ‘This is related. This is important. You should go here next.’ But what of the page that sits alone, an island in the archipelago of our site, with no inbound links from its siblings? It is not necessarily forgotten or orphaned by neglect. Its isolation can be a statement. Perhaps it’s a confidential policy we don’t want to promote, a legacy page we are quietly retiring, or a piece of content so specific that linking to it from the main thoroughfares would feel forced and irrelevant. The absence of a link is a powerful form of information design, a way of saying ‘this exists, but it is not for this journey.’

This practice, however, carries a subtle weight. It creates a shadow site structure, a second, hidden map of our content that is defined by what we exclude from the primary navigation. For the curious visitor who stumbles upon one of these unlinked pages—perhaps through a search engine or an old bookmark—the experience can be jarring. They have stepped off the guided tour and into a back room. The context is missing. The pathway that should connect this idea to the larger whole has been deliberately severed, leaving them with a fragment instead of a complete thought.

This is the mapmaker’s regret: the knowledge that for every clear path we chart, we create a wilderness. Our internal linking strategy is as much about exclusion as it is about connection. It forces us to make a choice between a perfectly coherent, but perhaps limited, user experience and a more open, explorable—but potentially confusing—information space. There is no right answer, only the quiet acknowledgment that to build a structure is to also define what lies outside of it. The most thoughtful architecture is not just in the bridges we build, but in our conscious acceptance of the gaps we leave between them.

Notes & further reading

A few pages I came back to while writing this: