The Librarian's Unwritten Rule: On the Deliberate Tyranny of the Absolute Path
There is a piece of advice so common in our craft that it has ossified into unquestioned law: always use absolute URLs. From the root domain down to the final slash, we are told to inscribe the full, canonical address on every internal link and canonical tag. The reasoning is sound, we’re assured. It prevents ambiguity for crawlers, ensures consistency across domains and subdomains, and acts as a bulwark against content being scraped and misrepresented. It is the mark of a professional. But I want to question this absolutism. I want to make a case for the humble, the local, the deliberately myopic relative path.
The argument for the absolute path is, at its core, an argument for control. It is the librarian who insists every book must not only have a call number but must also bear the full, formal address of the library itself, stamped on every page. It creates a world that is perpetually self-referential, forever pointing back to its own complete, formal identity. This is a world without a local context, a place where no page can simply be a neighbor to another; each must always be a citizen of the entire domain, first and foremost.
But what of the spirit of the thing? A website is not merely a collection of individual documents existing in a void; it is a structure, an ecosystem. The relationships between pages—the parent, the child, the sibling—are the architecture itself. A relative path honors this architecture. It says, “from here, the next step is there.” It is a instruction based on current location, a native’s knowledge of the local paths. It acknowledges the structure as a lived-in space, not just a formal index.
The tyranny of the absolute path forces a kind of provincialism onto the site. It makes the content rigid and less portable. Want to stage the site on a development subdomain? Every single absolute link now points to production, a potential disaster. Need to restructure or migrate? The absolute path, in its stubborn specificity, can become an anchor rather than a guide. The relative path, by contrast, is adaptable. It understands its place within a hierarchy and moves with it. It is the difference between having a map that only works if you are standing at one specific spot on the globe, versus a map that orientates itself based on where you are now.
This is not a call for anarchy. Canonical tags, without question, should be absolute. They are the formal declaration of a page’s singular, universal identity to the outside world. But for the quiet, internal conversations between pages—the very sinews that bind a site together—the relative path offers a graceful, structural integrity that the absolute path simply smothers. It is the difference between building a community where everyone knows each other by their full government name at all times, and one where a simple, contextual nod is enough. Sometimes, the most powerful link is the one that knows exactly where it is.
Notes & further reading
A few pages I came back to while writing this: