b2KIT

Site Architecture Planner

Plan website information architecture with a drag-and-drop tree builder. Visualize URL hierarchy, silo structure, and navigation depth.

Tested tool guide Tested browser tools Checked August 16, 2026

What Site Architecture Planner does, with a checked example

Site architecture usually lives in a spreadsheet where indentation is the only hint of hierarchy, and nobody notices the deepest page sits five levels down until the site is live. This tool replaces the spreadsheet with a visual tree: you add pages as nodes, drag them into parent-child relationships, and the site's structure becomes something you can see, rearrange, and judge. The thing most people get wrong is how fast depth accumulates: a product nested under a category under a section is already three clicks from home, and depth is exactly what this tool makes visible.

Worked example

A concrete input and expected output from the current implementation.

Input

Pages added as nodes: Home, Services, Website Design, Case Studies, About, Contact. Dragged into this arrangement: Services, About, and Contact under Home; Website Design under Services; Case Studies under Website Design.

Expected output

A rendered tree of six pages in four levels. About, Contact, and Services sit one click below Home, Website Design two clicks below Home, and Case Studies three clicks below Home, the deepest node in the tree.

Each parent-child edge adds one click of distance from Home, so Case Studies inherits Website Design's depth plus one. The output is the hierarchy exactly as arranged, with depth following mechanically from the nesting the user drew.

How the result is produced

1

Building the tree

Pages are added as nodes, then dragged onto other nodes to form parent-child edges. The result is a rooted tree: every node except the root has exactly one parent, so there is never ambiguity about which section a page belongs to. Re-parenting a node takes its whole subtree with it, and deleting a node removes its children as well.

2

Depth and silo membership

Each page's depth is the number of edges between it and the root, recomputed as the tree changes, so dragging a page deeper visibly increases its click distance and the distance of everything below it. A page's silo is the top-level branch it hangs under; pages in the same branch share a silo, which keeps topical grouping readable at a glance.

Good uses

  • Planning a new site before any URLs exist: lay out every intended page, then check that no content sits more than two or three clicks from home while rearranging still costs nothing.
  • Planning SEO content silos: group each topic's pages under one top-level section and confirm the tree keeps related pages in a single branch rather than scattering them across sections.
  • Auditing an existing site: transcribe the live sitemap's URLs as nodes to see the depth and grouping the site actually has, and keep the tree as the before-picture for a restructure.

Limits and checks

  • The tree is a plan, not the live site. It shows only pages someone entered, so it goes stale when the real site gains pages, redirects, or dynamic URLs. Depth here is planned depth, not what a visitor will actually experience.
  • The same pages can be drawn many ways. Nesting is a judgment call and the depth follows the drawing: two equally reasonable arrangements of the same content can differ by two levels. The tool shows consequences, not the correct structure.
  • A tree allows one parent per page. A product that legitimately belongs in two categories, or an article in two sections, must be placed in exactly one branch, and that single-parent shape can hide real cross-linking the finished site will have.

Common questions

How deep is too deep?

There is no universal number. The old 'three-click rule' is a widely repeated heuristic, not a standard, and usability research has argued it is a myth. Use the depth the tree shows to ask why a page sits where it does: whether real visitors would follow that path, and whether the page could live one level up instead.

What is a silo?

A silo is one top-level branch of the tree: a section such as Services or Blog with everything nested beneath it. Silo planning means each topic's pages live inside a single branch rather than spread across several, so the hierarchy matches the site's topical groupings. In the tool, pages that share a branch share a silo, and pages in different branches do not.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools