Sitemap.xml Validator

A sitemap.xml file lists all important pages on your website, helping search engines discover and crawl them efficiently. It provides metadata like last modification dates and change frequency to guide search engine crawlers.

Having a well-structured sitemap is especially important for large sites, new sites, or sites with pages that aren't well-linked through internal navigation. It's worth being clear about what a sitemap does and doesn't do: it helps search engines find your pages. It has no influence on how those pages rank once found.

For a typical local service business, the pages most likely to benefit are the ones buried in your structure — individual service area pages, older blog posts, and anything you added after the site was built and never linked from the main navigation.

That it's genuinely XML. The most common failure is a server returning an HTML error page at /sitemap.xml. If that's happening, search engines are getting nothing, and you'd never know from looking at your site.

Structure and namespace. A valid sitemap needs a <urlset> root and the sitemaps.org namespace declaration. Miss either and the file may be rejected.

URL count against the limits. 50,000 URLs and 50MB uncompressed are the hard caps. Beyond those you need a sitemap index pointing at multiple files.

Whether lastmod dates are present. This is the one optional field genuinely worth having, because it tells crawlers what changed since they last visited. It only helps if the dates are honest — a sitemap that claims every page changed today teaches Google to ignore the field entirely.

Priority and changefreq get reported for completeness, but don't spend time tuning them. Google has said it largely disregards both, precisely because most sites mark everything as maximum priority.