100% offline
Developer
Free · no signup
Updated

Sitemap Visualizer & Validator

A sitemap visualizer turns a sitemap.xml file into a diagram of the site it describes, arranging its URLs into a tree by path. This one reads sitemaps, sitemap indexes, gzipped files and feeds, checks them against the sitemaps.org protocol and Google's documentation, and exports the map as SVG, PNG, Mermaid or a Markdown outline — all in your browser.

Drop files here, or

Sitemaps, sitemap indexes, .gz files, RSS or Atom feeds, or a text list of URLs. Drop an index together with the sitemaps it lists to map the pages in them.

Everything is read in this tab; nothing is uploaded.

Paste a sitemap or drop files to map them.

About Sitemap Visualizer & Validator

A sitemap is an XML file that lists the URLs a site wants search engines to find: one <url> entry per page, with its address in <loc> and, optionally, the date it last changed in <lastmod>. A file can hold 50,000 URLs and 50 MB uncompressed, so larger sites split their URLs across several sitemaps and list those in a sitemap index. Search engines treat all of it as a hint. Google and Bing both say they ignore <priority> and <changefreq>, and both rely on <lastmod> being the date the page's content really changed.

Paste the XML or drop the file and every URL becomes a box in a tree built from its path, so /blog/2024/hello sits under blog, then 2024. Folders that aren't pages themselves are drawn dashed, every branch shows how many URLs it holds, and the map can be coloured by section or by how recently each page changed. Drop a sitemap index together with the sitemaps it lists and they're mapped as one site; any you haven't added are listed with their URLs so you can fetch them. Branches open and close with a click, and long ones show their first 25 children, so even a 50,000-URL sitemap stays quick to explore.

Each file is also checked against the protocol, its XML schema and Google's documentation: broken XML, relative URLs, bad dates, the size limits, duplicates, and image, video, news and hreflang tags. Every finding gives its line and column and links the document the rule comes from.

The tool reads only what you give it. It doesn't crawl the site or check that pages load, and nothing you paste or drop leaves your browser.

What Sitemap Visualizer & Validator does

  • Reads sitemaps, sitemap indexes, .xml.gz files, RSS and Atom feeds and plain-text lists of URLs
  • Maps every URL into a collapsible tree by its path, left to right or top down
  • Colours the map by section or by how recently each page changed
  • Connects a sitemap index to the child sitemaps you add with it
  • Checks each file against the sitemaps.org protocol, its XML schema and Google's documentation, with line numbers
  • Validates hreflang codes and return links, and image, video and news tags
  • Exports the map as SVG, PNG, Mermaid or a Markdown outline, and the URLs as CSV
  • Runs entirely in your browser — nothing is uploaded

When to reach for Sitemap Visualizer & Validator

  • Seeing the shape of a site before a redesign, a migration or a content audit
  • Finding out why Search Console reports a sitemap error, and on which line
  • Checking that a generated sitemap lists what you expect, and nothing you don't
  • Auditing the hreflang annotations of a multilingual site
  • Putting a map of a site into documentation or a proposal as SVG or Mermaid

How to use Sitemap Visualizer & Validator

  1. 01

    Add your sitemap

    Paste the XML or a list of URLs, or drop the file — .xml, .xml.gz or .txt. Add a sitemap index together with the sitemaps it lists to map them as one site.

  2. 02

    Explore the map

    Click a box to open or close its branch, search to narrow the map, and switch between left to right and top down. Colour it by section or by last modified date.

  3. 03

    Fix what's flagged

    Every problem is listed with its file and line, how to fix it, and the document the rule comes from.

  4. 04

    Export

    Download the map as SVG or PNG, copy it as Mermaid or a Markdown outline, or save the URLs as CSV.

When to use Sitemap Visualizer & Validator vs alternatives

AlternativeUse Sitemap Visualizer & Validator when…Use the alternative when…
A crawler such as Screaming Frogyou want to see and check what the sitemap itself says, instantly and without installing anything.you need to find pages the sitemap leaves out, or check status codes, canonical tags and internal links — that takes crawling the site.
Online visualizers that fetch a sitemap URLthe sitemap is on a staging site, behind a login or not live yet, or you'd rather no one else fetched it.the sitemap is public and you'd rather paste its address than download the file.
Google Search Console's Sitemaps reportyou want to check a sitemap before it goes live, or one for a site you can't access in Search Console.you need to know what Google actually read, and when.

Frequently asked questions

How do I visualize a sitemap.xml file?
Paste the sitemap's XML here or drop the file, and every URL is drawn as a box in a tree built from its path. If your browser shows the sitemap as a styled page, use View Source, or download it with curl, to get the raw XML. For a sitemap index, add the sitemaps it lists too, and they're connected into one map.
What's the difference between a sitemap and a sitemap index?
A sitemap lists pages: up to 50,000 URLs, and 50 MB uncompressed, per file. A sitemap index lists sitemaps instead, up to 50,000 of them, so a large site can split its URLs across many files and submit only the index. An index can't list another index.
Do Google and Bing use priority and changefreq?
No. Google says it ignores both tags, and so does Bing. What both use is lastmod — as long as it's the date the page's content last changed, not the time the sitemap was generated. When nearly every URL shares one lastmod, it's usually the latter, and this tool points it out.
What date format does lastmod use?
W3C Datetime, the profile of ISO 8601 the protocol specifies: a plain date such as 2024-05-01, or a date and time with a time zone, such as 2024-05-01T09:30:00+00:00. Without the time zone it's no longer W3C Datetime, a month on its own (2024-05) is rejected by the sitemap's XML schema, and formats like 05/01/2024 are invalid under both. Each one is flagged on its line.
How do I check hreflang in a sitemap?
Each <url> lists its language versions as <xhtml:link rel="alternate" hreflang="…" href="…"> tags, including one for itself. The tool checks every code — an ISO 639-1 language, optionally an ISO 15924 script and an ISO 3166-1 region, or x-default — and that each pair of pages links both ways, because Google ignores a pair that doesn't.
Is my sitemap uploaded anywhere?
No. The file is read and drawn by JavaScript in your browser tab, and nothing is sent anywhere, so you can map a staging site's sitemap or one that isn't live yet. It also means the tool only knows what the sitemap says: it doesn't visit the URLs to check that they load.

Related concepts