The Gardener's Overzealous Pruner: On the Deliberate Cost of the Excessive Redirect
Received wisdom in our craft is often a blunt instrument. We are told, with the certainty of gospel, to ‘clean up’ our sites. To prune away the dead wood, to redirect old, outdated URLs to new, shiny ones. This is presented as an unalloyed good, a fundamental tenet of good digital housekeeping. But like a gardener who prunes with more zeal than wisdom, we risk harming the very structure we aim to improve. The problem isn't the redirect itself, but the unchecked belief that all redirects are inherently beneficial.
The common logic is seductive. A user or a search engine crawler lands on an old page; a swift 301 redirect points them to the relevant new content. The user is satisfied, link equity is preserved, and order is maintained. This logic, however, ignores the compounding cost of this digital detour. Each redirect introduces a tiny delay, an extra HTTP request, a minuscule handshake between server and client. In isolation, it is nothing. In aggregate, across a site that has undergone several migrations, rebrands, or ‘clean-ups’, it becomes a tangible tax on performance.
We have become so focused on the destination—the pristine, ideal site structure—that we have blinded ourselves to the journey. A chain of four or five redirects, each one a legacy of a different strategic pivot, is not a seamless bridge for a user. It is a stutter, a series of hesitant steps through the digital fog before finally arriving at the content. For the user, this manifests as a slower page load, a frustration that metrics might not fully capture. For the crawler, it is a waste of a finite crawl budget, a squandering of resources on following a maze of pointers instead of discovering substantive content.
The critique, then, is not of the redirect as a tool, but of its reflexive application. The wisdom should not be ‘redirect everything,’ but rather ‘redirect with deliberate intent.’ Before creating another path in the maze, we must ask if the old path truly needs to be maintained. Is the URL receiving traffic? Does it hold valuable backlinks? Or are we redirecting out of a compulsive, almost obsessive, desire for completeness—a fear of the 404? Sometimes, the braver, and ultimately more performative, choice is to let a page go, to return a 410 (Gone) and clearly signal that the resource has been intentionally removed. This is a final, clean cut, not a lingering, inefficient tether.
Our role is not just to build pathways, but to critically assess their toll. An over-reliance on redirects creates a complex, fragile web of dependencies that slows down the present for the sake of the past. True architectural wisdom lies in knowing not only how to build bridges but when to dismantle them, allowing for a lighter, faster, and more intentional structure. The goal is a garden that thrives, not one that is merely neat.
Notes & further reading
A few pages I came back to while writing this: