Audit your sitemap and robots.txt in one call

Two small files decide a lot about how a search engine sees your site: robots.txt says what crawlers may fetch, and the XML sitemap lists the pages you want indexed. Mistakes in either are easy to make and hard to notice.

What goes wrong

• A Disallow rule that blocks more than intended, sometimes the whole site after a staging deploy.
• A sitemap that does not load, or that is declared in robots.txt at the wrong address.
• URLs in the sitemap that redirect, return errors or point to another host.
• Mixed HTTP and HTTPS URLs and duplicates.
• A lastmod that is missing or never changes, so it carries no signal.
• A sitemap that is too large: the limits are 50,000 URLs and 50 MB uncompressed per file.

One request

curl "https://api.ambolt.dev/v1/sitemap-robots-doctor?site=sitemaps.org&free=1"

{
  "site": "https://sitemaps.org",
  "robots": { "found": true, "sitemapDirectives": ["https://www.sitemaps.org/sitemap.xml"], "blocksEverything": false },
  "sitemaps": [{ "url": "https://www.sitemaps.org/sitemap.xml", "ok": true, "type": "urlset", "urls": 84 }],
  "stats": { "urlsRead": 84, "withLastmod": 84, "duplicates": 0, "offHost": 0, "nonHttps": 0, "newestLastmod": "2022-12-15", "oldestLastmod": "2016-11-21" },
  "issues": []
}

Recorded 2026-10-03; fields trimmed. The answer also lists a sample of the sitemap's URLs with their HTTP status, and ends with a list of concrete issues so a script or an agent can act on it without reading the raw files.

How to use it

Run it after each deploy and on a schedule, and fail the build when issues is not empty. Sitemap indexes are followed up to ten files.

It does not crawl your site: it reads robots.txt and the sitemaps and checks a small sample of the listed URLs. Try your own domain in the free sitemap checker.