The Tinker's Adjustable Spanner: On the Precise Fit of a Crawl
My grandfather kept a leather roll of tools in his shed, each one worn smooth by purpose. Among them, his favorite was an ancient adjustable spanner. It wasn’t the tool for every job, he’d say, but for the ones that mattered—the ones where the standard wrench wouldn’t fit. The artistry wasn’t in having a thousand wrenches, but in knowing exactly how to turn that one threaded jaw until it gripped the nut perfectly, without stripping it. That memory came back to me this week, while thinking about how we direct the attention of search engine crawlers across a vast and varied site.
We often talk about ‘crawl budget’ as if it’s a simple allowance to be spent, a bucket of water to be poured. But the tinker’s lesson suggests something else: it’s about precision of application. A crawler’s attention is not just a volume; it’s a force. And like that adjustable spanner, its grip needs to be calibrated to the task. Applying the full, blunt force of a crawler to every corner of a site—from the deep, dynamic catalog to the stable, timeless ‘about’ page—is like using a sledgehammer on a watch. You’ll make an impression, but you’ll break the mechanism.
The Calibration of Attention
The tinker’s first move was always assessment. He’d eye the nut, feel its edges, and only then begin to adjust the tool. Our parallel is in reading a site’s architecture before we ever touch a robots.txt or sitemap.xml file. Which sections are the high-priority, fast-changing ‘nuts’ that need a firm, regular grip? These are your news feeds, product listings, inventory updates—the parts that must be turned often to keep the machine running. They need a crawl setting that is frequent and firm.
Then there are the older, painted-shut fixtures—the legacy policy pages, the archived announcements from a decade ago. The tinker would know these need a different touch, perhaps just a check for integrity now and then. By signaling crawl delays, or using careful ‘noindex’ tags on truly irrelevant archives, we’re not wasting the crawler’s time. We’re adjusting its jaw to avoid a fruitless, grinding strain on parts that don’t need to move. We prevent the stripping of threads.
This is where the sitemap ceases to be just a list and becomes a set of specifications for the tool. It’s not about declaring everything exists; it’s about indicating the precise order and frequency for engagement. It tells the crawler, “Start with this, then move to that, and apply this much pressure here.” The priority tags and change frequencies are the micrometer marks on the spanner’s adjuster wheel.
The final lesson is in the feel. My grandfather could tell by the resistance in his wrist if the grip was true. For us, that feel comes from server logs and crawl reports. Watching where the crawler lingers, where it slips, and where it meets solid resistance tells us if our calibration is correct. It’s a continuous, quiet adjustment—a quarter-turn here, a slight loosening there—to ensure the force of discovery is applied exactly where it can do the most good, without wasting energy or damaging the delicate parts. It’s not about forcing discovery, but fitting the crawl to the contours of the site itself.
Notes & further reading
A few pages I came back to while writing this:
- Surprise, AZ
- The Archivist's Whisper: On the Quiet Power of the robots.txt
- Elk Grove, CA
- The Hearth-Tender's First Ember: On the Warmth That Draws the Crawl
- Pasadena, CA
- The Navigator and the Dredge: Two Ways of Seeing a Website
- New Haven, CT
- Stamford, CT
- Washington, DC
- one area's overview
- a practical rundown
- Little Rock, AR
- Gilbert, AZ