Information architecture and navigation

0:00 Information architecture and navigation

Here's a real conversation that happens every week in small agencies. A prospect emails: what do you charge? And someone replies, it's on the website, under Investment. The prospect never found it. Not because they're lazy, but because nobody calls prices investment except the agency. That's an information architecture problem. In this lecture, you'll learn what information architecture is, how to label navigation in your users' words, how card sorting and tree testing work, and how to structure landing pages and multilingual sites so people find what they need in one or two taps.

0:41 What IA is

Information architecture, or IA, is the structure and labeling of content so people can find what they need and understand where they are. It has five parts. Organization: how content is grouped, by service, audience or task. Labeling: what groups and links are called. Navigation: how people move around, with header menus, footers and breadcrumbs. Search: finding things by typing. And hierarchy: the levels, like home, then services, then one service. Poor IA shows up as high bounce rates, lots of support questions the website already answers, and prospects who say they couldn't find your prices.

1:23 The supermarket analogy

Here's an analogy. Think about a supermarket. You walk in wanting rice. You don't know the store, but you find it in under a minute. Why? Clear signs above the aisles, in words you use, like rice and pasta, not carbohydrate solutions. Related things are grouped together. And the layout is similar to other supermarkets you've visited. A website works the same way. Clear signs are your navigation labels. Grouping is your organization. And familiarity is following conventions people already know, like pricing in the header and contact at the end.

2:03 Labels in users' words

Labels are one of the biggest findability factors. Use the words your users use, from interviews, search queries and support tickets. Not internal jargon. Not clever branding. Solutions becomes Services. Investment becomes Pricing. Our Journey becomes About us. Resources Hub becomes Guides or Blog. Connect becomes Contact. Creative language can live in your content and headlines. But your navigation is a sign system, and signs must be instantly clear. For small business sites, four to seven top-level items is a common, manageable range, with the most important tasks first and one primary call to action in the header.

2:46 Card sorting and tree testing

How do you know how users group things? Card sorting. In an open card sort, people group topics and name the groups themselves. That reveals their mental model and their words. In a closed card sort, they place topics into categories you've already defined, which tests your structure. Then there's tree testing. You show a text-only menu, no visual design, and give tasks like, you want to know what a new logo would cost, where would you click? If people can find it in the bare tree, your structure works. If not, no amount of visual polish will save it.

3:29 Worked example 1: agency menu

Worked example one, simple. An agency website has nine menu items with creative labels: The Lab, Our DNA, Let's Talk Magic. Prospects can't find pricing or examples. The team reviews site search terms and sales call questions, and people keep saying price, cost, examples and portfolio. So they run an open card sort with eight clients, then tree-test a new structure. Services. Work. Pricing. About. Blog. Plus a Book a call button. And case studies filterable by industry. Over the next quarter, more visitors reach pricing and case studies, and the what do you charge emails drop.

4:11 Worked example 2: bilingual retailer (illustrative)

Worked example two, a business scenario with illustrative numbers. A furniture retailer in Dubai runs its site in English and Arabic. Arabic visitors browse fewer pages and use site search far more. A tree test with six Arabic-speaking customers reveals why. The Arabic menu was a literal translation, with categories organized differently from the English site, and the language switcher was a tiny flag icon. The fixes: an Arabic structure mirrored for right to left reading, category names chosen by Arabic-speaking customers, identical structure across both languages, and a switcher labeled in each language's own script.

4:53 Watch me do it: label test

Watch me do it. First I collect words. In GA4, I check site search terms, and I pull the top questions from sales calls. Then I write two candidate structures in a spreadsheet. Next, a quick tree test with five people over video. I show only the text menu and give three tasks that don't reuse the menu words. For each task I record the first click, the final answer, and whether it was right. Task one, find logo pricing: two out of five succeed. That's a fail. I rename Investment to Pricing and re-test that one task. Five out of five.

5:37 Two special cases

Two special cases. First, campaign landing pages. Many remove or reduce the main navigation to keep focus on one goal. That can help conversion, but keep essentials: the logo link, a minimal footer, and access to pricing, privacy and contact information so trust doesn't suffer. Second, multilingual sites. Provide an obvious language switcher with language names in their own script, mirror layouts for right to left languages, and keep the same structure across languages so people can switch without getting lost. And a bonus: clear labels and descriptive page titles also help search engines and AI answer engines understand your pages.

6:21 Mobile navigation

A quick word on mobile navigation, because that's where most social traffic lands. The menu usually collapses behind an icon. Make sure that icon is recognizable, and consider adding the word menu next to it. Keep your primary call to action visible outside the menu, like a book a call button in the header, so people don't have to hunt for it. Put the most common tasks first inside the menu. Use breadcrumbs on deeper sites like shops and help centers. And add site search once you have a big content library. Then test it on a real phone, with your thumb, not a mouse.

7:07 Common mistakes and measures

Common mistakes. Clever labels that hide meaning. Too many top-level items. Organizing by your internal team structure, like marketing department pages, instead of by user tasks. Hiding essential information in footers or PDFs. And skipping validation, because the structure seems obvious to the team. Remember, you're not your user. How do you measure success? Tree-test success rates. More homepage visitors reaching key pages like pricing and case studies. Less site search for things that are already in the menu. And fewer where can I find your prices questions.

7:45 Recap and try this now

Let's recap. Information architecture is how content is organized and labeled so people can find it. Use your users' words for labels, keep navigation shallow and focused, validate structures with card sorts and tree tests, and handle landing pages and multilingual sites deliberately. Try this now. Draw a simple sitemap for your website or a client's. Rewrite any unclear navigation labels using words from real customer messages and search terms. Then ask three people to find two items using only the text menu, and record how many succeed on the first try.