Information architecture: Everything in its place.

Website information architecture that holds up as content grows

Good website information architecture is the part nobody notices when it's right and everybody feels when it's wrong: the moment someone can't find the page they know must exist somewhere.

Structure before screens

We audit existing content, work out what it's actually for, and group it around the questions people arrive with rather than the org chart it was written under. That produces a sitemap, a navigation model and a content hierarchy — what sits at the top level, what's nested beneath it, and what gets cut because nobody was going to find it anyway.

Tested with real people

We start with a full content inventory, not a redesign brief: every page, what it's for, who links to it and how it's currently found. Card sorting and tree testing with real people check whether our proposed categories match how they'd actually go looking, rather than how the site's owners think about it internally. The result is a structure we can defend page by page, and one that holds up in use as well as it does on the diagram.

• Content inventories and audits
• Sitemaps and navigation models grounded in tree testing
• Taxonomy and content relationships
• Page purpose and hierarchy, decided before layout

Why menus get blamed unfairly

Navigation problems get blamed on visual design, but a confusing menu is usually a structural problem wearing a styling complaint. No amount of interface polish fixes a category that doesn't match how people think, or a page that's three clicks from where anyone would look for it. Get the structure right first and the interface work that follows gets easier and cheaper. A structure search engines can crawl cleanly matters as much as one people can navigate, which is where our SEO work picks up.

We build this alongside usability testing on the same projects, so a structure is checked against real tasks while it is still cheap to change. See Nielsen Norman Group on the difference between architecture and navigation, how card sorting works and what makes a sitemap usable.