The Cartographer's Eraser: On the Hubris of Planning the Perfect Sitemap

In our discipline, we have a fondness for the metaphor of the map. We talk of site structure as ‘architecture’ and ‘blueprints,’ and we speak of the sitemap—that tidy, hierarchical XML file—as the definitive guide to our territory. The prevailing wisdom is clear: a good site must begin with a well-planned sitemap. It is the foundational act, the cartographer’s first stroke on parchment, promising order and clarity from the outset. I’d like to gently, but firmly, push back against this foundationalist faith.

The assumption that we can, or should, plan the perfect navigation skeleton before we have truly walked the land is a kind of hubris. It presupposes that the relationships between ideas, the paths users will need, and the content’s own organic growth can be fully anticipated. We draft neat boxes for ‘Resources,’ ‘Insights,’ and ‘Support,’ only to find, six months later, that a crucial piece of content belongs squarely in the intersection of all three, a place our pristine map never allocated. The sitemap becomes a Procrustean bed, forcing living content to fit a predefined, static mold, often at the expense of intuitive sense.

The Map is Not the Territory

This is where the metaphor truly frays. A geographical map charts a landscape that changes on a scale of epochs. Our digital territories change on a scale of weeks. The ‘perfect’ initial sitemap is often rendered obsolete by the first successful blog series, the first unexpected user query pattern, or the first product pivot. Clinging to it then isn’t diligence; it’s an adherence to a plan that no longer reflects the reality of the place it supposedly describes.

The more vital, and more humble, tool is not the plan, but the audit. It is the willingness to erase. True structure emerges not from a grand, top-down design drafted in isolation, but from the slow accumulation of user journeys, from the internal links that naturally form between related pieces, and from the continuous, critical look at what is actually there versus what we thought would be. The skeletal structure should be a hypothesis, tested and reshaped by traffic and engagement, not a holy writ.

This isn’t a call for chaos. It is an argument for a different kind of rigour: the rigour of the gardener who prunes and trains based on how the plant grows, not merely on a sketch in a gardening book. Start with a simple, sensible, and flexible initial structure—a compass direction, not a detailed street plan. Then, use your internal linking strategy as your true surveying tool, drawing paths based on real use. Let your canonical tags and redirects be the careful annotations on a map you are constantly updating, correcting your earlier assumptions.

In the end, the most accurate map is the one that admits it is a draft, subject to revision. The quest for the perfect, pre-launch sitemap is often a displacement activity, a comforting illusion of control. The real work lies not in the pristine planning, but in the courageous, ongoing act of redrawing—with a well-used eraser close at hand.

Notes & further reading

A few pages I came back to while writing this: