All free tools
Free · no signup

XML Sitemap Validator

Paste or upload a sitemap and see every problem Google would report, with the line it's on — before you submit it, and for any site, not just the ones you've verified in Search Console. It also flags what's valid but useless, like the tags Google ignores.

Your sitemap

Paste the XML, a sitemap index, or a text sitemap.

.xml, .xml.gz or .txt

Nothing is uploaded and nothing is fetched — the file is read and checked in your browser, so a list of every URL on your site stays on your machine.

Result

Valid, with warnings

Google can read it. The warnings are about whether it helps.

Type
XML sitemap
URLs
5 of 50,000
Size
976 B of 50 MB
Hosts
example.com
With lastmod
5 (100%)

Findings

  • Every entry has exactly the same lastmod. That's usually the time the sitemap was generated, not when each page changed — and Google uses lastmod only when it's "consistently and verifiably" accurate.

    • 2026-10-21T06:00:00+00:00
  • Google ignores <priority> and <changefreq> entirely. They're harmless, but tuning them does nothing for Google — lastmod is the tag that matters.

    • 5 priority and 5 changefreq tags

This checks the file, not your server. Whether Google can fetch it, and whether the URLs in it actually work, are separate questions.

Share this result

Posts the numbers below and nothing you typed or pasted, and you get to edit it before it goes out.

“Validated my sitemap: 5 URLs, no errors. It also turns out Google ignores priority and changefreq completely, so every one of those tags was doing nothing.”

Why validate before you submit

Search Console’s Sitemaps report is the authority on what Google made of your sitemap, and every error this tool reports is named after one of its errors. But it only answers after you’ve submitted the file and Google has fetched it, and only for a property you’ve verified.

That leaves the two moments you most want an answer: before a new sitemap goes live, and when you’re looking at a site that isn’t yours. A sitemap generated by a plugin you’ve never read, a migration that changed every URL, a client’s site you’ve been handed — this is where those get checked.

What Google actually reads

A sitemap entry can carry four tags, and Google uses two of them. Its sitemap documentation is blunt: “Google ignores <priority> and <changefreq> values.” That leaves <loc>, the URL, and <lastmod>, the date the page last changed.

The URL has to be absolute — https://example.com/page, never /page — and any & in it must be written &amp;, because a sitemap is XML first. An unescaped ampersand in a query string is the single most common reason a sitemap fails, and it fails the whole file, not just that entry.

The lastmod trap

Google uses lastmod, but conditionally: “if it’s consistently and verifiably (for example by comparing to the last modification of the page) accurate.” A lastmod is only as useful as it is believable.

The commonest way to fail that test is a generator that stamps every entry with the time the sitemap was built. Every URL claims to have changed this morning, which is verifiably untrue for most of them, and the tag stops carrying any information. The tool above flags a file where every entry has the same lastmod for exactly this reason.

What counts as a change worth recording? Google’s post on lastmod gives the examples: “if you changed the primary text, added or changed structured data, or updated some links, do update the lastmod value.” A new copyright year in the footer doesn’t qualify.

The limits, and what happens past them

  • 50,000 URLs or 50MB per sitemap, measured uncompressed. Gzip shrinks the download, not the limit.
  • Past either, use a sitemap index — a file listing up to 50,000 sitemaps. Search Console accepts up to 500 index files per site.
  • An index can’t list another index. Search Console’s help is explicit: “A sitemap index file can’t list other sitemap index files, only sitemap files.”
  • UTF-8 only, and the namespace must be exactly http://www.sitemaps.org/schemas/sitemap/0.9 — the commonest typo is https.

Where the sitemap lives matters

A sitemap you don’t submit through Search Console only covers URLs inside its own folder: one at /blog/sitemap.xml can vouch for /blog/post but not for /pricing. And www.example.com and example.comare different hosts, so a sitemap mixing them is listing two sites. Fill in the sitemap’s own address above and the tool checks every URL against it.

Since Google retired its ping endpoint (“The sitemaps ping endpoint deprecation is complete.”), there are two ways left to tell Google a sitemap exists: submit it in Search Console, or list it on a Sitemap: line in your robots.txt. The robots.txt tester checks that line along with the rest of the file. If your sitemap carries hreflang alternates, the hreflang generator builds those entries with the language codes checked.

What a valid sitemap still can’t do

A sitemap is a list of suggestions. Google calls submitting one “merely a hint: it doesn’t guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site.” It helps Google find pages. It doesn’t make them rank, or even get indexed.

It also only works when the list is honest. Google’s advice is to “include the URLs in your sitemap that you want to see in Google’s search results” — so a URL that redirects, returns a 404 or carries noindexdoesn’t belong in it, however valid the XML around it. Finding those is a crawl, not a parse, which is what Site Audit does; the guide to which audit issues to fix first starts with exactly this class of problem.

Questions

How do I validate an XML sitemap?
Paste it into the tool above or upload the file — .xml, .xml.gz or .txt all work. It checks that the XML is well-formed, that the namespace, URLs and lastmod dates follow the rules Google publishes, and that the file is inside the 50,000-URL and 50MB limits. Every finding shows the line it's on. Nothing is uploaded; the checking happens in your browser.
Can I check a sitemap on a site I don't own?
Yes. Open the sitemap's URL in your browser, use View Source to see the raw XML, and paste it in. Copy from View Source rather than the page itself: many sitemap plugins attach a stylesheet that makes the browser show a table, and copying that gives you text, not XML.
Does Google use priority and changefreq?
No. Google's sitemap documentation says it ignores both. They are harmless to leave in, and other search engines may still read them, but time spent tuning them does nothing for Google. The tag that matters is lastmod, and only when it is accurate.
What date format does lastmod need?
W3C Datetime: either a date (2026-10-21) or a full timestamp with a timezone (2026-10-21T09:30:00+00:00 or …Z). A time without a timezone is invalid, and so is any day-first format like 21/10/2026. Search Console reports both as "Invalid date".
How big can a sitemap be?
50,000 URLs or 50MB uncompressed, whichever comes first. Past either, split it into several sitemaps and list them in a sitemap index, which can itself hold up to 50,000 sitemaps. Gzipping a sitemap shrinks the download but not the limit — the 50MB is measured uncompressed.
Can a sitemap index list another sitemap index?
No. Search Console's documentation is explicit that an index can list only sitemap files, never other index files, and it reports a nested index as an error. If you need more than one index, submit each of them separately.
Why does Search Console say my sitemap "Couldn't fetch"?
That status is about retrieving the file, not its contents, so no validator can diagnose it from a paste. Check that the sitemap URL loads in a private browser window, returns XML rather than an HTML error page, and isn't blocked by your robots.txt.
How do I submit a sitemap now that the ping URL is gone?
Two ways remain: submit it in Search Console's Sitemaps report, or add a Sitemap: line with its full URL to your robots.txt. Google retired the old ping endpoint in 2023, so scripts and plugins still calling it are doing nothing.
Will a sitemap get my pages indexed?
Not on its own. Google describes submitting a sitemap as merely a hint — it doesn't guarantee Google will download the sitemap or crawl what's in it. A sitemap helps Google find URLs; whether they're indexed depends on the pages themselves.
Why isn't there a sitemap generator here?
Generating a sitemap means crawling the whole site to find every URL, which is a different job from checking a file. Most CMSs and frameworks generate one already; this tool is for checking that the one you have is right.
Is this tool free?
Yes — no signup, no limit, and nothing leaves your browser. Gzipped files are decompressed locally, and we never fetch your sitemap or your site.

More free tools

A valid sitemap can still be full of URLs that don't work.

This checks the file. Site Audit crawls the site behind it and lists every page that returns an error, redirects or can't be indexed — the URLs that shouldn't be in a sitemap at all — plus the orphan pages nothing links to.

7-day free trial Cancel anytime