Information Architecture for Small Business Websites

Most small business websites have a design problem that is not actually a design problem. The colours are fine. The logo is fine. The issue is that visitors cannot find what they came for, and they leave. Information architecture is the discipline of organising content so that the right person finds the right thing with the least friction. It is unglamorous work, and it is usually where the difference between a site that converts and one that does not is made.

Start with your visitors, not your org chart ¶

The most common structural mistake is organising a site around how the business is internally structured rather than how a visitor thinks about their problem. A law firm might have departments called Corporate, Litigation, and Employment. A potential client is thinking: 'I need help with a contract dispute.' Those two ways of organising information do not map neatly onto each other.

The fix is to start with the questions your visitors are actually asking when they arrive, and build the navigation around the answers to those questions. This usually means fewer top-level navigation items, not more.

The three-click rule is wrong, but the instinct behind it is right ¶

You may have heard that users should be able to reach any page within three clicks. The research behind this is thin, and the rule is not worth following literally. What is worth following is the instinct: every additional step between a visitor and the information they need is a point at which they might leave.

For most small business sites, the practical implication is that the contact page, the pricing page, and the most important service or product page should all be reachable from the homepage without scrolling. If a visitor has to hunt for how to get in touch, some of them will not bother.

How we map a site before designing it ¶

Our standard process starts with a content inventory: a spreadsheet listing every page that exists or needs to exist, what its purpose is, and who it is primarily for. From that inventory we build a sitemap, then a set of user journey maps showing how each visitor type moves through the site.

The sitemap goes through at least one round of card-sorting with real users before we treat it as final. Card-sorting is a simple exercise: you write each page name on a card and ask participants to group them in a way that makes sense to them. The groupings that emerge are usually different from what the client expected, and almost always more useful.

• List every page before you design any of them
• Group pages by visitor type, not by internal department
• Test the navigation with people who do not work at your company
• Keep the top-level navigation to five items or fewer

Structure is the part of a website that visitors never consciously notice when it is working. They only notice it when it is not. Getting it right before the visual design starts is the single most reliable way to avoid a rebuild eighteen months later.