The Gardener's Forgotten Path: On Letting a Redirect Lie Fallow
My grandfather’s garden was a maze of intention. Neat rows of beans gave way to a wildflower patch, which then opened onto a small, circular lawn. But there was one path I never understood. It branched off from the main gravel walk, led confidently for about ten feet past the rhododendrons, and then simply… stopped. It didn't lead to a bench, a tool shed, or a prized rose. It just ended in a soft wall of ferns.
When I was old enough to help him weed, I asked him about it. He wiped his brow with a handkerchief and smiled. "Oh, that," he said. "Used to lead to the compost heap. Moved that years ago. The heap's over by the apple trees now. Better sun." I asked why he didn't just tear up the path, let the grass grow over. It seemed like a wasted effort to keep raking it clean. "Because," he said, as if it were the most obvious thing in the world, "it’s still a path. It just goes somewhere else now."
I think of that forgotten path every time I debate a redirect chain. In our world, a path that leads nowhere is a failure, a dead end to be ruthlessly pruned. We are taught to consolidate, to streamline, to point every single redirect directly to its final destination. Efficiency is our gospel. But my grandfather understood something about structure that we often forget: a path has a history, and that history has value.
That old garden path was a redirect. It didn't point to the compost heap's original location anymore; it pointed to its memory. By maintaining it, he wasn't confusing anyone. No one ever got lost looking for compost. Instead, he was acknowledging that the garden’s structure had evolved. The path was a artifact, a signpost to a past configuration. It said, "Things were once different here," and in doing so, it told a richer story about the whole.
Sometimes, in our rush to create the cleanest, most efficient site map, we are too quick to obliterate every trace of what came before. We set up a single 301 and call it a day. But what about the user who, for whatever reason, has that old, deep-linked path bookmarked? The redirect is a courtesy, a gentle guide to the new location. But the chain itself—the journey—can be a kind of narrative. It can soften the abruptness of change, providing context rather than just a destination.
My grandfather’s garden wasn’t just a collection of plants; it was a living document of his decades of work. The paths were its links. Some were strong and direct, the main navigational arteries. Others, like the one to the old compost, were like canonical tags pointing to a deprecated—but not erased—version of the garden’s story. They weren't inefficient. They were humane. They respected the past without living in it, allowing the garden, and anyone walking through it, to understand its growth. Not every redirect needs to be a shortcut. Some can afford to be the scenic route.
Notes & further reading
A few pages I came back to while writing this: