Skip to content
Tutorials Center
My learning

Topics

Lesson 17 of 36 ยท Information Architecture

Site Maps and Navigation Patterns

Learn to draw a site map, choose a hierarchy with the right breadth and depth, pick navigation patterns for web and mobile, and test the structure with a tree test.

Once you know your content and how people group it, you need to draw the structure and decide how people will move through it. A site map (or sitemap, in the UX sense) is a diagram of the pages or screens of a product and how they relate. It is a planning tool for designers and developers, not the same as the XML sitemap used by search engines.

Drawing a site map

A site map is usually a tree. The home page is at the top; main sections branch below it; sub-sections and pages branch further.

flowchart TD
  H["Home"] --> A["Shop"]
  H --> B["Help"]
  H --> C["Account"]
  A --> A1["Shoes"]
  A --> A2["Clothing"]
  A1 --> A11["Running"]
  A1 --> A12["Hiking"]
  B --> B1["Returns"]
  B --> B2["Contact us"]
  C --> C1["Orders"]
  C --> C2["Settings"]

A hierarchy of three levels. Cross-links (not drawn) also connect pages, such as Returns from Orders.

Use boxes for pages, lines for parent-child relationships, and a different line style for cross-links. Number the pages if developers will refer to them.

Breadth and depth

A structure can be broad and shallow (many top-level choices, few levels) or narrow and deep (few choices per level, many levels). Research and experience suggest broad and shallow trees are often easier than deep ones, because each extra level is another chance to choose wrongly and backtrack. But too many items in one menu also hurts (see Hick's Law). Aim for a balance: group related items, keep labels distinct, and make important content reachable in about three clicks. The number three is a guideline; clear paths matter more than counting clicks.

Global navigation is the main menu, present on every page. Common forms:

  • Top horizontal bar: familiar on desktop; works for five to nine items.
  • Mega menu: a large panel for big sites, with grouped links.
  • Sidebar: good for tools and documentation with many sections.
  • Hamburger menu: hides navigation behind an icon; saves space but lowers discoverability.
  • Bottom tab bar (mobile): three to five main destinations within thumb reach; always visible.
  • Footer links: secondary and legal content.

Local navigation helps within a section (a sidebar of related pages). Contextual navigation appears inline: related articles, "next step" links. Utility navigation covers account, cart and search.

Other wayfinding aids:

  • Breadcrumbs show the path (Home > Shop > Shoes > Running) and let users go up.
  • Current-page highlighting shows where you are.
  • Clear page titles that match the link that led there.
  • Search as an escape from the hierarchy (see Labeling and Search).

Wayfinding questions

Where am I? Highlight and breadcrumbs
Where can I go? Clear menus and links
1 / 2

Mobile considerations

Small screens favor a short top-level list, a bottom tab bar for frequent destinations, and progressive disclosure for the rest. Do not hide the primary navigation behind several taps if users need it constantly. Test with real thumbs.

Tree testing

How do you know a structure works before you build it? Tree testing (also called reverse card sorting) shows participants only the text hierarchy, with no design, and asks them to find where they would look for something: "Where would you find the return policy?" It measures:

  • Success rate: did they end up in the right place?
  • Directness: did they get there without backtracking?
  • Time taken.

By removing visual design, it tests the structure and labels alone. Low-scoring tasks point to problems with categories or wording.

A stand-in: tree test scoring

This stand-in records where participants clicked for a task and calculates success and directness. The data is invented.

JS Tree test results (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Here 4 of 5 eventually succeed, but only 2 get there directly; the others wandered, which suggests labels or placement could be clearer.

Practical tips

  • Use plain, mutually exclusive category names. "Resources" and "Learning" invite confusion.
  • Avoid a "Miscellaneous" top-level bucket; it is a sign something is unorganized.
  • Keep navigation consistent across pages.
  • Let people reach important items from more than one place.
  • Revisit structure as content grows.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a site map in UX?

    It plans structure for the team; the XML sitemap for search engines is a different thing.
  2. 2. What does a breadcrumb trail do?

    Breadcrumbs support wayfinding in hierarchies.
  3. 3. What does tree testing evaluate?

    Participants navigate a text-only tree to find items.
  4. 4. What is a downside of hiding navigation in a hamburger menu?

    What is out of sight is used less.

Summary

  • A site map is a tree diagram of pages and their relationships.
  • Balance breadth and depth; broad and shallow often beats deep.
  • Use global, local, contextual and utility navigation, with breadcrumbs and clear highlighting.
  • On mobile, favor a short list or bottom tab bar.
  • Validate with tree tests: success, directness and time.

Next: Labeling and Search Design