Sitemap Extractor, URL Status Checker & New Page Monitor

Get every URL from any website's sitemaps in seconds, check which ones are broken, redirected or noindexed, or schedule it to tell you only when pages are added, updated or removed. No browser, no login, no API keys.

Three jobs in one Actor

You want to…	Settings	You pay for
Export all URLs from a site's sitemaps (lastmod, changefreq, priority, image/video counts, hreflang alternates)	Mode: All URLs	Each URL row
Audit sitemap hygiene: find 404s, 5xx, redirects, redirect chains, noindex and canonical-to-elsewhere URLs that shouldn't be in a sitemap	All URLs + Check each URL	Each URL row + each URL checked
Monitor competitors' new pages (blog posts, product pages, landing pages)	Mode: Changes only, run on a schedule	A tiny fee per URL compared + each new / updated / removed URL

Use cases

• SEO audits and migrations: list every URL a site declares, then flag the ones Google shouldn't see in a sitemap (non-200, redirected, noindex, canonicalised elsewhere).
• Content and competitor monitoring: a daily schedule in Changes only mode gives a feed of new pages a competitor publishes, often before they're promoted.
• Crawl seeding: feed the clean URL list into a crawler, RAG pipeline or AI agent instead of crawling blindly.
• Uptime spot checks of the pages that matter, straight from the sitemap.

Connect the dataset to Slack, email, Google Sheets, Make, n8n or Zapier with Apify integrations, or call it from an AI agent through the Apify MCP server.

Input

{
  "startUrls": [{ "url": "https://crawlee.dev" }, { "url": "https://www.example.co.uk/post-sitemap.xml" }],
  "mode": "all",
  "checkStatus": true,
  "maxUrlsPerSite": 5000,
  "includePattern": "/blog/",
  "excludePattern": "/tag/|/author/"
}

• Homepage or sitemap URL. For a homepage the Actor reads Sitemap: lines in robots.txt, then tries /sitemap.xml, /sitemap_index.xml, /wp-sitemap.xml and /sitemap.txt. Sitemap indexes (up to 4 levels), .xml.gz, plain-text sitemaps and RSS/Atom feeds are all supported.
• URLs are de-duplicated across all of a site's sitemaps (trailing slash and host case ignored).
• Filters run before billing, so skipped URLs cost nothing.
• Changes only: the first run saves a baseline (no rows). Schedule the Actor with the same monitorName and every later run outputs only new, updated (lastmod changed) and removed URLs. With Check each URL on, only new and updated URLs are checked. Snapshots are kept in a key-value store called sitemap-url-monitor-state in your own account.

Output (one row per URL)

{
  "site": "https://www.gov.uk",
  "url": "https://www.gov.uk/employment-tribunal-decisions/…",
  "lastmod": "2026-10-20T09:12:44+01:00",
  "changefreq": null,
  "priority": null,
  "imageCount": 0,
  "videoCount": 0,
  "alternates": [],
  "sitemap": "https://www.gov.uk/sitemaps/sitemap_1.xml",
  "statusCode": 200,
  "finalUrl": "https://www.gov.uk/employment-tribunal-decisions/…",
  "redirectChain": [],
  "contentType": "text/html; charset=utf-8",
  "xRobotsTag": null,
  "metaRobots": "noindex, nofollow",
  "canonical": "https://www.gov.uk/employment-tribunal-decisions/…",
  "responseMs": 142,
  "issues": ["noindex"],
  "indexable": false,
  "checkedAt": "2026-10-26T18:24:02+00:00"
}

issues can contain client-error, server-error, error (timeout / connection), redirect, redirect-chain, noindex, canonical-elsewhere and checker-blocked-by-robots. In Changes only mode each row also has changeType (new, updated, removed) and, for updates, previousLastmod.

A per-site summary (sitemaps found and read, sitemap errors, URL count, issue counts, changes, whether the read was complete) is saved as OUTPUT in the run's key-value store.

How it works and what it respects

• Reads only public sitemaps that sites publish for crawlers, and (if you ask) requests each URL once, reading at most the first 256 KB of HTML to find meta robots and canonical tags. No personal data is collected.
• Obeys robots.txt for every request it makes (sitemaps and URL checks) and identifies itself honestly in its user agent. Sitemaps or pages disallowed for it are reported, not fetched.
• Polite by default: sitemap files are fetched one at a time with a pause, URL checks use at most 4 parallel requests per site (configurable up to 10), with back-off on 429/5xx.

Limits

• Sites with no sitemap at robots.txt or the usual locations are reported as "No sitemap found". Pass the sitemap URL directly if it lives somewhere unusual.
• "Updated" relies on the site's lastmod. Many sites don't set it (or set it to the build time), so treat updates as a hint; new and removed URLs are reliable.
• Removals are only reported when the full sitemap was read (not when a limit or error cut the run short).
• Status checks see what a polite bot sees. Sites behind aggressive bot protection may return 403 to it; enable a proxy if needed.
• Max 100 sites per run, 200,000 URLs per site, 1,000 sitemap files per site.

Pricing (pay per event)

• URL (All URLs mode): $0.0002 per URL, i.e. $0.20 per 1,000 URLs.
• URL status checked (optional): $0.0008 per URL checked, so a full export + check is $1.00 per 1,000 URLs.
• URL compared (Changes only): $0.00002 per URL, i.e. $0.02 per 1,000.
• URL change (Changes only): $0.001 per new, updated or removed URL.

Example: monitoring 10 competitor sites with 2,000 URLs each, daily, with ~15 new pages a day costs about $0.42/day ($0.40 compared + $0.015 changes).