The Unwelcome Mat: On the Politeness of Pervasive Redirect Chains

There is a piece of received wisdom in web architecture so commonly accepted it’s practically chiseled into stone: a redirect is a polite gesture. It’s the web’s equivalent of a friendly usher, seeing a lost theatre-goer from an old seat to a new one. This is the story we tell ourselves, especially when we implement chains of redirects—a 301 to a 301 to a 301, leading a user (or a bot) step-by-step to their final destination. We believe we are being thorough, even conscientious. But I’d like to propose a heretical thought: a long redirect chain is not a courtesy. It is a series of locked doors, each requiring a key you must wait to be handed.

Consider the physical metaphor we so often neglect. If you walked into a building looking for an office, and the person at the front desk didn’t give you directions but instead walked you to another desk, who then silently walked you to a third, who then pointed you down a hall, you would not feel served. You would feel shuffled. Each hand-off, no matter how swift, introduces a moment of latency, a tiny fracture in the user’s sense of agency. On the web, these fractures are measured in milliseconds, but they accumulate into a palpable sensation of friction. The user clicks, waits, is moved, waits again, and is moved once more. They are not navigating; they are being processed.

This is where our technical understanding of efficiency collides with the human experience of flow. To a search engine crawler, a well-formed redirect chain is a logical, if suboptimal, path. It’s a puzzle to be solved, and the bot has the patience. But a human visitor is on a journey of intent. They have a goal. Every additional HTTP request, every new handshake between server and browser, is a detour that pulls them out of their purpose. The politeness we imagine we are offering is, in practice, a form of bureaucratic obstruction. We have prioritized the completeness of the audit trail over the immediacy of the destination.

The justification, of course, is legacy. We redirect A to B because B moved to C, and we can’t break old links. This is a responsible impulse. But it often masks a deeper architectural timidity—a reluctance to perform the definitive surgery of updating links at their source or implementing a single, clean redirect. We layer the new path over the old, creating a sedimentary record of our site’s evolution. The user, however, has no interest in our archaeology. They seek the living page, not its fossilized trail.

The Cost of Courtesy

So what is the alternative to this endless politeness? It is a quiet boldness. It is the willingness to make a decision and see it through directly. Where possible, this means collapsing chains into a single, decisive redirect. It means auditing internal links to point to canonical URLs with a finality that obviates the need for redirection at all. It is an ethos that values the user’s time more highly than the preservation of every single, obsolete pathway.

A redirect should be a bridge, not a guided tour of the bridge’s construction history. True politeness on the web is not found in documenting every step of a page’s long life, but in the graceful and instantaneous fulfillment of a user’s request. It is the difference between a host who says, "Your table is right this way," and one who insists on showing you the kitchen, the pantry, and the wine cellar before you are allowed to sit down. One is a service; the other, however well-intentioned, is an imposition. Perhaps it is time we stopped being such meticulous hosts and started being better guides.

Notes & further reading

A few pages I came back to while writing this: