The Watchmaker's Spare Spring: On the Deliberate Preservation of the Redundant Redirect
Conventional wisdom in our field is a relentless pursuit of efficiency. We are taught to streamline, to prune, to consolidate. A redirect chain is the epitome of this inefficiency—a series of hops from URL A to B to C—and the advice is unanimous: eliminate it. Compress it. Point A directly to C. This is presented as an unalloyed good, a clean signal for both users and crawlers. But what if, like a meticulous watchmaker keeping a seemingly superfluous spare part, we are sometimes wise to preserve a degree of deliberate redundancy?
The argument for compression is sound on the surface. Each HTTP request in a chain adds latency. For a user, a fraction of a second; for a crawler, a waste of precious crawl budget. Squashing these chains is a technical best practice, a box to be ticked in any audit. Yet, this perspective is purely mechanical. It ignores the human and historical context in which these URLs exist. A redirect chain is often a timeline, a story of a page’s journey across your site’s evolving architecture. To collapse it is to erase that history.
Consider the long tail. An old URL, from a site structure five iterations ago, might have been bookmarked by a dedicated user. It might be linked from a forgotten forum post, a printed academic paper, or a slide deck from a 2015 conference. The immediate redirect we put in place then was a promise: “This content has moved, but we will bring you to it.” By compressing that chain, we point that old URL directly to the newest canonical page. We fulfill the technical promise but break a contextual one. The user arrives at the destination with no understanding of the path, the context of the original source now entirely invisible.
Preserving a single, intentional ‘redundant’ hop can serve as a gentle historical marker. The first redirect, from the very old URL, can point to an intermediate URL that itself is a well-documented, stable page designed to contextualize the move. This intermediate page can be a simple, text-based explanation: “The content you were looking for from our previous site section has been moved and updated here.” It provides continuity. It acknowledges the user’s intent based on an old understanding of your site and gently educates them on the new one. It treats the redirect not as a technical error to be fixed, but as a narrative device.
This isn’t an argument for preserving mile-long chains of poor planning. It is an argument for thoughtful architecture over mindless compression. The crawl budget cost of one additional, purposeful hop is negligible compared to the value of maintaining a coherent story for the tiny fraction of users who travel these ancient paths. Sometimes, the most elegant solution isn’t the most mechanically efficient one. It is the one that respects the journey as much as the destination. The watchmaker knows the value of every spring, even the spare.
Notes & further reading
A few pages I came back to while writing this: