The Translator's Unshared Idiom: On the False Consensus of a 'Universal' Site Structure

There’s a map we tend to draw when planning a new site, a sort of received wisdom etched into the collective consciousness of web development. It’s a clean, logical hierarchy: a homepage that branches into sections, which in turn lead to categories, which finally spit us out at the destination of individual pages. We call this Information Architecture, and we treat it with the reverence of a fundamental law. But I’ve come to see this idealized pyramid not as a universal truth, but as a specific dialect—one that often fails to account for the unique idioms of content, audience, and purpose.

The problem with a ‘universal’ structure is its presumption of a universal user. It assumes a linear, goal-oriented visitor who appreciates our neat taxonomies. Yet, human curiosity is rarely so orderly. A reader might land on a deeply technical article from a search engine, fascinated by a tangential detail, with no interest in navigating ‘up’ to the ‘Programming’ category to which it ‘belongs’. To them, our cherished hierarchy is an irrelevant scaffold, invisible at best and a confusing maze at worst. The structure we build for administrative clarity can become a barrier to intuitive exploration.

This is where the cult of the perfect site map can lead us astray. We spend endless hours debating whether a page should live under ‘/services/consulting/’ or ‘/solutions/enterprise/’, as if the ‘correct’ path will be divined by both users and algorithms. We treat these URL paths as immutable classifications, forgetting that they are, first and foremost, a tool for wayfinding. The semantic weight we assign to a folder name like ‘/blog/insights/industry-news/’ is often far heavier than any user will ever impart. They are looking for an answer, not a lecture on our filing system.

Internal linking, then, becomes the crucial translator of this rigid structure. It’s the network of footnotes, asides, and recommendations that allows a user to bypass our official hierarchy entirely. A well-placed contextual link from one deep article to another, unrelated but conceptually adjacent piece, is more valuable than a perfectly rendered breadcrumb trail. It creates a web of meaning that exists parallel to the site map—a structure built not on container labels, but on genuine relational context. This secondary, organic structure often reflects the user’s actual journey far more accurately than our top-down blueprint.

This isn’t an argument for anarchy. A logical foundation is essential for maintenance and, to a degree, for accessibility. But it is a critique of purity. The most effective site structure isn’t the one that looks most elegant in a diagram; it’s the one that feels most natural in use. It accepts that its primary taxonomy is just one of many possible paths. It embraces redirects not as admissions of structural failure, but as graceful adaptations to a changing understanding of our own content. It understands that our job is not to force a universal language upon our visitors, but to learn their dialect and build paths that feel like native terrain.

Notes & further reading

A few pages I came back to while writing this: