Sitemap monitors
A sitemap monitor fetches your sitemap.xml, parses the URLs it lists, and checks each one returns a 2xx response. It's how you catch broken internal links and dead landing pages before SEO crawlers do.
Quick setup
- Go to Add sitemap monitor.
- Enter the full sitemap URL (e.g.
https://example.com/sitemap.xml). If you omit the scheme we addhttps://; we do not auto-append/sitemap.xml, so include the path yourself. - Save. The first crawl runs within a few minutes.
How it works
Once per day we fetch the sitemap, follow each URL listed, and record the HTTP status. The dashboard shows pages found, pages broken, and per-page details with their response codes.
Alerts fire when previously-OK pages start returning 4xx/5xx, or when the sitemap itself becomes unreachable.
Per-plan page limit
| Plan | Pages per sitemap |
|---|---|
| Free | 2 |
| Basic | 10 |
| Pro | 100 |
If your sitemap lists more URLs than your plan covers, we sample the first N pages and tell you at the top of the report. Need more than 100 pages? Contact us.
Troubleshooting
"Sitemap not found." Some frameworks serve sitemaps from a different path (e.g. /sitemap_index.xml). Point the monitor at the actual URL — include the full path, not just the host.
Pages return 4xx/5xx that work in my browser. The crawler uses the default Python requests user agent. Some sites bot-block aggressively — if you're filtering by user agent, allow the requests library or the IPs of our infrastructure.
Next steps
- Route sitemap breakage alerts to Slack.
- Add an uptime monitor on your most-trafficked URLs for higher-frequency checks.