UX Glossary Information Architecture

Sitemap

Information Architecture

A hierarchical diagram showing all the pages or screens in a product and how they connect. Sitemaps help teams plan and communicate the structure of a site before design or development begins, and expose navigational gaps or unnecessary complexity.

Sitemap illustration
Source: picsum.photos

Common contexts

Use when

Build a sitemap at the start of any project involving more than twenty pages or screens, or any redesign where the current navigation structure is being reconsidered — it's the fastest way to make structural decisions visible before they become expensive to change.

Avoid when

Don't create a detailed sitemap for single-page applications or products with highly dynamic, user-generated content structures — a static hierarchy diagram misrepresents experiences whose structure is defined at runtime rather than by IA decisions.

A sitemap that everyone agrees on in a workshop often reveals the first round of real disagreements only when you start assigning actual content to it — the abstraction of boxes and arrows lets conflicting assumptions coexist until labels force a decision.

Real-world examples

Related terms

Information Architecture Navigation Content Hierarchy Wayfinding
← Browse all UX Glossary terms