Brand Extractors·4 min read

Reading Site Structure From a Sitemap Tree View

Inheriting a website nobody documented is a rite of passage, and the fastest orientation exercise costs nothing: the site's own sitemap already lists every page it wants indexed. Reading site structure from a sitemap turns that flat file into a map of sections, sizes and depth, no crawler required. The Sitemap Visualizer finds the file and renders it as a collapsible folder tree in seconds. This piece covers how to read the tree, what depth and forgotten sections look like, and the file-format rules worth knowing.

Open the free Sitemap Visualizer All insights

The sitemap tree as an X-ray of a site

Structure hides in plain sight.

A sitemap is a machine-readable list of everything a site publishes. Reading it as XML tells you almost nothing, because two thousand loc lines in arbitrary order have no shape. Group those same URLs by path segment, though, and the site's skeleton appears: which sections exist, how big each one is, how deep the content sits.

That view answers real questions fast. Where did the old agency put the landing pages? Is the blog 40 posts or 900? Does the site have a half-launched /es duplicate tree? One look at the tree, versus an afternoon of clicking.

Reading site structure from a sitemap, step by step

From flat file to folded tree.

Type a domain and click Load sitemap. The tool follows redirects, reads the Sitemap lines in robots.txt, tries common paths such as /sitemap.xml and /sitemap_index.xml, and opens nested sitemap indexes. If the live site blocks the request or has no sitemap, it checks the Wayback Machine for an archived copy and says so. For a blocked or private site you can also paste sitemap XML, or a plain list of URLs, and click Visualize pasted list.

Each URL's path is split into segments, so /shop/planters/ceramic files under shop, then planters, then ceramic. The first two levels open by default, every folder shows the total number of URLs at or below it, and each page links to the live URL. Scan the top-level folders and their counts first, that is the site's table of contents, then expand the branch your project concerns. The Diagram tab draws the same top levels as boxes you can save as SVG or PNG for a deck.

A worked sitemap tree walkthrough

1,240 URLs, four findings.

Load a garden retailer's site and the top level reads: /shop with 860 URLs, /journal with 310, /guides with 58, and 12 loose pages at the root. Expanding /shop shows /planters, /tools and /seeds, with paths reaching /shop/planters/ceramic/small-terra-pot.

Four findings in one look: commerce outweighs content by a wide margin, the journal is a serious archive rather than a token blog, guides are thin next to everything else, and product pages sit four segments deep. Type /journal/ into the Filter box and click Export CSV, and the content team gets every journal URL with its path, depth and top-level folder in a sheet.

Deep branches and forgotten sections

The two patterns worth hunting.

Depth first: when a branch nests five or six segments, ask whether users can actually click their way down there. URL depth and click depth are not identical, but they correlate, and pages buried that far usually get little internal linking and less crawl attention.

Orphan candidates look different: a folder full of pages that the site's navigation never mentions. Old campaign folders, test leftovers and abandoned locale trees all show this signature. The sitemap proves the pages exist; a check of the menus and internal links shows whether anything still points at them. Two folders doing one job, such as /product/ and /products/, often point to an old migration too.

Size limits and sitemap index files

The protocol's fine print.

The sitemap protocol caps each file at 50,000 URLs or 50 MB uncompressed. Sites that exceed either limit split into several sitemaps and publish a sitemap index that lists them.

When you load a site or an index URL, the visualizer opens each child sitemap and merges their pages into one tree, stopping at 5,000 URLs and telling you when it does. On a large site, load the child sitemap for the section you care about directly to stay under that limit. Pasted index XML is different: it only contains links to child sitemaps, so paste each child file instead.

Mistakes when reading a sitemap tree

The tree is only as truthful as the file behind it, so keep these in mind.

Assuming the sitemap equals the site. It lists what the owner chose to submit; pages can exist outside it and entries can 404.
Reading URL counts as importance. A branch of 800 thin tag pages outweighs nothing.
Missing the note that a tree came from the Wayback Machine, and treating an archived copy as the live site.
Forgetting the file may be stale; sitemaps generated by a job that stopped running last year still look authoritative. The lastmod counts in the Stats tab show this quickly when the file has dates.
Confusing sitemap structure with navigation. The tree shows URL paths, not the menus users travel.

Tips for sitemap structure audits

The tool reads robots.txt on its own, but it is still worth opening robots.txt yourself: it shows which sitemaps the site declares, and if there are separate files for images or news, you can load the one you need directly.

Then compare the tree against the site's main navigation side by side. Sections present in the tree but absent from the menus are your orphan shortlist, and sections in the menus but thin in the tree show where the site promises more than it publishes.

Sitemap Visualizer vs related tools

Reading, writing, and the page level.

The Sitemap Visualizer reads structure that already exists. When you are producing the file instead, the XML Sitemap Generator builds a valid sitemap from your URL list. The Robots.txt Tester and Validator pairs naturally with both, since robots.txt is where sitemap locations are declared. Once site-level structure looks sane, the Heading Tag Checker (H1 to H6) applies the same outline thinking one level down, to the headings inside a single page.

Try it now

Open Sitemap Visualizer

The tool is one click away. No sign up, no upload, no payment.

Open Sitemap Visualizer

Write a review