S SCHEMA.BIZ

Last updated:

Sitemap Checker

This sitemap checker reads an XML or text sitemap or a sitemap index, and can test a sample of its URLs.

Our server fetches the sitemap as SchemaBizBot (a site address means its /sitemap.xml, or else the first sitemap its robots.txt lists; .gz files are decompressed), then it's checked here in your browser.

How to use the sitemap checker

"Fetch a sitemap" takes the sitemap's address, or a site's address for its /sitemap.xml. When a site has no /sitemap.xml, the checker reads its robots.txt and checks the first sitemap listed there, says so above the results, and lists any others with a button to check each. Our server fetches the file as SchemaBizBot, decompressing it first when it's gzip (sitemap.xml.gz), and the file is checked in your browser, with the status, redirects and size of the fetch. "Paste a sitemap" checks XML or a text list of URLs in your browser only. A link such as /seo/sitemap-checker/?url=https://example.com/sitemap.xml runs the check when it opens.

"Try an example sitemap" loads a small shop's file with four mistakes: the second entry's <lastmod> has a time but no time zone, the third <loc> is a path rather than a full URL, the fourth is on another host (shop.example-shop.com), and the last lists the home page a second time. Its <changefreq> and <priority> get a note, since Google ignores both.

What it checks

  • The file. A <urlset>, a <sitemapindex> or a text file with one URL per line; the sitemap namespace; well-formed XML, with the line of the first broken tag; and every & escaped. An RSS or Atom feed is recognized, and an HTML page is reported as not a sitemap.
  • The limits. 50,000 URLs and 50 MB uncompressed per file, the same for an index. Our server reads up to 5 MB of a fetched file after decompression; for a larger one the checker says its counts cover that part.
  • Each entry. A <loc> that's a full URL under 2,048 characters, on the sitemap's host and protocol and below its folder; no duplicates; <lastmod> in W3C Datetime format and not in the future; <changefreq> and <priority> values. A problem found on many entries is listed once, with a count and the first five lines.
  • A sample of URLs. For a fetched sitemap, "Check 20 URLs" fetches 20 addresses spread over the list, 4 at a time, and reports each one that doesn't answer 200, redirects, is noindex (robots meta tag or X-Robots-Tag) or names another page as canonical. One our server couldn't fetch just then, because of too many checks in a short time, shows as "Couldn't be checked just now"; check again a minute later.
  • An index lists its sitemaps, each with a "Check this sitemap" button.

The sitemap rules that matter

The sitemaps protocol at sitemaps.org defines the format, and Google, Bing and other search engines read it. A minimal sitemap is a <urlset> in the sitemap namespace with one <url> per page; only <loc> is required:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/</loc>
    <lastmod>2026-11-02</lastmod>
  </url>
  <url>
    <loc>https://www.example.com/products/?color=blue&amp;size=m</loc>
    <lastmod>2026-10-28T09:15:00+00:00</lastmod>
  </url>
</urlset>

The second address shows the escaping rule: every value is entity-escaped, so & in a URL is written &amp;. The file must be UTF-8. Google asks for fully-qualified, absolute URLs, and uses <lastmod> when it's consistently and verifiably accurate.

A site with more than 50,000 URLs, or a file over 50 MB, splits its sitemap and lists the parts in a sitemap index. An index can list up to 50,000 sitemaps, which can be gzip-compressed:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://www.example.com/sitemap-pages.xml</loc>
    <lastmod>2026-11-02</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.example.com/sitemap-products.xml.gz</loc>
  </sitemap>
</sitemapindex>

Fetch an index and the checker lists its sitemaps, so you can check each in turn.

Common sitemap mistakes

  1. Listing URLs that aren't the canonical page. Redirects, parameter variants, noindex pages and pages whose canonical points elsewhere. List the final, canonical, indexable address.
  2. A lastmod that's always today. A generator that stamps every URL with the build time teaches Google to ignore the dates.
  3. Relative or wrong-host URLs. /shoes/ instead of https://www.example.com/shoes/, or http:// and www variants of the site the sitemap is on.
  4. Unescaped ampersands. One raw & makes the XML invalid, and a crawler may reject the whole file.
  5. Pages blocked by robots.txt. A sitemap URL that robots.txt disallows can't be crawled. Test a few in the robots.txt checker.
  6. Oversized files. More than 50,000 URLs or 50 MB uncompressed breaks the protocol's limits. Split the file and list the parts in an index.

Hreflang annotations can live in the sitemap too, as <xhtml:link> elements; the checker counts the entries that have them, and the hreflang checker checks the codes and the return links between them. For a sampled page's tags in detail, use the meta tag checker.

Frequently asked questions

FAQ

Where should my sitemap be, and how do crawlers find it?

At the site's root, such as https://example.com/sitemap.xml: Google says a sitemap affects only pages below its own folder unless you submit it in Search Console. Then list it in robots.txt with a Sitemap: line, which any crawler can read, and submit it in Google Search Console and Bing Webmaster Tools. The robots.txt checker lists the sitemaps a robots.txt names.

Does Google use changefreq and priority?

No. Google says it ignores both. It uses <lastmod> when the dates are consistently accurate, so set it to the date the page's content last changed, not the date the sitemap was generated. The checker notes the two tags without counting them as problems.

Can a sitemap list URLs on another domain or subdomain?

The sitemaps protocol says one host per sitemap, in the same protocol. Google accepts a sitemap with other sites' URLs only when you've verified ownership of every one of them in Search Console. The checker warns about each URL on another host or protocol than the sitemap's.

Why check a sample of URLs?

A sitemap tells search engines which pages you want crawled and indexed. A URL that redirects, answers 404, is noindex or names another page as its canonical sends a mixed signal and wastes crawls. Checking 20 URLs spread across the file finds a template or a generator that lists the wrong addresses, without fetching all of them.

Does the checker store my sitemap?

A pasted sitemap is checked in your browser and never leaves it, and its URLs aren't fetched. For a sitemap address, our server fetches the file as SchemaBizBot (decompressing a .gz file) and sends it back to your browser; when you ask for the sample, it fetches those 20 pages the same way. Like every tool on the site, the checker records what kind of check ran: counts, the kind of file and problem codes, never an address from the sitemap. The sitemap's own address is recorded without its query string. See the privacy policy.