Skip to content
EnterraHost
Products
Tools
Hosting Email Support Client Area Find a domain
Easy utilities

Sitemap Checker

Checks a sitemap against the protocol and tells you what to change. Parse errors, limit breaches, bad dates and broken index entries, each with the fix.

Give it a domain and it checks any Sitemap line in robots.txt, then the usual addresses starting with the root. Or paste the full address of a sitemap anywhere on the site.

Email me this result

The same result, sent to your inbox.

We use the address to send this result. It is not stored after the message goes out, and nothing is added to a list unless you tick the box.

Need somewhere to put the site? Hosting from $4.95 a month, with free DNS on every domain you own.

How the sitemap is found

The root first, then robots.txt, then the usual suspects.

Nearly every sitemap is at the site root, either /sitemap.xml or whatever your platform generates by default. That is where a crawler looks first, and it is where this tool ends up on the average site.

A Sitemap line in robots.txt is checked before that guess, because a declaration is a statement about the site and a guess is not. It is what gets a sitemap found when it lives somewhere else, such as a platform that generates it at a subpath.

With nothing declared, the usual addresses are tried in turn and the first one that returns a real document is the one reported. That starts at the root /sitemap.xml, then the WordPress variants such as /wp-sitemap.xml and /sitemap_index.xml, then a compressed or plain text sitemap. The result says which address answered and whether anything declared it.

A declared sitemap on a different host is reported rather than fetched. A sitemap there is only valid when it is verified in the same search property as this one, and following it would mean this tool requesting any address the site owner cared to name.

The failure nobody notices

A sitemap checker and a sitemap tester do the same job: fetch the sitemap.xml the crawler fetches, parse it the way the crawler parses it, and tell you what would be ignored. This page validates the XML itself and tests the entries that matter, showing the fix beside each problem.

A sitemap that does not parse is silent.

A sitemap is read as a single document. If one character in it is wrong, the parser stops and reports nothing at all, so every URL the file listed is lost rather than merely mis-described. The site looks like it has no sitemap, which is the opposite of the truth and points at the wrong problem.

What breaks it

An unescaped ampersand in a query string, an unclosed tag, or a character that is not valid in the declared encoding. Generating the file by hand or by string concatenation is what usually causes it, because both skip the escaping an XML writer would do.

What a fix looks like

Write & where you meant a bare ampersand, and build the file with an XML writer rather than a string. This tool reports the line number the parser objected to, which is the quickest way to find the one character that matters.

Two limits, one file each

50,000 URLs and 50 megabytes.

A single sitemap may hold up to 50,000 URLs and may be up to 50 MB uncompressed. Past either limit the file is invalid and the whole thing is discarded, not truncated. Larger sites split the URLs across several sitemaps and list those in a sitemap index.

An index has its own failure mode. Each loc in it has to resolve to a real sitemap, and one dead child takes every URL inside it out of the picture without anything reporting an error. This tool fetches the children on the same host and reads each one.

What this does not do

This validates the document, not the pages.

A sitemap can be perfectly written and still list URLs that 404, redirect or carry a noindex tag. That is a different check against real requests, and it lives in the next tool along.

The full walkthrough is in how a sitemap is validated, including the fields Google ignores and the URLs that vanish.

Discovery

There is a fourth way to find a sitemap, and it is the one a machine uses.

A sitemap is normally found three ways. You can paste the address, declare it in robots.txt with a Sitemap line, or leave it at one of the conventional paths. A Link response header is a fourth, and it is the one an automated reader acts on without guessing anything.

The header rides on the page response rather than on the sitemap itself, because a static XML file carries no headers worth reading. This tool fetches the site root to look for it, and reports what it finds.

Link: </sitemap.xml>; rel="sitemap"

It also checks for /llms.txt, the plain text companion a reader looks for beside a sitemap. That file describes what the site is and which pages are worth reading. Neither the header nor the file is required by anything, and a site without them is not broken. They are how a machine finds the file without being told where it is.

A header naming a file that does not resolve is worse than no header, because a reader acts on it. The two are therefore checked separately, and this tool reports it when one promises something the other cannot deliver.

Questions

Questions about sitemap validation.

Can I get the result by email?
Yes. Run the check, then press the paper plane beside the result and give it an address. The message carries the same figures the page shows, any table the result produced, and on the map tools the diagram itself as an attached vector file. Nothing is stored unless you tick the box asking to hear about new tools and trials, and if you do, the message carries a link that removes you again.
What is a Link header for a sitemap?
A line in the response headers that names the sitemap, written Link: </sitemap.xml>; rel="sitemap". Search crawlers do not need it, because they find a sitemap through robots.txt and the conventional addresses. An automated reader that is not a search crawler uses it, because it is the route that does not involve guessing a path. It is sent on the page response rather than on the sitemap, since a static XML file carries no headers of its own.
What is an llms.txt file?
A plain text file at the root of a site, written in Markdown, that describes what the site is and points at the pages worth reading. It is a convention rather than a standard, no crawler is obliged to read it, and a site without one is not doing anything wrong. It answers a question a sitemap does not, which is what the site is for rather than only which URLs exist. This tool checks whether one is there and whether anything advertises it.
What is the difference between a sitemap and a sitemap index?
A sitemap is a urlset, one flat list of pages. A sitemap index is a list of other sitemaps, each one a loc pointing at a separate file. An index is how a large site stays inside the 50,000 URL limit per file, and a loc inside an index has to resolve to a real sitemap or everything below it is invisible.
Why does a malformed sitemap matter if the pages are fine?
Because the file is read as one document. If it does not parse, nothing inside it is read at all, so every URL it lists is lost rather than merely misdescribed. A single unescaped ampersand in a query string is enough to do it, and the symptom is a sitemap that appears to contain nothing.
Is lastmod required?
No, it is optional, and a sitemap without it is valid. It is worth adding because it is the signal that lets a crawler skip pages which have not changed since it last looked. If you do use it, use a real date. An invalid or future date is ignored at best and makes the field untrustworthy at worst.
Does a sitemap guarantee my pages get indexed?
No. A sitemap is a hint about what exists, not an instruction to index it. It does not override a noindex tag, it does not lift a robots.txt disallow, and it does not make a thin page worth ranking. It helps a crawler find pages it might otherwise miss.
What are the sitemap size limits?
One sitemap may list up to 50,000 URLs and may be up to 50 MB uncompressed. Past either limit the file is invalid, so a larger site splits its URLs across several sitemaps and lists those in a sitemap index.
Should the sitemap be listed in robots.txt?
It helps, but it is not required. Nearly every sitemap sits at /sitemap.xml and a crawler finds that by looking. A Sitemap line is what gets a sitemap noticed when it lives somewhere else, such as a platform that generates it at a subpath. A missing line is therefore a note rather than a fault.
Does this check whether the pages in my sitemap work?
No, and that separation is deliberate. This validates the document. The Broken Link Checker crawls the pages and reports broken links, redirects, blocked URLs and pages that should not be in the sitemap at all.
Is a sitemap checker the same as a sitemap validator?
The names describe one job. Checker, validator and tester all mean reading the XML, comparing it against the sitemap protocol and reporting what breaks. This one also resolves every entry inside a sitemap index, so an index pointing at a file that is not there is reported rather than passed.
Does this work on a Google sitemap, or only the standard one?
There is no separate Google sitemap. The format comes from the sitemaps protocol, which Google published and every major crawler reads, so a document that passes here is the document Google is asking for. What differs between search engines is which optional fields they act on, not the XML itself.