Free sitemap checker

Sitemap checker

Validate your XML sitemap, then test a sample of the URLs in it for errors, redirects, noindex and canonical tags: the problems that keep listed pages out of Google.

Free, no sign-up. Enter a domain and it finds the sitemap through robots.txt.

Updated

A sitemap checker fetches your XML sitemap the way a search engine does and tests it against the sitemaps protocol and Google’s rules: the HTTP status, the content type, whether the XML is valid, the 50,000-URL and 50MB limits, and whether robots.txt points to it. This one goes a step further. It also fetches an even spread of up to 50 of the URLs your sitemap lists and checks whether each one is really indexable, because a perfectly valid sitemap full of redirects, noindex pages and non-canonical URLs is the more common problem.

What the sitemap checker tests

CheckWhat it looks for
HTTP statusThe sitemap answers 200. A 404, 403 or 5xx, or a redirect, is reported, with the URL it redirects to.
Content typeServed as application/xml or text/xml. A text/html page at the sitemap URL usually means the site returned its home page instead.
XML validityOne <urlset> or <sitemapindex> root with the sitemaps namespace, balanced tags, no unescaped & and nothing before the XML declaration. Errors come with a line number.
Sitemap index and gzipFollows an index to its child sitemaps (up to 20) and unzips .gz files. Flags a nested index and a .gz file that isn’t really gzipped.
Size limitsAt most 50,000 URLs and 50MB uncompressed per file, and 50,000 sitemaps per index.
robots.txtWhether robots.txt lists this sitemap, lists a different one, or blocks Googlebot from fetching it.
lastmodThe share of URLs with a <lastmod> date, dates that aren’t in W3C format, and dates in the future.
DuplicatesURLs listed more than once, within a file or across child sitemaps.
URLs on another hostURLs whose host or protocol differs from the sitemap’s, such as http:// URLs in an https:// sitemap, or a missing www.
Status of each sampled URLUp to 50 URLs spread evenly across the whole sitemap: 4xx and 5xx errors, and every redirect with where it lands.
noindexA noindex in the robots meta tag or the X-Robots-Tag HTTP header of each sampled page.
CanonicalA canonical tag that points to a different URL than the one listed.
Blocked URLsSampled URLs that robots.txt blocks for Googlebot.

Why it tests the URLs, not just the XML

Most sitemap validators stop at the file: is the XML well-formed, is it under the limits. Those problems are real but rare, because sitemaps are written by plugins that get the XML right. What plugins get wrong is which URLs go in. Google’s sitemap guidelines say to list only the canonical URLs you want in search results, and Search Console flags the rest in the Page indexing report:

The sample is spread evenly through the whole list, not taken from the top, so on a directory with separate sitemaps for listings, cities and categories it covers every page type. When one template is wrong, say every expired listing has a noindex, it shows up in the sample even if that template is only a fifth of the sitemap.

How to read the results

LabelMeaning
✕ ProblemSomething Google reports as an error or that stops the sitemap, or the URLs in it, being used: an HTTP error, invalid XML, a broken limit, noindex or blocked URLs.
! WarningWorks, but costs you something: redirects, canonicals pointing elsewhere, duplicates, missing lastmod dates, a missing robots.txt line.
i NoteWorth knowing, not necessarily wrong, such as robots.txt listing a different sitemap.
✓ PassedChecked and fine.

The URL sample counts are out of the URLs tested, not the whole sitemap. If 6 of 50 sampled URLs redirect, expect roughly 12% of the sitemap to redirect, and look at which kind of URL they are to find the template or plugin setting behind them.

This checker vs Search Console

Use both. This checker shows the state of the file and its URLs right now, in one run, without access to the site’s Search Console. Search Console’s Sitemaps report is the authority on what Google itself managed to read, and when; see sitemap could not be read for its messages.

One limit to keep in mind: this checker fetches as DirectoryLensBot, not as Googlebot. If a firewall, CDN or security plugin blocks only Googlebot, the sitemap will pass here and still show “Couldn’t fetch” in Search Console. The live test in the URL Inspection tool fetches with Google’s own crawler and is the check for that.

Limits of the free checker

Fixing what it finds

Sitemaps on directory websites

A directory’s sitemap is mostly listings, and listings change: they expire, merge, move city or lose their owner. Every one of those leaves a URL that may now redirect, return 404 or carry a noindex, and the sitemap plugin often keeps listing it. Run the checker on the listings sitemap after any bulk import, cleanup or plugin update, and keep listings, cities and categories in separate sitemaps so you can test them one at a time. The page indexing issues guide explains what Google does with each kind of URL.

Check every sitemap every day

The checker is a one-off test. DirectoryLens does the ongoing version from your Search Console connection: the Sitemaps tab in Google indexing re-reads every sitemap you submitted each day, follows indexes, unzips gzipped files, shows URL counts per sitemap over time, lists any sitemap it couldn’t load, and alerts you when a sitemap or the total loses 20% or more of its URLs within a week. Those sitemap URLs then feed daily checks with Google’s URL Inspection API, so you see how much of each page type Google has actually indexed.

Questions

How do I check if my sitemap is valid?

Enter its URL, or just your domain, in the sitemap checker above. It fetches the file, checks the status code, content type, XML structure and size limits, follows a sitemap index to its child sitemaps, and tests a sample of the URLs listed. Then submit the sitemap in Search Console, whose Sitemaps report shows whether Google could read it.

Is the sitemap checker free?

Yes. There’s no sign-up and nothing is stored. Each visitor can run 5 checks every 10 minutes.

What is the maximum size of an XML sitemap?

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

Why does my sitemap pass here but Search Console says Couldn’t fetch?

This checker fetches as DirectoryLensBot. If a firewall, CDN or security plugin blocks only Googlebot, the file loads here but not for Google. Test it with the live test in URL Inspection. Google can also show Couldn’t fetch for a while simply because it hasn’t fetched the sitemap yet.

Do I need to list my sitemap in robots.txt?

It isn’t required if you submit it in Search Console, but it helps Bing and other crawlers find it. Add a line like Sitemap: https://www.example.com/sitemap.xml anywhere in robots.txt.

Should a sitemap include redirected or noindex URLs?

No. List only the canonical URLs you want indexed, each returning 200. Redirects, noindex pages and URLs whose canonical points elsewhere are reported in Search Console and blur which URL you want shown.

How often should I test my sitemap?

After any change to the site’s structure, a plugin update, a bulk import or a migration, and whenever Search Console reports a sitemap error. DirectoryLens re-reads submitted sitemaps every day if you want it checked continuously.

Check every sitemap, every day.

Connect Search Console and DirectoryLens re-reads your submitted sitemaps daily, alerts you when one fails or shrinks, and shows how much of each page type Google has indexed.

Explore the live demo →

5 days free · no card needed · ends on its own