NeovaAdvanced SEO Platform

XML Sitemap Checker: How to Validate Your Sitemaps and Fix What They List

An XML Sitemap is a list of the URLs you want search engines to crawl. It only helps if the list is true: every URL should answer 200, be indexable and be the canonical version, and every page that matters should be on it. An XML sitemap checker reads the files, fetches what they list and compares it with what a crawl of the site finds.

Crawling and Indexingxml sitemap checkerUpdated November 21, 2026By the Neova team

What an XML Sitemap Checker Does

A checker works on two levels. First the files themselves: can they be fetched, are they well-formed XML in a sitemap format, and do they stay within the size limits? Then the URLs inside them: what each one returns when requested, whether it is indexable, and whether it matches what the site's own links point to.

The second level is where most of the value is. A sitemap that validates perfectly can still list thousands of redirects, or leave out half of the product pages. You only see that by fetching the URLs and comparing them with a crawl.

How XML Sitemaps Work

The format is defined by the sitemaps.org protocol, which Google, Bing and other search engines support. A sitemap is a urlset with one url entry per page:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/shoes/running</loc>
    <lastmod>2026-11-12</lastmod>
  </url>
</urlset>

Large sites split their URLs over several files and list those files in a sitemap index:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap><loc>https://www.example.com/sitemap-products-1.xml</loc></sitemap>
  <sitemap><loc>https://www.example.com/sitemap-blog.xml</loc></sitemap>
</sitemapindex>

Search engines find sitemaps through a Sitemap: line in robots.txt, which takes a full URL and can appear more than once, or through submission in Search Console and Bing Webmaster Tools. Google's sitemaps overview explains when a site benefits from one: large sites, new sites with few outside links, and sites with a lot of media or news content. SEO ProCheck's XML sitemaps reference covers image, video and news sitemaps too.

Sitemap Limits and Format Rules

RuleLimit
URLs per sitemap file50,000
File size, uncompressed50 MB (52,428,800 bytes)
Sitemaps per sitemap index50,000
URL lengthUnder 2,048 characters
EncodingUTF-8, entities escaped
URL formAbsolute, crawled as listed
ScopeSame host, at or below folder

The 50 MB limit applies even when the file is served as gzip. A URL outside the sitemap's folder or host is allowed only when that host's robots.txt declares the sitemap. These come from the protocol and from Google's guide to building and submitting a sitemap. Google's page on large sitemaps explains the index file. One thing that changed: Google retired its unauthenticated sitemap ping endpoint in 2023, as its announcement explains, so submit through robots.txt or Search Console instead.

lastmod, changefreq and priority

Google ignores changefreq and priority. It uses lastmod as a hint for when to recrawl a known URL, but only when the dates are consistently accurate. A lastmod that changes on every page every day, or that moves when only the footer year changes, teaches Google to stop trusting it.

Keep lastmod for real changes to the main content, structured data or links, and write it in W3C date format, such as 2026-11-12 or a full timestamp with a time zone. If you cannot tell when a page really changed, leaving lastmod out is better than guessing.

The Most Common XML Sitemap Errors

Most sitemap problems are not about XML. They are URLs that should not be on the list, or pages that should be and are not:

Listed URLBelongs in sitemapFix
200, indexable, self-canonical✓Keep
Redirects (3xx)–List the final URL
404, 410, 5xx–Remove
Noindex–Remove, or drop noindex
Canonical names another URL–List the canonical
Blocked by robots.txt–Remove, or allow
http:// on an https site–Use https
Wrong host (www or not)–Use the canonical host

Two problems a table of listed URLs cannot show: missing pages, often a whole template the CMS never added, and empty or broken files that return an error, an HTML page or no URLs at all. The robots.txt tester guide shows how to check blocked URLs, and SEO ProCheck's XML sitemaps FAQ covers the rest.

Sitemaps, Crawls and Orphan Pages

Comparing the sitemap with a link crawl answers two questions at once. URLs the crawl found but the sitemap does not list are pages your generator misses. URLs the sitemap lists but no internal link reaches are orphan pages. The orphan pages guide covers what to do with each.

We ran this on our own site. The full Neova crawl of seoprocheck.com on October 17, 2026:

seoprocheck.com, Oct 17, 2026Count
URLs fetched10,222
HTML pages answering 2004,561
URLs in the XML sitemaps1,835
Reached by the crawl, in no sitemap2,727
In a sitemap, reached by no link1
Crawl completeness99.98%
Time61 minutes

The sitemaps listed 1,835 URLs while the links reached 2,727 more, so the generator was the gap, not the site. The one orphan was a single page to link or retire. This comparison only means something because the crawl ran to 99.98%: a crawl stopped at a URL limit makes linked pages look as if only the sitemap knew them.

How to Check Your XML Sitemaps

  1. Find every sitemap. Read the Sitemap lines in robots.txt, try /sitemap.xml and /sitemap_index.xml, and check what Search Console's Sitemaps report lists.
  2. Validate the files: status 200, readable gzip if compressed, well-formed XML, within the limits.
  3. Fetch every listed URL and record its status code, robots directives and canonical.
  4. Crawl the site from the home page to the end and compare the two lists.
  5. Fix the generator, not the file. Most sitemaps are built by the CMS or a plugin, so a hand edit will be overwritten on the next build.
  6. Resubmit and watch. Check the Sitemaps report for errors, and crawl again on a schedule so a broken build is caught early.

Sitemap hygiene is one step of the technical SEO audit checklist, and on large sites a clean sitemap helps search engines spend their crawl budget on pages that count.

Check XML Sitemaps With Neova

Neova reads the XML Sitemaps robots.txt declares, plus any you add in Settings, and crawls the URLs they list after the pages the links reach. Pages only the sitemaps list are fetched as a separate step and counted apart. The Sitemaps category then shows what the sitemaps list against what the crawl found. You can also crawl the XML Sitemaps on their own, or paste a list of URLs into List Crawl. Some of the checks:

Neova keeps every XML Sitemap its crawls read, and can export a new XML Sitemap of the indexable pages it found. See Features or download Neova.

Questions

How do I check if my XML sitemap is valid?

Fetch it and confirm it returns 200, parses as XML in the sitemap format and stays within 50,000 URLs and 50MB uncompressed. Then fetch the URLs it lists: a valid file can still list redirects, errors and noindex pages.

How many URLs can an XML sitemap have?

Up to 50,000 URLs and 50MB uncompressed per file. Larger sites split their URLs over several sitemaps and list them in a sitemap index, which can itself list up to 50,000 sitemaps.

Should every page be in the XML sitemap?

Every indexable, canonical page you want in search results should be. Leave out redirects, error pages, noindex pages, canonicalized duplicates and URLs blocked by robots.txt.

Does Google use priority and changefreq?

No. Google ignores both. It uses lastmod when the dates are consistently accurate, so keep lastmod for real content changes.

Can I still ping Google with my sitemap?

No. Google retired the sitemap ping endpoint in 2023. Declare the sitemap in robots.txt and submit it in Search Console instead.

Take this with you

The assistant links open with a question about this page already written.

Crawl your site with NeovaThe Free plan runs every check on Mac, Windows and Linux. No credit card required.

Keep Reading