The Cartographer's Ghost River: On When a Redirect Should Be a Destination
Conventional wisdom in our field is absolute: a redirect is a temporary measure. It’s a ferry, a detour sign, a temporary bridge while the permanent one is built. We are taught to view these URL mappings as transient, often even scheduling them for removal once we assume search engine crawlers and the trickle of legacy traffic have adjusted to the new path. The goal is always the neat, orderly map, free of the dashed lines that indicate a change in course. But this obsession with finality misunderstands the landscape of human curiosity and the true nature of a website as a living archive. There are times when a redirect should not be temporary. There are times when a redirect should be treated not as a bridge to be demolished, but as a destination to be maintained.
Consider the concept of the “ghost river” in geography—a waterway that has been diverted, buried, or paved over, yet whose course can still be traced in the shape of a city’s streets or the recollection of its oldest residents. The path of the ghost river is no longer functional for navigation, yet its memory is etched into the place. Our websites have these too: old URLs that, while no longer hosting the primary content, represent significant moments in our site’s history. They might be the path to a product long discontinued, an event that has passed, or a controversial article we’ve since revised.
The common advice is to 301-redirect the ghost river to the nearest relevant piece of land—say, the old product page to the new product category. But in doing so, we erase the ghost river entirely. We pretend that the past iteration never existed. A visitor, or a scholar, following a deep link from an old forum post or an academic citation, is unceremoniously dumped onto a generic page that lacks the context they were seeking. The redirect, in its efficient haste to clean up, creates confusion. It tells the visitor, implicitly, that their reason for arriving is invalid. The map has been redrawn, and your old coordinates are an error.
What if, instead, we honored the ghost river? What if the destination of that redirect was not a generic landing page, but a specific, permanent memorial? The redirect should lead to a page that acknowledges the former content. It could be a simple, elegantly designed note: “You have reached the former location of our 2018 Annual Report. That document is now archived here, but you can view our current reports on our main financial page.” This approach doesn’t just preserve user intent; it builds trust. It tells the visitor that you respect the pathways they use to find you, even the overgrown ones. It demonstrates a thoughtful stewardship of your own history.
This is the counterintuitive core of the argument: a permanent, well-crafted destination for a redirect can be a more powerful signal of authority and care than a perfectly pruned site structure. It treats your URL architecture not as a sterile floor plan to be optimized, but as a narrative, layered with time. The ghost rivers on your site are not flaws to be hidden; they are evidence of a journey, of growth and change. By mapping them with purpose—by ensuring the redirect leads to a meaningful endpoint rather than just a convenient one—we build a web that is not only more navigable but also more humane. We acknowledge that a destination can be a place of explanation, not just transaction.
Notes & further reading
A few pages I came back to while writing this: