Visual Sitemap Generator

Why structure is easier to judge as a tree

A list of 2,000 URLs tells you almost nothing. The same URLs grouped by path immediately answer questions a list cannot.

• Where the weight sits. One section holding most of your pages is where most of your crawl budget goes.
• How deep content is buried. Long chains of nesting usually mean pages that are hard to reach and slow to get indexed.
• Which sections are thin. A top-level section with three pages under it is rarely worth being top level.
• Whether the taxonomy leaked. Tag and category archives multiplying into hundreds of URLs shows up instantly here.
• What does not belong. Staging paths, old campaign directories, and orphaned test sections stand out in a tree in a way they never do in a list.

Using the tree in real work

1. 01

   Audit an unfamiliar site

   Before taking on a new client or codebase, the tree gives you the shape of the site in about thirty seconds.

2. 02

   Plan an information architecture change

   Export the current structure as text, edit it into the proposed one, and you have a before and after that non-technical stakeholders can read.

3. 03

   Scope a migration

   Section page counts tell you where the redirect work actually is, which is rarely where people assume it is.

4. 04

   Study a competitor

   Their sitemap is public. The tree shows you how they organise content and which sections they have invested in.

5. 05

   Spot depth problems

   Anything sitting four or five levels deep is a candidate for promotion or for internal linking work.

Sitemap tree versus click depth

This tree is built from URL paths, which is not quite the same as how many clicks a page is from the homepage. The two usually track each other, but they can diverge in ways worth knowing about.

• A flat URL can still be deep. A page at /product-name may only be reachable through four levels of navigation.
• A deep URL can still be shallow. A page at /blog/2026/07/post can be linked directly from the homepage.
• Crawlers care about link depth, because that is how they reach pages, but URL structure shapes how people and search engines interpret hierarchy.

For the underlying URL list rather than the shape, use the sitemap extractor. To check whether the URLs in that structure are actually healthy, run the sitemap crawler.

When the tool falls back to crawling

If a site has no discoverable sitemap, the tool crawls up to 100 pages live and builds the tree from those instead. The result says which source it used, because a crawl-built tree only reflects what is reachable by following links, and will miss any orphan pages entirely.

What depth costs, level by level

Depth is the thing a flat URL list hides and a tree makes obvious. The figures below are directional rather than thresholds: what matters is the shape of your own tree relative to the pages you care about.

What the shape of the tree tells you

A healthy tree is wide near the top and shallow overall. The two shapes worth noticing are a single branch carrying most of the site, which usually means a category that grew without anyone splitting it, and a long thin chain, which means a hierarchy that exists in the URL structure and nowhere in the navigation a visitor sees.

Frequently asked questions