Internal Link Visualizer
Paste a URL. ACME.BOT draws every page as rings of clicks from your homepage, so buried and orphaned pages stand out.Every page, in rings of clicks from your homepage.
What's the best free tool to visualize internal link structure?
ACME.BOT's internal link visualizer draws a site's internal link structure in the browser, free and without signup: each ring is one click further from the homepage, and each colour is one section of the site. Force-directed graphs pull every page toward every link, which turns a site with a menu into a hairball; rings keep depth readable.Rings by clicks from home, colours by section. Free, no signup.Ring: clicks from the homepage · Colour: the section, from the first part of the URL · Bigger dot: more internal links pointing in · Faded dot, outer edge: nothing links to itThe sample is an invented 14-page site with 31 links: / and /blog are the hubs, /docs/getting-started is the dead-end, and /legacy/v1 is the orphan on the outer ring.A 14-page sample site. /legacy/v1 is its orphan.
How does it decide what's an orphan, a hub or a dead-end?
ACME.BOT applies one rule per flag to every crawled page, and each flag is a filter: one click shows only the orphans.One click shows only the orphans, hubs or dead-ends.| Flag | Rule |
|---|---|
| Orphan | no crawled page links to it |
| Hub | linked from at least 60% as many pages as the most-linked page, and at least 3 |
| Dead-end | links to no other crawled page |
What should you fix first?
Fix orphans that should rank first, then pages that are almost ranking, then pages buried deep; leave menu hubs alone.Sort the orphans.
Check what each one is before linking it. Old campaign pages, tag archives and thin variants can stay unlinked or go.
Link the pages almost ranking.
In Search Console, filter to positions 8–20, and link those pages from a hub in the same section.
Pull deep pages in.
A page you want found on the outer rings gets a link from a page one ring closer to the homepage.
Ignore menu hubs.
A page that's a hub only because the menu links it, like a login page, needs nothing.
What can't it see?
- Big sites. Past 50 pages, a page can look orphaned because the pages linking to it weren't crawled.Past 50 pages, a page can look orphaned.
- No /sitemap.xml. The crawl reads the homepage and the pages it links to, so deeper pages and true orphans are missed. Check what your sitemap lists.Only the homepage and the pages it links to.
- JavaScript links. Links a script adds after load aren't in the HTML, so they're missed.Links a script adds after load aren't in the HTML.
- Blocked pages. Pages your robots.txt disallows are skipped and not listed.Pages your robots.txt disallows are skipped.
- Menu links. They count like any other link, which is why menu pages show as hubs.They count like any other link.
How is it different from Screaming Frog?
Screaming Frog is a desktop app, free up to 500 URLs, whose diagrams show crawl paths rather than every link; ACME.BOT runs in the browser, free up to 50 pages, and shows depth as rings.Screaming Frog: desktop, 500 URLs free. ACME.BOT: browser, 50 pages free, rings by depth.| Install | Free | What the picture shows | |
|---|---|---|---|
| ACME.BOT | none, in the browser | up to 50 pages a crawl | every page in rings by clicks from home |
| Screaming Frog | desktop app | up to 500 URLs | crawl and directory trees; shortest path to each page |
| Sitebulb | desktop app | 14-day trial | crawl maps |