Sitemap Auditor
Audit any XML sitemap by URL. Expands sitemap indexes, flags spec errors, duplicates, off-host and mixed-protocol URLs, and checks the HTTP status of a sample of listed pages so redirects and 404s don't sit in your sitemap. Free, no signup.
Input
A sitemap (.xml or .xml.gz) or a sitemap index. Enter just the domain and the sitemap is found via robots.txt.
The sample is spread evenly across the whole sitemap.
Output
| Property | Value |
|---|---|
| No data yet | |
| Severity | Check | Detail |
|---|---|---|
| No data yet | ||
| URL | lastmod | Status | Result |
|---|---|---|---|
| No data yet | |||
More ways to use this tool
REST API
curl -X POST https://api.iotools.cloud/v1/tool/sitemap-auditor \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.sitemaps.org/sitemap.xml",
"statusCheck": "25"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `sitemap-auditor` tool (Sitemap Auditor) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.
| Cost per API/MCP call | From 5 credits |
|---|---|
| Need more credits? | View pricing |
Also available with
Guides
What this tool does
Enter a sitemap URL and this tool fetches it server-side and audits it against the sitemaps.org protocol and the problems search engines actually care about. It doesn't stop at the XML: it also checks the HTTP status of a sample of the listed pages, because a sitemap full of redirects and 404s wastes crawl budget and makes search engines trust the file less.
It handles the sitemaps you'll meet in practice:
- Sitemap indexes are expanded, and up to 10 child sitemaps are audited together, so duplicates across files are caught too.
- Gzipped sitemaps (
.xml.gz) are decompressed automatically. - Just a domain? Enter
https://example.comand the sitemap is found from theSitemap:line in robots.txt (or/sitemap.xmlas a fallback).
What it checks
| Check | Why it matters |
|---|---|
Valid <loc>, lastmod, changefreq, priority |
Malformed entries are skipped by crawlers |
| Broken and redirecting URLs (sampled) | Only list final, indexable 200 URLs |
| Duplicate URLs | Redundant entries, often a sign of a CMS bug |
| Off-host URLs | A sitemap may only list URLs on its own host |
| Mixed http/https, trailing-slash pairs | Points to non-canonical URLs in the file |
lastmod in the future |
Google ignores lastmod values it can't trust |
| 50,000 URLs / 50 MB limits, namespace, Content-Type | Hard protocol limits and serving errors |
How to use it
- Enter the sitemap URL (or just the site's domain).
- Choose how many pages to status-check. The sample is spread evenly across the whole sitemap, not taken from the top.
- Click Audit sitemap, then copy or download the findings as CSV.
Frequently asked questions
Why isn't every URL status-checked? Large sitemaps hold tens of thousands of URLs. An evenly spread sample of 25–50 shows whether there's a systemic problem (like a whole section redirecting) in seconds. To check a specific page's links, use Broken Link Checker.
Can I audit a sitemap I haven't published yet? Paste it into Sitemap XML Parser, which validates pasted or uploaded XML in your browser. To create one, use Sitemap XML Generator.
Why are priority and changefreq marked as info?
Google has said it ignores both. They're valid, so they aren't errors, but an accurate lastmod is the field worth maintaining.