The Footpath and the Streetlight: On the Deliberate Neglect of the Shortest Path
Our modern web is obsessed with efficiency. We treat pages as destinations and links as the most direct route. The entire machinery of SEO, information architecture, and even user experience (UX) design often feels like a grand civic project to pave every road, install brilliant streetlights, and ensure no traveler ever feels lost or takes a wrong turn. The internal link is the ultimate expression of this: a sanitized, well-lit corridor from one piece of content to the next, designed for maximum speed and minimum friction. It’s the highway interchange.
But cities are more than their highways. The soul of a place often resides in its footpaths—the worn-down trails in the grass that cut across the manicured lawns, the alleys between buildings that aren’t on the official map. These paths are created not by planners, but by use. They are evidence of a more organic, human-driven navigation. They represent a choice, often a conscious one, to ignore the ‘proper’ route in favor of one that feels more direct, more interesting, or simply more natural.
What is the digital equivalent of this footpath? It’s the URL bar.
Every time a user, especially a power user, bypasses your carefully crafted internal navigation and instead glances at the address of the page they’re on, edits it, and hits enter, they are cutting a footpath. They are rejecting your streetlights in favor of their own intuition. They see the structure inherent in your URL schema—/blog/2024/05/post-title—and they understand it. They might navigate ‘up’ a level by deleting the post title to see the monthly archive, or change the date to explore what you wrote last year. This is not a failure of your internal linking; it is a testament to the clarity of your underlying structure.
This act of deliberate pathfinding reveals something profound about user intent. The user clicking a ‘Related Articles’ link is browsing. The user editing the URL is hunting. They have a specific, directed goal that your pre-defined pathways may not anticipate. They are not lost; they are exploring the map you provided at a more fundamental level. This is the user who understands your site not as a series of pages, but as a system.
Should we try to pave these footpaths? Should we anticipate every possible URL edit and redirect it to a ‘proper’ page? Often, the best action is deliberate inaction. A well-designed URL structure should be resilient enough to handle this kind of exploration. A ‘404 Not Found’ for a half-formed, guessed-at URL isn’t necessarily a failure—it’s a boundary. It’s the edge of the park where the worn dirt path meets an actual fence. It tells the explorer where the known world ends.
By embracing, or at least accepting, this behavior, we acknowledge that the most efficient pathway isn’t always the one we build for our users, but the one they build for themselves. Our job is not to control every step of the journey, but to build a landscape with a legible grammar—a URL structure so clear that it invites this kind of intelligent, direct manipulation. The goal is not to eliminate the footpaths, but to lay out the city in such a way that the footpaths that naturally form are themselves a feature, a sign of a living, understood, and engaging digital space.
Notes & further reading
A few pages I came back to while writing this: