The Detective's Red Herring: On When a 'Clean' URL Structure Becomes a Blind Alley
There is a sacred text in the SEO and content management world, recited with the reverence of a mantra: keep your URL structure clean, logical, and shallow. We are told to be architects, not janitors. The ideal, we’re promised, is a pristine hierarchy—domain.com/category/subcategory/product—a map so intuitive a user (and a crawler) could navigate it blindfolded. It’s presented as an unalloyed good. But I’d like to posit a heresy: this rigid devotion to a ‘clean’ URL structure can, in certain contexts, become a red herring. It distracts from the real investigation—understanding user intent and semantic relationships—by focusing obsessively on a neat, but potentially misleading, filing system.
The problem lies in the conflation of physical file paths with conceptual meaning. In the early days of the web, a URL often was a direct reflection of a file’s location on a server. That legacy persists in our thinking. We believe that by organizing URLs like folders on a desktop, we’re imposing order. But a website is not a static library of documents; it’s a dynamic, interconnected web of ideas. The logic of a hierarchy is brittle. Where do you put an article that belongs equally to two categories? Do you force a choice, burying it under one branch and obscuring it from the other? The pursuit of ‘cleanliness’ here forces a false taxonomy onto content that naturally resists it.
The Tyranny of the Shallow
Worse is the dogma of ‘shallow’ structure. The fear of deep nesting is so profound that we contort our sites to avoid a few extra slashes. We flatten everything into a sprawling, single-level directory or, conversely, jam complex topics into overly broad parent categories. In doing so, we strip away the very context a thoughtful hierarchy can provide. A URL like /guides/advanced/woodworking/dovetail-joints/ isn’t just ‘long’—it’s narratively rich. It tells a story of progression: from beginner to advanced, within the craft of woodworking, to a specific technique. That depth is information, not clutter. Obsessively shortening it to /dovetail-joints/ in the name of cleanliness severs it from its conceptual home, making it an orphan.
This isn’t an argument for messy, parameter-laden URLs. It’s a plea for intentionality over dogma. A URL structure should serve your content, not the other way around. Sometimes, the most semantically ‘true’ structure isn’t the flattest or the most classically hierarchical. It might be a hybrid, leveraging tags, internal links, and breadcrumbs to create multiple pathways. The redirect and the canonical tag exist as tools precisely because the real world of ideas is messy. They allow us to create a clean facade where needed, while acknowledging the complex, overlapping relationships underneath.
The true goal isn’t a spotless URL log. It’s a coherent, crawlable, and user-intuitive experience. If a user lands on a page and understands where they are in the constellation of your site—through navigation, content, and yes, perhaps a descriptive URL—then the structure is working. If you’ve mangled your content’s natural groupings to fit a Procrustean ideal of ‘clean,’ you’ve followed the red herring. You’ve tidied the desk while losing the case. The most elegant structure is the one that disappears, allowing the meaning of your content to take centre stage, slashes and all.
Notes & further reading
A few pages I came back to while writing this:
- Elizabeth, NJ
- The Lock-Picker's Set: On Cracking the Case of the Misused Backlink
- Albuquerque, NM
- The Librarian's Unwritten Volume: On the Virtue of a Missing Canonical
- North Las Vegas, NV
- The Stonemason's Hidden Keystone: On the Structural Integrity of a Single Redirect
- Reno, NV
- Akron, OH
- Cincinnati, OH
- Dayton, OH
- Tulsa, OK
- Salem, OR
- Charleston, SC