The Roman Milestone: On the First Static Path and the Imperative of Place
Before there was a canonical link, there was a canonical road. Before a 301 redirect, there was a legio marching to a new, permanent fort. Our modern web, with its intricate structure of paths and pointers, often feels like a uniquely digital invention. But its deepest principles—the need for stable, reliable, and well-signposted routes—are ancient. To find their purest expression, we must look not to a library or a cartographer, but to a Roman engineer standing beside the Via Appia.
The Roman road system was the internet of its age, a network designed for the rapid, reliable transmission of information and force. Its genius wasn't just in its physical construction, but in its information architecture. At regular intervals, the engineers placed milestones—miliaria. These were not mere distance markers. They were the original static URLs. A milestone did not simply say "50 miles"; it declared "50 miles to Rome." It was an absolute path, a fixed point of reference in a changing landscape. The path to the capital was immutable. The terrain around it could flood, a village could be abandoned, a new market town could spring up, but the path and its definitive endpoint remained.
This is the very essence of a well-structured URL. It is a promise of place. A user (or a legionary) trusts that following this precise path will lead them to the intended destination, every time. The Roman state understood that the integrity of the network depended on the unwavering stability of these signposts. To alter a milestone capriciously would be to introduce chaos, to misdirect armies and misinform citizens. It would break the trust the entire system was built upon.
So what happened when the destination itself had to move? Imagine a major administrative center, a regional capital, being decommissioned and its functions moved to a new, better-located city. The Roman solution was not to scratch out the old name on the milestone and write in the new one. That would have invalidated every previous inscription and created confusion. Instead, they built a new road to the new city and erected new milestones pointing the way. The old road, while perhaps less traveled, remained, its markers now serving as a historical record—a 410 Gone, if you will.
This ancient practice speaks directly to our work with site migrations and redirects. The modern temptation is often to simply repurpose the old path, to force the new content into the old URL, breaking the original promise that path made. The Roman model teaches a better way: honor the original path. If the destination must permanently move, build a new, dedicated path to it (the new URL) and use a redirect—the digital equivalent of a signpost saying "New Capital, This Way ➡️"—to gracefully guide travelers from the old, respected road to the new one. This maintains the integrity of both the old signpost and the new destination. It is an act of respect for the user’s expectation and for the structure of the system itself. We are still laying down roads, still carving milestones. The medium has changed, but the imperative of place remains.
Notes & further reading
A few pages I came back to while writing this:
- Hampton, VA
- The Lost City of Alexandria: On the Unmade Decision and the Redirect Chain
- Newport News, VA
- The Unspoken Guest: On the Etiquette of the Unlinked URL
- Norfolk, VA
- The Ship of Theseus and the Ever-Changing URL
- Richmond, VA
- Virginia Beach, VA
- Bellevue, WA
- Kent, WA
- Spokane, WA
- Tacoma, WA
- Vancouver, WA