The Stonemason's Spare Trowel: On the Tools We Keep Handy for the Wall

There’s an old photograph I once saw of a stonemason at work on a cathedral. His focus is on the great wall before him, but tucked into his belt, almost out of frame, is a second trowel. It’s not the primary tool, not the one laying the mortar that day, but it’s there. Clean, oiled, ready. It’s the spare. The one you don’t think about until the first one fails, or the mix changes consistency, or a tricky corner demands a different angle of attack. That second trowel isn’t part of the grand design of the cathedral, but it is an essential part of the building’s reality.

In the architecture of the web, our sitemaps are the grand designs. They are the blueprints we present to the search engine’s crawlers, the formal invitations that say, ‘Here is the cathedral. Here are the naves, the chapels, the spires. Please, come and see.’ We meticulously list every page we deem important, every URL we want discovered and indexed. It’s a conscious act of presentation, a tidy and organized view of our domain. It’s the primary trowel, the one we expect to do all the work.

But discovery, true discovery, is often a messy affair. It doesn’t always follow the blueprint. Crawlers are curious creatures, and they find their way through the mortar between the stones—the links. This network of internal linking is the stonemason’s spare trowel. It’s the secondary, often overlooked system that gets the real work done when the formal plan meets the unpredictable reality of the build.

Think of a page deep within your site, one you might have forgotten to include in the latest sitemap.xml submission. Perhaps it’s an old but evergreen article, or a utility page not deemed ‘important’ enough for the main index. If it has no links pointing to it, it’s like a stone sealed behind a wall. The sitemap crawler may never find it, and the ‘discovery’ crawler, which follows links, has no path to follow. It remains in the dark, a finished room with no door.

Conversely, a well-placed link from a high-traffic page acts like that spare trowel, expertly applied. It can guide a crawler to a section of the site the sitemap might have underrepresented, or to a new piece of content faster than you could ever ping the search engine with an update. The link is the tool of adaptability. It says, ‘The blueprint is a guide, but the real structure is built right here, in the connections.’ It’s how pages get found in the wild, not just in the archive.

Relying solely on a sitemap is like a stonemason refusing to use anything but his primary trowel. It might work for the broad, straight sections, but it will fail at the delicate arches and the intricate corbels. A robust internal link architecture is the spare tool that ensures no part of your construction is left inaccessible. It’s the acknowledgement that while we design with blueprints, we build with the tools we keep handy—and sometimes, the most important one isn’t the one in your hand, but the one waiting patiently in your belt, ready to ensure the wall gets built, connection by connection.

Notes & further reading

A few pages I came back to while writing this: