The Janitor's Master Key: On Keeping the Unseen Corridors of a Site Open

It’s a common enough scene in old buildings. You turn a corner into a dim hallway and find a door that doesn’t seem to lead anywhere important. It’s unmarked, maybe a little dusty. Most visitors wouldn't give it a second glance. But to the janitor, that door is essential. It’s the access point to the pipes, the wiring, the structural beams—the things that make the building function but are never meant to be on display. This role, the caretaker of the unseen, is the one we play when we manage the labyrinth of internal redirects on a website.

Redirects are often discussed in terms of grand migrations: the moment you move your entire site to a new domain, the great consolidation of a rebrand. But what about the smaller, quieter shifts? The page you merged with another last year. The product you discontinued six months ago. The blog category you decided was too narrow and folded into a broader one. These actions create a network of silent corridors within your site. They are the 301 and 302 redirects that point not to the outside world, but inward, from one part of your own domain to another.

Like that unmarked door, their purpose isn't to be admired. Their success is measured by their invisibility. A user clicking an old bookmark, or a search engine bot following a years-old sitemap entry, should glide seamlessly from the outdated address to the current, relevant one. They should never hit a dead end, that chilling 404 error that whispers of neglect. The janitor’s job isn’t to build the grand new atrium; it’s to ensure that the service elevator still works, that the path to the basement boiler room remains clear.

The Weight of the Ring

This maintenance, however, comes with a hidden cost. Every redirect, no matter how small, adds a tiny amount of friction. It’s a micro-instruction that must be processed. A site with a sprawling, unmanaged web of internal redirects—layers of them, chaining from one URL to another to another—is like a building where you need three different keys and two separate codes just to get to the supply closet. The journey still works, but it’s slow. It’s inefficient. For a search engine, this ‘redirect chain’ dilutes the authority being passed from the old page to the new. For a user, it can mean a barely perceptible lag, a subtle erosion of the experience.

So the janitor must also be an archivist. The master key ring needs a meticulous log. Why does this redirect exist? When was it created? Is it still necessary? Sometimes, the answer is yes, indefinitely. A URL that was ever publicly shared is a promise, and that promise should be kept. But other times, a redirect is a temporary measure, a scaffold that was never taken down. Auditing this network, pruning the unnecessary hops, and shortening the chains is an act of housekeeping that preserves the structural integrity of the entire site.

It’s a humble discipline. There are no trophies for a perfectly maintained redirect map. The reward is the absence of trouble: the phone that doesn’t ring with a complaint, the analytics report that shows no mysterious dead-ends, the quiet confidence that the foundations, though unseen, are solid. It is the satisfaction of knowing that every corridor, even the ones long forgotten by the architects, remains open and functional for anyone, or anything, that might someday need to pass through.

Notes & further reading

A few pages I came back to while writing this: