Sitemap Viewer

How to View a Sitemap

Features

The File Search Engines Actually Read

A sitemap doesn't influence rankings directly, but it's one of the plainest signals a site can hand a crawler: here is every page we consider worth finding. For a small site, that barely matters — normal crawling finds everything anyway. For a large one, or a section of a site with weak internal linking, a sitemap can be the difference between a page getting discovered promptly and sitting unindexed for months. This tool reads that file the same way a crawler would and shows you exactly what it contains.

Who Actually Opens This File

• SEOs and site owners — auditing whether a sitemap actually reflects the site's real, current pages
• Developers — confirming a generated sitemap is well-formed right after a CMS migration or platform switch
• Agencies — quickly sizing up an unfamiliar client site's structure before deeper work begins, often alongside a quick HTTP Header Checker pass for caching and security basics
• Anyone debugging indexing issues — checking whether a specific page is even listed before assuming a crawling problem

Why Some Sitemaps Are Really Just a List of Lists

Large sites almost never publish one giant sitemap — the protocol itself caps a single file at 50,000 URLs, so anything bigger gets split into multiple files, all referenced from one sitemap index. That index file doesn't contain a single page URL itself; it's purely a directory pointing to the real sitemaps underneath. This is exactly why the drill-down here exists — without it, an index file would just look like an oddly empty, unhelpful result.

Three Fields, Only One Worth Trusting

A sitemap entry can carry three optional pieces of metadata beyond the URL itself, and they don't carry equal weight. lastmod records when a page last changed — genuinely useful as a re-crawl signal, provided whatever generates the sitemap actually updates it accurately. changefreq is a stated guess at how often a page changes (daily, weekly, yearly), and priority is a 0.0–1.0 self-assigned importance score. Google has said plainly, for years, that it largely ignores both of the latter two, precisely because so many sitemap generators set them to the same default value across every single URL regardless of whether that page actually changes daily or hasn't been touched in years.

That's exactly why the freshness statistics here focus on lastmod coverage rather than surfacing changefreq or priority as if they carried equal signal — a stat built around a field crawlers mostly discount wouldn't tell you anything a real audit should act on.

Catching a Migration Problem Early

A site moves to a new CMS, and the new sitemap generator quietly points every URL at the old domain structure instead of the new one. Nobody notices until organic traffic drops weeks later. Pulling up the sitemap right after any migration and skimming the actual URLs listed — not just trusting that "the sitemap was regenerated" — catches this in minutes instead of after the damage is already done. If the domain itself just moved hosts, checking the DNS Lookup Tool first confirms you're even looking at the sitemap the new server is actually serving.

Getting More Out of a Sitemap Check

• Check the freshness stats first. A site with thousands of URLs but almost none showing a recent lastmod either updates rarely or isn't maintaining that field — worth knowing before reading too much into individual dates.
• Group by category to sanity-check site structure against what you'd expect — an unexpectedly huge count under one category often reveals auto-generated pages (tag archives, filtered category combinations) nobody intended to index at scale.
• Download the Excel file before a big audit. Splitting URLs into one sheet per category makes it easy to assign different sections of a large site to different reviewers.
• Cross-reference against robots.txt. A URL blocked there but still listed in the sitemap is a contradictory signal worth cleaning up — pair this with our Robots.txt Generator when fixing it.
• Don't trust changefreq or priority for anything important. Treat lastmod as the only field here worth real attention, and only when a site is known to keep it accurate.

What the Multi-Sheet Export Is Actually For

A flat list of ten thousand URLs isn't something any one person reviews end to end, which is the whole reason the Excel download splits into a sheet per category instead of dumping everything into one tab. In practice, that means a site audit stops being one person's multi-day slog and becomes something a team can split up in an afternoon — one reviewer takes the /blog/ sheet, another takes /products/, a third checks the summary sheet's freshness numbers against what marketing claims was recently updated. Nobody needs to filter a giant spreadsheet down to their section first; the file is already organized that way.

The summary sheet earns its own use on top of that: a category count that's dramatically larger than anyone expected is usually the first sign of an auto-generated URL pattern — paginated filters, tag archives, faceted search combinations — quietly outnumbering a site's real content by ten or twenty to one, long before anyone opens a single URL to confirm it.

What This Won't Tell You

A sitemap listing a URL doesn't mean that page is actually indexed, ranking, or even still returning a 200 status — it's a claim the site makes, not a guarantee from the search engine. For real indexing status, Google Search Console's own coverage reports are the authoritative source. And a handful of sitemaps are gzip-compressed and won't parse here; checking for an uncompressed version at the same location, or pasting the sitemap index's readable child sitemap instead, is the workaround.