Brandon Lazovic

Tool · Site architecture

URL taxonomy visualizer

Turn a list of URLs (or a CSV) into an interactive, collapsible tree of your site's structure, with page counts at every level.Everything runs in your browser; nothing is uploaded.

Your site tree will appear here.

No tree yet. Paste URLs above, or

What does a URL taxonomy visualizer do?

It reads a flat list of URLs and rebuilds the site hierarchy they imply, grouping pages by their path so you can see how a catalog or content set is organized, where the depth lives, and which sections hold the most pages. It is the fastest way to sanity-check information architecture, spot orphaned or over-nested sections, and communicate structure to a stakeholder without a crawl diagram.

How to use this tool

  1. Add your URLs. Paste a list of URLs (one per line), or paste/upload a CSV with a URL column plus L0-L7 level columns.
  2. Pick how the tree is built. In URL mode the tree is derived from each URL's path segments; in CSV mode it uses your explicit level columns. Auto-detect picks for you.
  3. Explore, then export. Expand and collapse branches, read the page counts per section, filter by name, and click any URL to open it. Download CSV breaks every URL into path-level columns (Full URL, L1, L2, ...) — the full list, even when the on-page tree is capped.

Option A: paste a list of URLs

Paste one URL per line (absolute or root-relative). The tree is derived from each URL's path segments, and each branch shows how many pages sit under it. This input:

https://shop.example.com/shoes/trail/mens
https://shop.example.com/shoes/road
https://shop.example.com/apparel/jackets

produces shoes (2) with trail › mensand road beneath it, plus apparel (1) › jackets.

Option B: paste or upload a CSV

Use CSV mode when your taxonomy is not the URL path (for example a merchandising or content hierarchy). The first row is a header. Include a Full URL column and one column per level namedL0, L1, L2 and so on, in order:

Full URL,L0,L1,L2
/p/123,Shoes,Trail,Mens
/p/456,Shoes,Road,
/p/789,Apparel,Jackets,

Leave a level cell blank where a URL does not go that deep (row two stops at L1). If there are no L columns, every column except the URL is treated as a level, in order.

How does it work?

In URL mode the tool reads each URL's path, splits it on/, and nests the segments into a tree, tallying a page count at every level. In CSV mode it ignores the path and builds the tree from your explicit L0-Ln columns instead. Either way the parsing, tree-building, and rendering happen entirely in your browser with plain JavaScript; the collapsible branches use native HTML disclosure elements, so the view is keyboard-accessible and needs no framework.

Is my data safe?

Yes. The tool parses your URLs and builds the tree locally in your browser. Nothing is transmitted or stored, so it is safe to use with staging URLs or unreleased site structures. Only absolutehttp(s) URLs are turned into clickable links; anything else is shown as plain text.

Frequently asked questions

Is my URL list uploaded anywhere?

No. Parsing and tree-building run entirely in your browser with JavaScript; your URLs never leave your device.

What is the difference between URL mode and CSV mode?

URL mode derives the hierarchy from each URL's path (e.g. /shoes/trail/mens becomes shoes > trail > mens). CSV mode ignores the path and uses the explicit L0-L7 columns you provide, for when your taxonomy is not the URL structure.

Where do I get a list of URLs?

Export from a crawl, an XML sitemap, Search Console, or an analytics tool. This pairs with the sitemap URL extractor tool, whose output you can paste straight in.

How big a list can it handle?

It comfortably handles thousands of URLs in the browser. The on-page tree is capped for responsiveness (and tells you when), but Download CSV always exports the full list, broken into path-level columns.

Why does URL structure matter for SEO?

A shallow, consistent URL hierarchy helps crawlers discover and prioritize pages, clarifies topical relationships between sections, and keeps important pages close to the homepage. Visualizing the tree makes over-nested branches, inconsistent nesting, and thin sections obvious at a glance.

Can I use it to find over-nested or thin sections?

Yes. The page count on each branch shows where pages concentrate; a deep branch with a low count is often over-nested, and a shallow branch with a high count may need sub-categorization. Expand-all plus the depth figure in the stats line surface both quickly.

Related tools

Feed it with the sitemap URL extractor (its output pastes straight in), and check page markup with the JSON-LD prettifier & validator. See all SEO tools.