The Homepage Is Where Old URLs Go to Die

Illustrative scenario. Records, events and arithmetic are constructed examples, not findings about a named organisation.

The redirect file sends 6,400 retired addresses to /. Every row passes the status-code check. An old link to a course application now opens a photograph of the campus.

The browser arrived. The applicant did not.

The old estate contains duplicates, expired services and pages nobody will claim. Launch cannot wait for every department to resolve its archive. A common destination avoids a dead address while the team settles the detail.

Having maintained public access through platform changes, supplier departures and successive rounds of content ownership that left the same pages in place under different managers, the delivery team considers continuity a duty rather than an item to discard for a cleaner release.

They kept the doors open.

A redirect plugin cannot decide whether a withdrawn qualification has a successor. Nor can an SEO checklist settle a policy question about an obsolete service. Those decisions need people with authority to make them.

You know the meeting: everyone agrees the old URLs matter, then assigns the work to whoever owns the website. That person owns the routing file. They do not own the institution’s decisions.

At an assumed three minutes per destination decision, 6,400 addresses require 320 hours. Leave the task until ten working days before launch and it requires four people working eight-hour days.

That allowance excludes consultation, implementation and testing. It is arithmetic for an illustrative workload, not an estimate derived from a client audit.

The shortcut has a staffing plan. Nobody approved it.

A single destination removes the visible queue by removing the distinctions the queue was meant to resolve.

After release, search traffic changes. An algorithm update offers a plausible explanation. Reporting periods differ; demand shifts; competitors publish. Search has enough moving parts to make attribution difficult.

The team can spend weeks comparing charts without confronting the file that maps an application page, a policy document and a retired staff profile to the same address.

The outside world is rarely short of suspects.

No.

Your redirect test checked arrival. It never checked where.

An old URL needs a disposition: a relevant replacement, a retained archive or an appropriate retirement response. The choice depends on the content and its use. A homepage cannot perform all three jobs.

Test destination meaning as well as the response chain. Sample actual journeys. Give unresolved addresses an owner and a decision date.

The receptionist praised for finding the right page is completing the routing you removed.

A successful response is not a successful answer.