The Translator's False Cognate: On the Shared Word That Means Another Thing
We often speak of a site's URL structure as a kind of language. It has a syntax, a vocabulary, and, ideally, a logic that both users and machines can parse. But there’s a subtle peril in this linguistic metaphor, one that doesn’t appear in broken links or 404 errors, but in the quiet, successful resolution of a request. It’s the peril of the false cognate: two words that look or sound identical across languages but carry entirely different meanings. In our digital architecture, this manifests not as a broken path, but as a perfectly functioning redirect that translates a user’s intent into the wrong destination.
Consider a common, well-intentioned scenario. Your site once had a section at /insights/reports, a repository for lengthy, formal white papers. Later, you launch a livelier blog for short articles at /blog. Deciding the old ‘reports’ section is redundant, you redirect /insights/reports to /blog. The server returns a clean 301, the link is ‘mended,’ and the logs show no errors. Technically, it’s a success. Semantically, it’s a betrayal. The user who bookmarked or searched for ‘reports’ anticipated depth, analysis, and formality. The redirect, our false cognate, cheerfully delivers them to a stream of casual posts. The word ‘reports’ and the path /insights/reports promised one thing; the new location speaks another language entirely.
The Semantics of the Path
This is where site stewardship moves beyond mere plumbing into the realm of semantics. A redirect is not just a traffic signal; it’s a translator. Its primary duty is to preserve meaning, not just to avoid a dead end. When we consolidate content or restructure a site, we must ask a harder question than “Where should this traffic go?” We must ask, “What did this path mean, and does the destination honor that contract?”
The failure of the false-cognate redirect is a failure of empathy. It assumes that any page is better than a missing page. But to the user with specific intent, a gentle, explanatory 404—or better yet, a curated archive page—can be far more respectful than a jarring, context-less shift. The 404 says, “This specific thing is no longer here, let me help you find it.” The false-cognate redirect says, “This is probably what you meant,” and is often wrong.
Avoiding this requires a kind of cartography of intent. Map the old URL’s promise—its content type, its tone, its purpose—and seek the closest true semantic match, even if it’s not a perfect one-to-one. Perhaps /insights/reports should go to a filtered view of the blog showing only long-form content, or to a new /resources/whitepapers section. Sometimes, it means not redirecting at all, but decommissioning with clarity. The goal is to maintain the thread of the user’s understanding, so they never feel the disorienting click of a shared word that suddenly, silently, means another thing.
Notes & further reading
A few pages I came back to while writing this: