Paste a plain list of URLs or the raw contents of an XML sitemap, and see your entire site structure rendered as a clean, collapsible folder tree.
Paste a URL list or sitemap XML above, then click "Visualize sitemap".
Paste a plain URL list or raw sitemap XML — the tool figures out which one it is.
Expand and collapse folder-level nodes to explore deep site structures without the clutter.
Every folder node shows how many pages live underneath it, plus a running total at the top.
Turn a flat list of URLs into a structure you can actually read.
A sitemap.xml file or a URL export from a crawler is easy for a machine to read and painful for a human to skim. Turning that flat list into a folder tree makes it immediately obvious how a site is organized: which sections are deep, which are shallow, and where duplicate or orphaned paths might be hiding.
Any one-per-line list of URLs or paths works, whether exported from a crawler, a CMS or just typed by hand.
Paste the raw XML of a sitemap.xml file and every <loc> value is extracted automatically, CDATA included.
Each URL's path is split into segments, and shared prefixes are merged into the same branch of the tree.
Every folder-level node shows how many of your pasted URLs live underneath it, so you can spot the biggest sections at a glance.
Questions about format detection, fetching and privacy.
It checks the pasted text for <loc> tags, which are how XML sitemaps wrap each URL. If any are found, every <loc> value is extracted as a URL; otherwise each non-empty line is treated as its own URL.
No. This is a client-side tool with no server component, and browsers block many cross-origin fetches by default, so it can't reliably download an arbitrary sitemap URL. Paste the file's content directly instead, which works for any site.
Only the path portion of each URL is used to build the tree. Query strings and fragments are ignored so the structure reflects your actual page hierarchy rather than every URL variant.
Yes. Lines like /blog/post-1 work exactly like full URLs; the tool only needs the path segments to build the tree.
No. Parsing and tree-building both happen locally in your browser. Nothing you paste here is sent to a server.