map Technical SEO

XML Sitemap Checker and Validator

Enter a sitemap URL in the tool on this page and it fetches the file, confirms it parses as XML, and reports whether it is a urlset or a sitemapindex. From there it looks at the details that quietly break sitemaps: a missing or wrong namespace, relative URLs, malformed lastmod dates, and listed pages that redirect, error out, or sit behind a robots.txt disallow. Keep in mind that a sitemap is a crawl hint. A clean file helps Google discover URLs, but it does not force crawling, indexing, or better rankings. Use this public check for structure and hygiene, then confirm processing in your own Search Console sitemap report.

build_circle Try the free tool

What a valid XML sitemap contains

A standard sitemap opens with a urlset root element declared in the sitemaps.org 0.9 namespace. Inside it, each url entry needs a loc holding a full absolute address, such as https://www.example.com/pricing/, not /pricing/. The lastmod field is optional, but when present it should use W3C datetime format, either a plain date like 2026-11-06 or a full timestamp with a time zone. Larger sites often split URLs across several files and list them in a sitemapindex, whose sitemap entries point to each child file.

Common sitemap errors and what they usually mean

The checker groups problems into structure and content. Structure errors include a server returning an HTML page or login screen instead of XML, a misspelled or missing namespace, unclosed tags, and a sitemap index pointing at child files that return 404. Content errors are about the URLs inside: relative paths, http entries on an https site, pages that only redirect, pages returning 4xx or 5xx, URLs disallowed in robots.txt, and lastmod values that are not real dates. A file that exceeds the URL or size limit is another frequent cause of a sitemap being only partly read. Most of these trace back to a CMS plugin setting or a stale export.

This checker vs the Search Console sitemap report

Google Search Console is the source of truth for site owners. Its sitemap report shows whether Google fetched your file, when it last read it, and how many discovered URLs it recorded. This free checker answers a different question from the outside: is the file itself well formed and tidy right now? It works on any public sitemap, including a competitor's or a client's before you have access, and it is useful for catching problems before you submit. When the two disagree, trust Search Console for what Google actually processed, and use this tool to find the file-level issue behind it.

Will a clean sitemap get my pages indexed?

Not on its own. Search engines treat a sitemap as a list of suggestions about which URLs exist and which changed recently. A perfectly valid file can still contain pages Google decides not to index because of thin content, duplication, or a canonical pointing elsewhere. What a clean sitemap does is remove avoidable friction, so crawlers are not wasting requests on redirects, dead pages, or blocked paths. If you need to know whether a specific URL is in the index, that is a separate check.

Questions

Questions we get asked

Can I check a sitemap index file?

Yes. If the root element is sitemapindex, the checker identifies it as an index and lists the child sitemaps it references. Run each child file through the tool as well, since the index can be valid while an individual child is broken or missing.

Which URLs should be included in a sitemap?

Only canonical, indexable pages that return a 200 status. Leave out redirects, error pages, noindex pages, parameter duplicates, and anything blocked by robots.txt. Including them sends mixed signals and dilutes the usefulness of the file.

Is lastmod required, and what should it say?

It is optional. If you include it, it should reflect the last meaningful change to the page content, in W3C datetime format. Setting every lastmod to today's date on each build makes the field unreliable, so search engines may start ignoring it.

How is this different from a broken link checker?

A broken link checker crawls the links on your pages to find dead destinations. The sitemap checker reads only the sitemap file, validates its format, and samples the status of URLs listed in it. They catch different problems and work well together.

How do search engines find my sitemap?

The two usual routes are a Sitemap: line in your robots.txt file and direct submission in Google Search Console or Bing Webmaster Tools. Declaring it in robots.txt also helps other crawlers that read that file.

Free audit

Want your sitemaps and crawl setup reviewed together?

Request a free audit and we will look at sitemaps, robots rules, redirects, and indexing signals as one system.

Get a Free Audit