Information Architecture: The Map Under Your Website

Glowing blue sitemap chart showing a website's pages connected by straight lines

Information Architecture: The Map Under Your Website

Part 7 of Build Wireframes and Low-Fidelity Prototypes — a series on the UX principles I use in client work.

A wireframe shows one screen. Information architecture shows how all the screens fit together. It is the map underneath the website: what content exists, how it groups, and what sits above what. It also sets the order a visitor moves through it. When visitors call a site “easy to use,” they usually mean they found what they wanted quickly. They did it without thinking about it. That feeling is not an accident. Instead, it comes from good information architecture, before anyone draws a single screen.

Think of it as a family tree for a website. At the top sits the homepage, the front door. Underneath it sit the main sections. Underneath each section sit its sub-pages. A festival site might have sections for schedule, tickets, parking, and about. Under tickets might sit single-day passes, weekend passes, and group rates. Under schedule might sit each day, and under each day, each stage. A church site might have sections for plan a visit, ministries, events, and giving. A nonprofit site might have sections for our work, donate, volunteer, and news. The shape is simple. The decisions inside it, however, are not.

Three ideas that build the map

Information architecture rests on three ideas. For that reason, I check every sitemap against all three before I draw a wireframe from it.

First, organization: how pieces of information connect to each other. Which things belong together? If a visitor looks for a ticket, where else might they want to go next? Parking, the schedule, or the lineup. A good map puts those things near each other. The sitemap should mirror how the visitor thinks, not how the organization arranges itself internally. As a result, one person can own the sitemap even when ten people own pieces of the content. The sitemap is the one place where the visitor’s view wins.

Second, hierarchy: what sits above what. The larger category goes on top, and more specific things sit below it. A page about the festival goes above the page about Saturday’s lineup. That page goes above the page about one band’s set time. Keep the hierarchy shallow enough that a visitor can hold it in their head. Three levels is plenty for most sites. A site that needs five has probably tried to say too much at once.

Third, sequence: the order of the journey

Some journeys are free: a visitor can browse a site’s stories in any order. Others, however, have a strict order. A donor chooses an amount, enters details, and confirms. A sitemap that respects sequence puts the steps in the order people actually take them. The wireframes that follow it inherit that order.

Why the map matters before the wireframe

A clear map makes wireframes clearer, and it makes everyone else’s job easier too. Stakeholders can look at a sitemap and judge the content. That includes the festival board, the church staff, and the nonprofit team. They can ask whether it is the right content, in the right places, to meet their goals. In fact, they do not need to read a design to do that. For example, in one picture, they can see the volunteer page hiding three levels deep. They can see the donate page with no parent except the homepage. And they can say so before anyone builds a screen.

A good map also leaves room to grow. Content always grows over time. A festival adds a stage, a church adds a ministry, a nonprofit adds a program. If you draw the map with no room for new sections, every addition becomes a hack. In other words, new items land in the wrong sections. Menus wrap awkwardly. Pages live nowhere sensible. A map you draw with growth in mind leaves room: one section can take a new child, and one grouping can stretch. So the site can grow without starting over.

Habits that keep a map honest

Here are the habits I lean on. Keep the number of choices small and well organized. Visitors do not actually want endless options. They want the right option, easy to spot. Do not surprise visitors with information they did not ask for in a place they did not expect it. Remember that the homepage is not the only front door. For instance, many visitors arrive through a search result, a shared link, or a social post. They land deep inside the site. So every page needs to orient a newcomer, not just the homepage. And on a phone, be ruthless about essentials. A small screen punishes a map that tried to include everything. So the mobile version of a map is often the truest test of whether the organization is sound.

The map is not glamorous. Still, nobody compliments a sitemap the way they compliment a homepage. But every wireframe that follows it inherits its strengths and its flaws. Draw the map first. Then argue about the map while it is still cheap to change. As a result, the wireframes that come after will almost draw themselves.

The next post is about the invisible rules that make those wireframes readable at a glance. It is about how our eyes group what they see.


Want your site’s structure sketched before it’s built? Shaun M. Johnson, owner of Signature Web Design is a full service Web designer, SEO, UI/UX, Graphic Design, and Logo and Branding Expert serving Goldsboro, Greenville, Kinston, Raleigh, Wilmington, Wilson and surrounding areas in North Carolina — with websites designed across the country. Get a free consultation or see recent work.

Previous in this series: Paper Wireframes · Next: Gestalt Principles: Why Visitors Group What They See



Ready to start your web design project?

Free consultations — with new pricing, non-profits & churches save 15%!