Visual Sitemap Generator
Enter a domain and get an expandable tree of its structure, built from its sitemap where one exists and from a live crawl where one does not.
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.
A quick sanity check
Look at your top three sections by page count and ask whether that ranking matches your commercial priorities. When it does not, you have found a crawl budget problem that no amount of on-page work will fix.
Using the tree in real work
- 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.
- 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.
- 03
Scope a migration
Section page counts tell you where the redirect work actually is, which is rarely where people assume it is.
- 04
Study a competitor
Their sitemap is public. The tree shows you how they organise content and which sections they have invested in.
- 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.
Frequently Asked Questions
What is a visual sitemap?
A visual sitemap shows a site's pages as a tree grouped by URL path, rather than as a flat list. It makes structure legible: which sections exist, how many pages each holds, and how many clicks deep the content sits.
Where does the tool get the URLs?
From the site's XML sitemap where one exists, following any sitemap index down through its children. If no sitemap is found, it falls back to crawling up to 100 pages live, and tells you which of the two it used.
How is the tree built?
URLs are split on their path segments and grouped. So /blog/seo/sitemaps becomes blog, then seo, then sitemaps. Sections are sorted by how many pages sit under them, so the biggest parts of the site appear first.
What does the number beside a folder mean?
It is the total count of URLs anywhere beneath that path, not just its direct children. A section showing 340 holds 340 pages across all its levels.
What is a healthy site depth?
As a rule of thumb, important pages should sit within three clicks of the homepage. Depth in this tree reflects URL structure rather than click depth, but the two usually correlate, and a section buried five levels down is worth questioning.
Is this the same as an HTML sitemap?
No. An HTML sitemap is a page on your site that links to your content, aimed at visitors and at helping crawlers find orphan pages. This is an analysis view of an existing structure, for you rather than for your visitors.
Can I export the tree?
Yes. Copy it or download it as an indented text file, which pastes cleanly into documents, tickets, and site architecture proposals.
Other sitemap tools
XML Sitemap Generator
Crawl any website and generate a valid XML sitemap you can download and submit. No signup, no software to install.
Use toolXML Sitemap Validator
Test any XML sitemap against the sitemaps.org protocol. Catches namespace errors, bad lastmod dates, size limits, and cross-domain URLs.
Use toolSitemap Crawler
Crawl every URL your sitemap declares and find the dead links, redirects, noindex pages, and canonical conflicts hiding inside it.
Use toolSitemap URL Extractor
Pull every URL out of a sitemap or sitemap index and download the list as CSV, TXT, or JSON. Handles nested indexes and gzipped files.
Use toolSitemap Finder
Find where any website hides its sitemap. Checks robots.txt directives plus nine common paths, including WordPress and gzipped variants.
Use toolStructure is only half the picture
CrawlRaven maps your whole site, then layers Search Console impressions and GA4 sessions onto every section, so you can see which parts of the structure actually earn anything.