Start with what your users actually need to find

Information architecture is the structure you build so people can find what they need on your site. You start by learning what your users are looking for, then organize your content to match those needs instead of organizing it the way you think makes sense.

Most sites fail at this because they organize around how the business is structured — separate sections for sales, support, legal — instead of around what visitors actually want to do. A visitor looking for a refund doesn't care that refunds are handled by the customer service department. They just want to find the refund process.

The first step is to stop guessing. Talk to real people who use your site or would use it. Ask them what they came looking for, what they expected to find, and where they looked first. Write down the words they use. This becomes the foundation of everything that follows.

Key Takeaways

  • Interview actual users about what they search for and where they expect to find it, then use their language in your navigation and labels.
  • Create a content inventory listing every page, document, and tool on your site so you can see what you actually have before you organize it.
  • Run a card sort exercise where users group content into categories the way they would naturally organize it, not the way your business does.
  • Build a sitemap that shows the hierarchy and relationships between pages, then test it with users before you build the navigation.
  • Use consistent naming and labeling across your entire site so users can predict where to find things based on what they learned elsewhere.

Interview users about how they search and think

Sit down with five to ten people who represent your actual audience. Don't ask them to evaluate your current site. Instead, ask them what they came to do, what words they would use to search for it, and what they expected to find.

If you run a software company, ask a customer: "You need to change your billing address. Where would you look first?" Listen to where they point and what they call that section. If they say "account settings" but you call it "user preferences," you have a labeling problem.

Write down the exact words people use. If three users call something "invoices" and two call it "receipts," you now know that labeling matters and that you may need both terms visible or searchable. This vocabulary becomes your navigation labels, your page titles, and your link text.

Create a complete inventory of what you have

Before you can organize anything, you need to know what exists. Make a spreadsheet with every page, document, tool, and form on your site. Include the current URL, the page title, what it's for, and where it currently lives in your navigation.

This inventory reveals duplicates you didn't know about, orphaned pages nobody can find, and content that belongs in multiple places. You'll find the FAQ page that answers the same questions as the support documentation, or the three different contact forms scattered across your site.

As you build this list, you'll also spot gaps — things users need that don't exist yet. A software company might discover they have documentation for every feature but no page explaining which plan includes which features. That gap becomes a new page you need to create.

Run a card sort to see how users group content

A card sort is a simple exercise where you write each piece of content on a card, hand them to a user, and ask them to group related items together and name each group. You're not testing whether they organize it your way. You're learning how they naturally think about your content.

You can do this in person with index cards or use online tools like Optimal Workshop or UserTesting that run card sorts remotely. Run it with at least fifteen to twenty users so you see patterns instead of individual quirks.

The results show you which content belongs together, what users expect to find near each other, and what names they would give to each section. If most users group "pricing," "plans," and "features" together but your site has them in three separate places, that's a structural problem you now know how to fix.

Build a sitemap that shows the hierarchy

A sitemap is a diagram showing how pages relate to each other and how deep users have to click to reach them. It's not the XML file search engines use — it's a visual map of your structure.

Start at the top with your homepage, then show the main sections below it. Under each section, show the pages that belong there. A typical structure might be: Homepage → Products → Product Category → Individual Product Page. Or: Homepage → Support → Documentation → Article.

The depth matters. If users have to click more than three times to reach something important, they'll get lost or give up. If your most-visited pages are buried four or five clicks deep, you have a structure problem.

Draw this out on paper or use a tool like Lucidchart, Miro, or even Google Drawings. The goal is to see the whole structure at once and spot problems before you build the navigation.

Test your structure with real users before you build

Once you have a sitemap, test it. Show the structure to five to ten users and ask them to find specific things. "You want to download our mobile app. Where would you look?" Watch where they click and whether they find it.

If most users look in the wrong place, your structure isn't matching how they think. You might need to move that section, add a link from somewhere else, or change the name so it's more obvious.

This testing is cheap and fast when you do it on paper or a wireframe. It's expensive and painful when you discover the problem after you've built and launched the site. Test before you code.

Use consistent naming so users can predict where things are

Once you've decided on your structure and labels, use them consistently everywhere. If you call one section "Resources," don't call another section "Tools" when they serve the same purpose. If you label something "get your free guide," don't label a similar page "Onboarding."

Create a style guide or naming convention document that lists all your main sections, what they contain, and what they're called. Share it with everyone who writes for your site. This prevents the slow drift where one person calls something "Help" and another calls it "Support."

Consistency teaches users how your site works. Once they learn that "Documentation" means written guides and "Tutorials" means videos, they can predict where to find new content without having to search.

Frequently Asked Questions

How many users do I need to interview to get useful information?

Five to ten users for initial interviews usually reveals the main patterns. For a card sort, run it with fifteen to twenty people so you see which groupings are common versus individual preferences. More is better, but even a small group of real users beats guessing.

What if my site is very large with hundreds of pages?

Start with your most-visited pages and the tasks users come to do most often. Organize those well first. You can always add more detailed structure for less-visited content later. A clear path to the things people actually need beats a perfect structure for everything.

Do I need special tools to do information architecture?

No. You can do card sorts with index cards and a table. You can draw sitemaps on paper or in free tools like Google Drawings. The thinking matters more than the tool. Start simple and upgrade tools only if you need features your current tool doesn't have.

How do I know if my information architecture is working?

Watch where users click and what they search for. If most people find what they need in two or three clicks, your structure is working. If they search for something that's already on your site, your labeling or navigation isn't clear enough. Use analytics and user testing to spot these problems.

Should I reorganize my site if I already have one built?

Test your current structure with users first. If they're finding what they need, leave it alone. If they're consistently looking in the wrong places or using search to find things that should be obvious, reorganization will help. Plan the change carefully so you don't break old links that people might have bookmarked.