I tried it on my company's website, surroundtech.com. It just produced a parent node and a very wide tree of child pages. Not useful in any way.
The website is built using a CMS that's part of our product line, which auto-generates a sitemap.xml file. It also automatically produces a Sitemap page: https://surroundtech.com/sitemap. The two tabs of interest are "Cards", which shows how each page would look when shared via social media links, and "Sitemap Tree" which shows the (non-graphical) page tree.
To be fair to the visual tool, our auto-generated xml is just a flat list of urls, and our auto-generated url routing is a flat list of uniquely named pages rather than a /-separated hierarchy. To create our own sitemap page we use the hierarchy that's built into our CMS, which also creates the top-level menu on the site.
Neat design! I made related a tool that crawls a given URL and generates a 3D sitemap (essentially a directed graph): https://github.com/schedutron/visualnet
Doesn't work at all on my custom-generated sitemap.xml which is valid and accepted by search engines. Worse than that, it displays a bogus diagram rather than an error.
As sibling comments point out, there are kinks to work out in mapping out different website structures, and I would add the suggestion that greater information density could improve the UX.
But just think about the collective thousands of hours spent looking for things on websites. Helping a fraction of us find things a bit faster would add up to a big impact.
for that level of magic.. just use https://VisualSitemaps.com ;-) and yes, we also crawl password-protected sites, great for user-dashboards and staging.
thanks! And the best is coming in the next few weeks.
Ping us: hello at visualsitemaps.com if you want to try our upcoming Screenshot Annotations() and Sitemap Editing().
Looks hand-built with HTML. For simple trees that's often sufficient and means you can delegate layout to the browser instead of having to do it yourself.
I found this helpful when I was integrating visual sitemaps with documentation. They have a few different examples for different styles some don't even require JavaScript.
Import XML sitemap feature is one of many functions, but not major. Octopus.do is UX prototyping tool for creating Visual Sitemap from the very beginning.
Yeah I just tried our sitemap and all it detected was sub pages for each of our second-level sitemaps. Unfortunately it wasn't obvious what was supposed to happen so it took me a few minutes of poking about and then watching their sales video to guess what it should have done and why it was wrong.
When I tried with one of our leaf sitemaps that is nearing the 50k item limit it just errored. Given that all of the URLs are of the form `/item/<id>`, I'd expect it to be able to understand that there's only really one page type that they need to represent for that in their visual sitemap.
The website is built using a CMS that's part of our product line, which auto-generates a sitemap.xml file. It also automatically produces a Sitemap page: https://surroundtech.com/sitemap. The two tabs of interest are "Cards", which shows how each page would look when shared via social media links, and "Sitemap Tree" which shows the (non-graphical) page tree.
To be fair to the visual tool, our auto-generated xml is just a flat list of urls, and our auto-generated url routing is a flat list of uniquely named pages rather than a /-separated hierarchy. To create our own sitemap page we use the hierarchy that's built into our CMS, which also creates the top-level menu on the site.