Press enter to see results or esc to cancel.

Information Architecture Made Easy With 3 Example Sitemaps

Information Architecture might sound big and confusing, but it’s really just organising information in a logical way so that people can find their way around and get what they need.

Striding through the supermarket the other day, I could glance at the signs for each aisle, read the 4-5 categories for each, and easily skip the aisles with things I didn’t need, and quickly find the things I did.

When planning a website’s information architecture I like to start by making a quick sitemap and then think about how it meets the users needs, the business goals, and how search-engine friendly it is.

  • Users

    Some research may need to go into understanding what users do on your website before “converting” to a lead/sale. For most businesses there will be smaller steps on the way to converting that need to be right to build trust and sell the value that your website provides.

    Information Architecture is NOT just about displaying your information in an order that you think is logical. Be sure to flip your thinking around. It’s about helping your website visitors easily get what they want. Talk to your target market, find out what they want, look at trends and data, find out how they will use your website.

  • Business Goals

    While you are planning out your website’s information architecture, stop a couple of times and check that it still lines up with your main business goal (i.e. lead generation for a builder’s website).

  • Search Engine Friendly

    When undertaking a new website project you may want to consider where any extra-for-SEO pages might fit into your information architecture, but beware of biting off more than you can chew, as a sitemap can easily add to the project scope. Start small, perhaps with 2 keyword-focused landing pages rather than 10, depending on your resources.

A Few Case Studies

Here’s a few example sitemaps which comparing the information architecture of websites that sell services, experiences, and products.

1. Websites that sell services

Typically businesses that sell their time will have similar information architecture for their websites. In this category I’m lumping together tradesmen along with professional services like accountants/lawyers/ consultants, etc. A service sold as $ per hour, or fixed price based on the approximate value of $ per hour.

Business Goal: Generate leads – phone or contact form enquiries

User actions: Check credibility, review pricing and previous work, make contact

Search engine goals: To rank for niche keywords, often location-based.

information architecture

View Complete Sitemap

2. Websites that sell experiences

Think restaurants, bars, mini golf, ten pin bowling, etc. A business that sells an experience, typically with a local focus.

Business Goal: Generate bookings/reservations or in-the-door traffic

User Actions: Find experiences (menu, activities) and pricing. Make a booking/reservation, or simply find opening hours and directions

Search engine goals: To rank for niche keywords, often location-based.

Information architecture

View Complete Sitemap

3. Websites that sell products

Here we’re looking at e-commerce websites. These are typically product categories, each with sub-categories, and possibly dynamic filtering to finish. On a Shoe store, this might look like first level categories being Women, Men, Children.

If you went into the Women category you would then find Heels, Flats, Sandals, etc. Dynamic filtering could further enable you to sort by factors such as Price and Brand.

Business Goal: Make product sales, repeat customers

User Actions: Find what they want, gather information, checkout

Search engine goals: To rank for all keywords in product range, with a focus on highly searched products

The information architecture and categories on your e-commerce site just needs to make sense to your shoppers so that they can easily find what they are looking for.

information architecture

View Complete Sitemap

When planning your website, be sure to consider the information architecture before diving into page-level content. Feel free to check out one of our ‘Complete Sitemap’ examples to get an idea of how to lay out a simple sitemap.