SiteVerdict — robots.txt & Sitemap Monitor
Pricing
Pay per event
Catch SEO disasters before Google does: watches robots.txt, XML sitemaps and key pages for Disallow: /, noindex, canonical and status changes, sitemap URL drops and errors. Diffs vs last run, Slack/webhook alerts, HTML report.
Live checks your sites. Sample replays two recorded days of a demo shop (a leaked 'Disallow: /' for Googlebot, a new noindex and a sitemap drop) so you can see the alert output for free, with no network calls.
Homepages or any URL of each site; only the origin (scheme + host) is used. robots.txt and sitemaps are discovered automatically.
Important pages to watch for noindex, canonical, redirect, status and robots.txt-block changes, e.g. your homepage, top category and product pages. Their sites are added automatically.
Sitemaps to check in addition to those declared in robots.txt (or /sitemap.xml). .gz is supported.
This many URLs, spread across the sitemap, are fetched to check they return 200, are indexable, not redirected and self-canonical. 0 = off. Each is billed as a URL check.
Safety cap on sitemap files read per site (sitemap indexes are followed up to 3 levels).
Warn when the number of sitemap URLs falls by at least this percentage since the last run.
Critical alert when the sitemap URL count falls by at least this percentage.
'All sites' writes one row per site every run. 'Only changes' writes a row only for the first (baseline) run and when something changed; ideal for hourly schedules.
Send an alert when a change of at least this severity is detected. Critical = e.g. 'Disallow: /' for Googlebot, noindex on a key URL, sitemap 404, URL count down 50%+.
We POST a JSON alert (site, changes, robots.txt diff) here, e.g. a Zapier/Make/n8n hook. Stored encrypted.
https://hooks.slack.com/services/... Stored encrypted.
Named key-value store holding the last snapshot and change history of each site. Use one name per client/project.
Past change events kept per site in the state store.
Ignore saved snapshots and start fresh this run.
Requests to the same host are always sequential, at most 1 per second (or the site's Crawl-delay).
Off by default. When on, the findings (no personal data) are sent to your chosen LLM provider with YOUR API key to get concrete, prioritised fix snippets. Charged as one 'ai-fix' event per successful answer; your provider bills tokens separately.
Which API your key belongs to.
Your Anthropic or OpenAI API key. Stored encrypted by Apify, never logged or written to the output.
