Website Information Architecture Design
Information architecture (IA) is the skeleton of a site: how sections are organized, how pages are connected, what routes users take to reach needed content. Poor architecture is invisible to the eye, but it kills conversion — people simply can't find what they came for.
What's Included in IA Design
Work begins not with drawing diagrams, but with content inventory and understanding business goals. Typical process looks like:
- Content audit — compile complete registry of existing or planned pages, their types and relationships
- User task analysis — what exactly people search for on site, what words they use
- Grouping and hierarchy — card sorting or tree testing to verify grouping logic
- Site map building — visual diagram of all sections with nesting depth
- Taxonomy definition — categories, tags, filters for content sites and catalogs
Deep Dive: Card Sorting and Tree Testing
This is the most underestimated tool in design. Instead of guessing how users mentally group services or products, we conduct research directly.
Open card sorting — participant names groups themselves and arranges cards with page names. Tools: Maze, Optimal Workshop, UXtweak. Output is dendrogram — similarity matrix showing what users consistently place together.
Tree testing — inverse task: give ready navigation tree and ask to find specific things. Metrics: success rate, directness (found directly or wandering), time-on-task. If success rate below 70% on key tasks — architecture needs reworking.
Real example: for B2B logistics automation service, tree testing with 40 participants revealed "Integrations" section users looked for in four different places — in "Settings", "API", "Partners". Solution: duplicate entry points + section rename. Success rate grew from 52% to 84%.
Nesting Depth and Three-Click Rule
Three-click rule is popular myth. Real research (Nielsen Norman Group, 2014) shows: number of clicks itself doesn't affect satisfaction, path predictability matters. Users tolerate 5 clicks if each is obvious.
Nevertheless, practical guidelines:
| Site Type | Recommended Depth | Comment |
|---|---|---|
| Corporate site | 2–3 levels | More — content fragments to meaninglessness |
| E-commerce | 3–4 levels | Category → subcategory → product |
| News portal | 2–3 levels | Category → article, tags as flat navigation |
| SaaS product | 2–4 levels | Depends on feature count and user roles |
Artifacts We Deliver
After IA design client receives:
- Site map in FigJam or Miro format (interactive, with comments)
- Taxonomy as table: categories, subcategories, attributes
- Content matrix: what page types are needed, what fields and blocks on each
- Card sorting / tree testing report with data visualization and conclusions
Timeline
Information architecture design for typical corporate site (15–40 pages) — 5–10 working days. Large portal or SaaS with multiple user roles — 2–4 weeks including research.
Architecture is investment that pays off at development stage: more accurate IA means fewer reworking in code and content later.