Site Architecture Visualizer
Search engines infer how important a page is partly from how few clicks it takes to reach it. Type a domain and this tool fetches the site’s real sitemap for you — reading robots.txt, following it to the XML sitemap, walking any sitemap index — then draws the true shape of the site: homepage at the top, every section nested beneath. It tells you where pages are buried too deep, which section dominates, and whether the architecture is flat enough to crawl. No sitemap, or want to map a list of your own? Paste URLs straight in instead.
Site architecture is the parent-child hierarchy of your pages, measured in clicks from the homepage. Enter a domain and this tool reads its robots.txt, follows it to the XML sitemap, and pulls the live URLs — or you can paste your own list or sitemap. It strips the protocol, host, query and anchor from every URL, splits each path into segments, and builds a nested tree with the homepage as the single root. It then reports your total URLs, top-level sections, maximum depth, your widest section, and how many pages sit deeper than three clicks — the rough threshold beyond which pages get crawled and ranked less.
Site Architecture Visualizer inputs and result
robots.txt, follows it to the XML sitemap(s), walks any sitemap index, and drops the live URLs into the box below — then draws the tree. No sitemap? Paste URLs manually instead.| Metric | Value | What it tells you |
|---|
How to use this calculator
- Enter a domain, or paste your URLsThe fast path: type a site URL (example.com) and click Fetch & map. The tool reads the site’s robots.txt, follows it to the XML sitemap, walks any sitemap index, and loads the real URLs for you. No sitemap, or want to map a custom list? Paste page URLs one per line, or the entire contents of an XML sitemap, into the box — the tool reads every <loc> tag and ignores blank lines and comments.
- Pick a display depthChoose how many levels to draw. Two or three keeps a big site readable; “All” shows everything up to the render cap. Anything below the limit is summarized as a “+N more” count rather than dumped.
- Read the treeThe homepage sits at the top, with each section nested beneath it and a badge showing how many pages live under that branch. Branches deeper than three clicks are flagged, because those pages are the hardest to crawl and rank.
- Check the insightsThe table reports total URLs, top-level sections, maximum and average depth, your widest section, pages buried beyond three clicks, and single-child chains — each with a plain-language read on whether it helps or hurts.
- Act on the verdict, then exportUse the verdict and analysis to decide what to flatten or relink, then copy a share link, export the metrics to CSV, or print the whole map for a structure review.
RGM Expert Says
The first thing we do on a technical SEO engagement is draw the site — not look at a list of URLs, but actually see the tree. A flat list hides the problem; the tree shows it instantly. You can spot a section that has quietly grown five levels deep, a homepage that links to forty top-level folders, or a thin pass-through directory that adds a click for no reason. None of that is obvious in a spreadsheet, and all of it shapes how Google crawls and ranks the site.
The number we keep coming back to is click depth. Google has said for years that it infers a page’s importance partly from how many links it takes to reach it, and pages buried deep in the tree get crawled less often and rank worse. So when this tool flags pages sitting more than three clicks from home, that is not a vanity metric — it is a list of pages that are quietly being starved of crawl attention and internal authority. The fix is almost always internal linking: hub pages, category listings, and related-content blocks that pull deep pages closer to the surface.
Use this before a migration, after a big content push, or whenever a section stops ranking the way it should. Type the domain, let the tool pull the live sitemap, look at the shape, and ask the two questions that matter: is anything buried too deep to crawl, and is one branch swallowing the whole site? Those two answers drive more SEO lift than most on-page tweaks, because they change how every page in the tree is discovered.
How it works
The logic is plain text parsing, not magic. When you fetch a domain, the tool reads its robots.txt, follows it to the sitemap, and gathers the live URLs; from there every URL is reduced to a pathname, the pathname is split into segments, and the segments are threaded onto a tree whose single root is the homepage.
- Click depth — how many links it takes to reach a page from the homepage; the lower the better for crawling and ranking.
- Top-level sections — the first path segment after the domain (/blog/, /products/, /about/); these are the trunk of the tree.
- Widest section — the top-level branch holding the most pages; a healthy site is not dominated by a single branch.
- Single-child chain — a folder with exactly one child, which adds a level of depth without adding any real structure.
Depth is measured by path segments, which is a close proxy for click depth on well-linked sites; a page reachable by a shortcut link can be fewer clicks from home than its URL implies. Treat the depth figures as a structural signal, and confirm true click depth with a crawler such as Screaming Frog when it matters.
Why depth and shape decide what gets crawled
Search engines do not crawl every page equally. Google has said plainly that it uses the number of links it must follow to reach a page — and the number of links pointing at it — to infer how important that page is relative to the rest of the site. A page sitting six clicks down a lonely branch reads as unimportant, gets crawled less often, and struggles to rank, no matter how good the content is.
That is why a flat, shallow architecture is the default advice from credible technical SEO sources. The rule of thumb — keep the pages you care about within roughly three clicks of the homepage — is not a hard law, but it captures something real: every extra level multiplies the links a crawler must follow and the authority that has to flow down to reach the page. Flattening the tree puts important pages closer to the front door.
Shape matters as much as depth. A top-heavy site where one branch holds most of the pages can bury individual URLs deep inside that branch while starving smaller sections of internal links. Single-child chains do the same damage quietly, adding clicks with no structural payoff. Seeing the whole tree at once is the fastest way to catch both problems before they cost you crawl budget and rankings.
Rules of thumb for site depth
These are widely-cited rules of thumb from technical SEO practice, not promises — the right shape depends on your site’s size and how well it is internally linked. Treat them as targets to aim at, then verify true click depth with a crawl.
| Signal | Rule of thumb | Why it matters |
|---|---|---|
| Click depth of key pages | Within ~3 clicks of home | Deeper pages get crawled and ranked less; Google infers importance from link distance. |
| Maximum site depth | Keep as shallow as the content allows | Each extra level multiplies links a crawler must follow to reach the page. |
| Top-level sections | A focused handful, not dozens | Too many top-level folders crowd the nav and dilute internal authority. |
| Widest section share | No single branch dominating the site | Top-heavy trees bury pages inside one branch and starve the rest. |
| Single-child chains | Collapse where you can | Pass-through folders add depth without adding structure. |
| Orphan pages | Zero — every page linked from somewhere | A page with no internal links may never be crawled at all. |
What search engineers and SEOs say
Google uses the number of links it needs to follow to reach a page, and the number of links to a page, to infer the relative importance of that page on your site.
Draw the tree before you touch a single page. A flat list hides the buried sections; the hierarchy shows you exactly which pages the crawler will struggle to reach.
Go deeper on site structure
Keep learning
Learn & train
Services & tools
Common questions
What does the site architecture visualizer do?
How does fetching a site work?
robots.txt, locate the sitemap it points to, walk any sitemap index to gather child sitemaps, and return the live list of URLs (capped for very large sites). Those URLs drop straight into the box so you can see and edit them, and the tree draws automatically. If a site has no sitemap or blocks the request, you can always paste URLs manually as a fallback.