The Kitchen Spice Rack: On the Practical Alphabet of Your Site Structure
I was looking for cumin the other night. It should have been simple. My kitchen, like many, is organized around a spinning carousel of spices, a miniature tower of flavors. But the cumin was not between curry powder and dill. It wasn't behind the paprika or in front of the oregano. After a minor panic, I found it. Someone, in a well-intentioned but disastrous act of reorganization, had placed it next to cinnamon. Alphabetical order, they explained. It made perfect sense on paper. On my tongue, in the context of the chili I was making, it was chaos.
This is the quiet tragedy and triumph of the spice rack, and it’s a near-perfect metaphor for the way we organize our websites. We are so often seduced by the clean logic of an external system—like the alphabet—that we ignore the internal logic of use. Alphabetizing a spice rack feels satisfyingly systematic, a victory of order over entropy. But it separates salt from pepper, it divorces the three different kinds of chili powder, and it forces thyme and rosemary, siblings in a thousand recipes, to opposite ends of the carousel. The system is legible to a stranger but inefficient for the cook.
A URL structure built solely on the strict, brittle logic of a corporate directory—/about/team/leadership/chief-executive-officer—is the digital equivalent of this alphabetic spice rack. It looks organized. It is, in a sterile, conceptual way, correct. But it fails its primary user: the person who has come to your site with a question, a need, an intent. They don't think in org charts; they think in tasks and solutions. They aren't looking for the "Chief Executive Officer"; they are looking for "who is in charge" or "our company's story." When your site's navigation mirrors your internal hierarchy instead of your visitor's mental model, you’ve put the cumin next to the cinnamon.
A Structure of Scent and Taste
The best spice racks are organized by culinary relationship. All the Italian herbs live together. The baking spices—cinnamon, nutmeg, cloves—form their own cluster. Hot spices are grouped, and the foundational staples like salt and pepper are within effortless reach. This is a structure built from the inside out, shaped by the work it supports. It is a practical alphabet, one where ‘S’ for savory and ‘S’ for sweet are more important than ‘S’ for sage.
Applying this to a website means letting user journeys and semantic relationships dictate your URL paths and internal linking. A page about "Installing Wood Floors" should not be buried under /products/hardwood/installation/. It should be part of a cluster that includes "Wood Floor Care," "Best Finishes for Pets," and "Comparing Hardwood vs. Laminate." These are the flavors that belong together. Your internal links are the gestures that reinforce these relationships, creating a scent trail of relevance that guides a visitor from one logical step to the next, not from one letter of the corporate alphabet to another.
In the end, a spice rack, like a URL structure, is not a filing cabinet. It is a tool for creation. Its primary purpose is not to be perfectly indexed for an auditor, but to enable the cook to build a meal without friction. When your site’s structure is built on the logic of use, you stop asking, "Where does this page belong in our sitemap?" and start asking, "Where will our visitor need to go next?" You trade the false comfort of an external system for the genuine utility of an internal one. You put the cumin where it belongs: right next to the chili powder.
Notes & further reading
A few pages I came back to while writing this: