Sitemap Analyzer
Audit, Fix & Build sitemap.xml

It reads the sitemap and reports how many URLs it lists, unique and duplicate URLs, the oldest and newest lastmod, how fresh each page is, site sections and URL depth, file downloads such as PDFs and ZIPs, hosts and http/https use, image, video, news and hreflang entries, and changefreq and priority values. The validator checks the XML, the namespace, required tags, URL format, the 50,000 URL and 50 MB limits, date format, robots.txt conflicts and more, scores the sitemap out of 100, and says what to do about each problem. Check the pages then fetches a sample of the listed pages to confirm they load, can be indexed and name themselves as canonical.

Paste any page of the site and it checks /sitemap.xml at the root, the standard location. A URL ending in .xml or .xml.gz is analyzed as-is, so sitemap_index.xml or a sitemap in a subfolder works too. If /sitemap.xml is missing, it shows the error and also checks robots.txt Sitemap: lines and common locations such as sitemap_index.xml and wp-sitemap.xml, and offers any it finds.

Usually the sitemap lives somewhere other than /sitemap.xml - the analyzer lists any it finds in robots.txt. Other causes: the server returns an HTML page (often a "not found" page with status 200) to non-browser requests, a firewall blocks automated requests, or the file is larger than the 10 MB the proxy can fetch. In those cases, use "Paste or upload XML instead".

It fetches a sample of the pages in the sitemap - 25 to 250, spread evenly across the site's sections - and reports each page's HTTP status, whether it is marked noindex, whether its canonical points to a different URL, its HTML size and its response time. It then looks up the size of every file the pages link to without downloading it. Errors, noindex pages and canonicals that point elsewhere join the validator and the score, because a sitemap should list only pages that load and can be indexed. Response times are measured through the RJL.io proxy, so compare pages with each other rather than reading them as your visitors' load time.

File downloads counts the files listed in the sitemap itself, and most sites list only pages - the ZIP, PDF and installer links sit on those pages. That is fine: a download does not need to be in the sitemap unless you want it in search results on its own. Click Check the pages and the analyzer reads a sample of your pages and lists every file they link to, with its type, its size and whether the sitemap lists it.

A copy with duplicates removed, relative paths turned into full URLs, spaces and special characters encoded, #fragments and URLs on other hosts removed, dates rewritten in the W3C format (or removed when they are not dates or are in the future), invalid changefreq and priority values dropped, the correct namespace and an XML declaration. Image, video, news and hreflang entries are kept. Over 50,000 URLs it is split into several files with a sitemap index, downloaded as a ZIP.

No. Google ignores both, and Bing gives them little weight. Only lastmod influences crawling, and only when it is consistently accurate - so a lastmod that is just the build time on every page is worse than none. The analyzer flags dates that look auto-generated.

The W3C Datetime format: a date such as 2025-03-01, or a date and time with a time zone such as 2025-03-01T09:30:00+00:00. Formats like 03/01/2025 or "March 1, 2025" are invalid, and dates in the future make search engines distrust all of them.

At most 50,000 URLs and 50 MB uncompressed per file. Larger sites use several sitemaps listed in a sitemap index; the analyzer reads an index and every sitemap in it (up to 100), and the Create tab splits large lists automatically.

PDFs and other documents you want in search results can be listed like pages. Images and videos are better described with image and video sitemap entries attached to the page that shows them. The analyzer lists every file in the sitemap by type, and Check the pages finds the files your pages link to, so you can decide.

Open the Create a sitemap tab, enter your website, and paste one URL or /path per line. To set lastmod, put a date after each URL with a comma or tab - a two-column spreadsheet paste works. Choose the options, then download sitemap.xml. It notes in a comment that it was created with RJL.io and the date.

Upload sitemap.xml to the root of your site, add a line such as "Sitemap: https://example.com/sitemap.xml" to robots.txt (the Create tab gives you the exact line), and submit it in Google Search Console and Bing Webmaster Tools.

The analysis and the Create tab run entirely in your browser. To read another website's sitemap and robots.txt - and, when you check pages, those pages and the sizes of the files they link to - the page fetches them through RJL.io's CORS proxy, because browsers block one site from reading another site's files; the proxy keeps a log of each request (the address fetched, your IP address and browser) to prevent abuse, and does not keep the content. Pasted or uploaded XML never leaves your browser.

Yes. Add ?url= with the site or sitemap address, for example /sitemap-analyzer/?url=example.com, and the analysis starts when the page opens. Add #create to open the Create tab.