The Stonemason's Uncarved Block: On the Deliberate Potential of the Reserved URL
I remember the first time I saw my grandfather’s workshop. It smelled of dust and damp stone. On a long, worn bench sat his current project, a half-finished angel for a local churchyard. But tucked away in the corner, almost out of sight, were the blocks. Raw, untouched slabs of limestone, their surfaces still rough from the quarry. They were waiting. He called them his ‘maybe’ stones. He hadn’t yet learned what they were meant to be, but he knew they were meant for something. He had reserved them, protecting their potential from being wasted on a lesser purpose.
That memory surfaced years later, not in a dusty workshop, but while staring at a spreadsheet of our site’s URL structure. We were planning a new section, a sprawling, multi-part project that would unfold over the better part of a year. The temptation, as it always is, was to build as we went. To create pages and URLs reactively, as the content was written. It’s the digital equivalent of grabbing whatever stone is handy and starting to chip away, hoping a form emerges.
But I thought of my grandfather’s ‘maybe’ stones. I thought of the deliberate act of reservation. So, we did something that felt strangely formal, almost ceremonial. We carved out a whole section of our URL namespace—/insights/season-one—and we reserved it. We placed a simple, elegant holding page there, not a cold 404, but a warm promise. “Something is coming,” it said. “We are building it for you.”
This act, the reservation of a URL path, is one of the most quietly profound practices in webcraft. It is not a redirect, which points elsewhere. It is not a canonical tag, which defers to another’s authority. It is the declaration of intent. It is a claim staked on a piece of digital territory not for what it is, but for what it will become. It protects the future from the haphazardness of the present.
Every time a user or a crawler visited that reserved space, they encountered that intent. They weren’t met with a dead end or a confusing redirect chain leading to a vaguely related article. They were met with a promise. In a world of instant gratification, it taught a small lesson in anticipation. More practically, it allowed us to internally link to the section long before it launched, building a scaffold of context and relevance that the future content would slot into perfectly, rather than forcing the new content to awkwardly backfill a poorly planned structure.
My grandfather never forced a shape onto his reserved blocks. He waited until he understood the stone, and the stone, in turn, suggested its form to him. Our reserved URL did the same. By holding the space empty, we gave the future content room to breathe and define itself on its own terms, ensuring that when it finally arrived, it felt inevitable, not improvised. It was the one thing my grandfather valued above all else in his workshop: the potential of the uncarved block.
Notes & further reading
A few pages I came back to while writing this: