Free XML Sitemap Checker

Free · In your browser

Free XML Sitemap Checker

Paste a sitemap or a sitemap index to validate the sitemaps.org protocol: loc values, absolute URLs, duplicates, lastmod dates, host and protocol consistency, and the 50,000 URL / 50 MB limits.

This is a practical checklist, not a Google ranking score. Google ignores priority and changefreq, and the old sitemap ping endpoint was deprecated in 2023.

Privacy: Paste mode stays in your browser. Fetch only requests a sitemap on the same site as this page. Other origins cannot be read in the browser (CORS), and this tool does not use a proxy.
Blogger helper

Blogger generates two XML sitemaps automatically: sitemap.xml for published posts and sitemap-pages.xml for static pages. The default robots.txt already lists both. An Atom feed can also be submitted to Google as a sitemap, but it usually only includes recent posts, so the two XML sitemaps are the better default.

Fetch works only when this tool and the sitemap share the same origin, for example /sitemap.xml on this site. For any other website, open the sitemap, copy the XML, and paste it below. Paste the full XML, including the xml declaration and the urlset or sitemapindex root.

No sitemap yet Paste sitemap XML and choose Check sitemap, fetch a same-origin file, or load the sample sitemap to see how results look. The sample is a demonstration, not your website.

What this free XML sitemap checker does

This page is a free, in-browser XML sitemap checker. You paste a sitemap or a sitemap index, and the tool checks whether the file is well-formed XML and whether it follows the sitemaps.org protocol: a urlset or sitemapindex root, the standard namespace, a loc for each entry, absolute http or https URLs, duplicates, lastmod date formats, mixed hosts or schemes, and the 50,000 URL / 50 MB limits.

It does not crawl the listed URLs, and it cannot log into Search Console. A clean report means the file looks valid, not that Google has indexed every URL. Google has said that submitting a sitemap is only a hint, and that it ignores the priority and changefreq fields. The sitemap ping endpoint was deprecated in June 2023 and now returns a 404 error.

For a broader on-page check, use the free SEO audit tool. For heading structure, use the free heading tag checker. The fuller writing guide for this topic is How to Check and Fix Your XML Sitemap for Better SEO (Complete 2026 Guide).

What the tool checks

Diagram of XML sitemap checks: structure, loc URLs, host and protocol consistency, lastmod dates, size limits, and a note that Google ignores priority and changefreq
The checker validates the sitemaps.org protocol and consistency. Google ignores priority and changefreq.

The analysis of a pasted file stays in your browser. Fetch is the only optional network request, and it is limited to a sitemap on the same origin as this page.

  • Well-formed XML, and a urlset or sitemapindex root.
  • The standard namespace, http://www.sitemaps.org/schemas/sitemap/0.9.
  • A loc value on every entry, written as an absolute http or https URL (not a relative path).
  • Duplicate loc values, mixed hosts, mixed http/https, and mixed www / non-www hostnames.
  • lastmod values in a supported W3C Datetime format, and dates that are clearly in the future.
  • The 50,000 loc and 50 MB uncompressed limits documented by Google and sitemaps.org.
  • A note, when priority or changefreq is present, that Google ignores both fields.
  • A searchable URL table, with CSV export, and a child-sitemap list when you paste an index.

The tool does not request each listed page to see if it returns 200 or 404. That would require crawling, which a page in your browser cannot do across the web without a proxy. Use the URL list, then confirm important URLs in Search Console or with a live visit.

How to use it

Six steps for using the free XML sitemap checker: find the sitemap, paste or fetch it, read the score and URL table, fix and retest, confirm in Search Console, and skip the deprecated ping endpoint
Paste the live XML, or fetch a same-origin sitemap. Other sites must be pasted because of CORS.
  1. Find the live sitemap. Try /sitemap.xml, and look for a Sitemap line in robots.txt.
  2. On Blogger, also open /sitemap-pages.xml. Posts and static pages are split across those two files, and both already appear in the default robots.txt on a typical Blogger site.
  3. Paste the full XML into the box. If this checker is published on the same site as the sitemap, you can use Fetch instead.
  4. Choose Check sitemap. Read fail and warning cards first, then search or export the URL table.
  5. Fix the issue at the source, publish, and paste the live file again.
  6. Confirm the same URL in the Search Console Sitemaps report. Do not ping the old endpoint.

Browsers block a page from reading a sitemap on another site (CORS). This tool does not bypass that rule with a proxy. When Fetch is blocked, open the sitemap URL, copy the XML, and paste it.

How to read the score and the URL list

How to read the sitemap checker score, with pass, warning, fail, and info results, plus notes about the URL table, sitemap indexes, and Blogger sitemap files
Read the items and the URL list, not only the score. A sitemap is a hint for crawling, not a guarantee of indexing.

The 0–100 number is a weighted summary of the checks. Pass items give full weight, warnings give half, and fails give none. Info items, including the note that Google ignores priority and changefreq, do not drag the score down.

Read the cards and the table, not only the number. A score of 100 means the file looks consistent with the protocol, not that every URL is indexed. Category bars show Structure, URLs, Consistency, Dates, and Limits. On a sitemap index, the table lists child sitemap files rather than page URLs. Those child files should be checked separately.

You can copy a plain-text report, export the table as CSV, or print the results. The report is a snapshot of this check, not a certificate.

Blogger notes

Blogger generates the XML for you. You do not upload a sitemap file. The usual addresses are:

  • /sitemap.xml — published posts
  • /sitemap-pages.xml — static pages, including About, Contact, and tool pages

If a blog has a large number of posts, Blogger may also serve additional pages such as sitemap.xml?page=2. An empty urlset on a later page usually means that all of the posts already fit on an earlier page. Google also accepts Atom and RSS feeds as sitemaps, and a Blogger Atom feed can still be submitted, but a feed often lists only recent posts. For a complete picture, start with the two XML sitemaps and the default robots.txt lines.

After you publish or update a post, give Blogger a moment to refresh the sitemap, then paste the live XML again. Search Console still has to recrawl the file; submitting it is not an instant index request.

Limits of this tool

The checker cannot see whether a URL is in Google’s index, whether a listed page returns an error, or whether lastmod matches the real content change. It cannot submit a sitemap for you. It cannot fetch another site’s sitemap. And a high score does not improve rankings by itself. Useful URLs, a page that can be crawled, and an accurate lastmod still matter more than this number.

Related guides on Free Seo Lab

Frequently asked questions

Does a high score mean the pages will be indexed?

No. The score is a checklist summary for this file. Google has said that a sitemap is only a hint. Use the Search Console Sitemaps report and the Page indexing report to see what happened after the file was read.

Why can’t I fetch another website’s sitemap?

Browsers do not allow a page on one site to read a file on another site. That is a normal security rule (CORS). This tool does not use a third-party proxy. Paste the XML instead. Fetch is reserved for a sitemap on the same origin as this page, such as /sitemap.xml when the tool is published on the same site.

Is my sitemap sent to this site?

No. A pasted file is read in your browser. Fetch, if you use it, requests only that same-origin URL.

Should I add priority and changefreq?

Not for Google Search. Google has said it still does not use those fields. lastmod is the optional date worth keeping accurate, and only when it reflects a significant change.

Can I still ping Google when the sitemap changes?

Not through the old ping endpoint. Google deprecated it in 2023, and those requests now return 404. Use a Sitemap line in robots.txt, and submit or check the file in Search Console.

Why does a Blogger sitemap look like Atom in the HTTP header?

Blogger may serve sitemap.xml with an Atom content type even though the body is a standard urlset. This checker reads the XML body, not the content-type header. If the body is a urlset with loc values, the file can still be a valid sitemap.

Start with the live sitemap URL, paste the XML, and fix fail items first. Then confirm the same file in Search Console, and use the longer sitemap guide when you want the writing and workflow behind the flags.

Post a Comment

Thank you so much for your comment we will back to you soon