Path depth analyzer
A URL list tells you nothing until you see its shape. Paste a sitemap export or a crawl and get the site's structure: how many URLs sit at each depth, which folders hold them, and where a branch has quietly grown to six levels. Useful for SEO structure reviews, for planning a migration, and for finding the section nobody remembered existed.
Depth histogram
Folder tree
Stats
How to use
- Paste your URL list. The sitemap URL lister produces exactly the right format if you are starting from a sitemap.
- If the list spans several hosts, pick one from the Host selector — mixing a CDN subdomain into the tree makes the shape meaningless.
- Read the histogram: each row is one depth level with a bar showing its share. A healthy content site peaks at depth 2–3.
- Set Tree depth to show to control how far the folder tree expands. Each branch shows how many URLs live under it and how many end there.
- Copy tree gives you an indented text version for a document or ticket.
Reading the shape
A long tail past depth 4. Every extra segment puts a page further from the home page in internal link terms, and pages more than three or four clicks deep get crawled less often. A tail at depth 6–7 usually means a date-based or category-nested URL scheme (/blog/2026/07/31/category/slug) that could be flattened without losing anything.
One folder holding most of the site. Normal for a blog or a docs site, and a warning sign for an e-commerce catalogue — it often means faceted URLs are being generated and indexed under one branch.
Many URLs at depth 1. A flat site, which crawls well but gives search engines no signal about which pages are important. Grouping into sections is generally a gain, provided the sections match how people actually navigate.
A branch with a high count but almost none "ending here". That folder is a pure container — it has no page of its own. Worth checking whether the container URL returns a 404 or an empty listing, because internal links and breadcrumbs will point at it.
FAQ
Does depth count the query string?
No — only path segments. A URL with ten parameters at depth 1 is still depth 1. For query-string analysis use the batch URL parser with parameter columns turned on.
Is a trailing slash counted as a segment?
No. /blog and /blog/ both count as one segment, so the histogram is not skewed by inconsistent trailing slashes. If those inconsistencies are your actual problem, the canonical grouper finds them.
Why does the tree stop expanding?
To stay readable — raise Tree depth to show up to 8. The counts on each branch are always for the whole subtree, however deep it goes, so a collapsed branch still tells you its true size.
Are unparseable lines a problem?
They are skipped and counted in the stats table as "unparseable lines". A high number usually means the list has relative URLs — resolve them first with the relative URL resolver.