Sitemap Extractor & Audit – All URLs, Lastmod, Broken Links

Get every URL a website lists in its sitemaps, in one table: give a homepage and the actor finds the sitemaps itself (robots.txt Sitemap: lines, then the usual locations), follows sitemap indexes, unpacks .xml.gz files and also reads text and RSS/Atom sitemaps. Each URL comes with lastmod, change frequency, priority, hreflang alternates and image/video/news counts.

Turn on Check HTTP status and it also requests every URL, so you see which pages in your sitemap are broken (4xx/5xx) or redirected. Every site gets a free health summary of what's wrong with its sitemaps.

What you get

One row per URL

Field	Description
url, sitemapUrl	The page, and the sitemap file it was listed in
lastmod, changefreq, priority	As declared in the sitemap (lastmod normalised to ISO 8601 UTC)
alternates	hreflang versions of the page (xhtml:link)
images, videos, news	Image, video and Google News entries for the page
statusCode, redirectsTo	With status checks on: HTTP status and redirect target

One summary per site (free): sitemaps read and failed, URL counts and a list of issues with an example each:

• sitemap missing, unreachable or not valid XML (URLs are still recovered from <loc> tags)
• URLs in the sitemap that are broken, redirect or don't answer
• URLs on another host, a mix of http:// and https://
• duplicate URLs across sitemaps, lastmod dates in the future
• files over the protocol limits (50,000 URLs or 50 MB)

Use cases

• SEO audits: find broken and redirected URLs you are asking Google to crawl, and stale or future lastmod dates.
• Content inventories and migrations: export every page of a site, with dates, before a redesign or CMS move.
• Competitor research: see how many product, blog or category pages a competitor has and what changed recently (filter by lastmod).
• Feeding crawlers and AI pipelines: give a scraper or RAG pipeline the exact list of pages to fetch, without crawling.
• Monitoring: schedule it and compare URL counts and issues over time.

Input examples

Whole sites, with status checks:

{
  "startUrls": ["https://www.sitemaps.org", "https://apify.com"],
  "checkStatus": true
}

Only blog posts changed since a date:

{
  "startUrls": ["https://example.com"],
  "includePattern": "/blog/",
  "lastmodAfter": "2026-01-01"
}

Output example

From a real run:

{
  "type": "url",
  "url": "https://www.sitemaps.org/",
  "site": "https://www.sitemaps.org",
  "sitemapUrl": "https://www.sitemaps.org/sitemap.xml",
  "lastmod": "2016-11-21T00:00:00Z",
  "changefreq": null,
  "priority": null,
  "images": 0,
  "videos": 0,
  "news": false,
  "alternates": []
}

With Check HTTP status on, a redirected URL looks like this (real run, 26 Oct 2026: 27 of the first 80 URLs in wordpress.org's sitemaps redirect):

{
  "url": "https://wordpress.org/embed-image/",
  "statusCode": 301,
  "redirectsTo": "https://wordpress.org/files/2022/08/embed-image.png"
}

and the site summary lists {"issue": "URL in sitemap redirects", "count": 27, "example": "https://wordpress.org/embed-image/"}.

Pricing

Pay per event: $0.30 per 1,000 URLs extracted, plus $0.50 per 1,000 URLs when Check HTTP status is on. Site summaries are free. Set a maximum spend per run in the run options; the actor stops cleanly when it is reached. Use Max URLs per site or the filters to keep large sites cheap.

Tips

• Give the homepage, not a page deep in the site: discovery starts at /robots.txt.
• Huge sites (millions of URLs): set Max URLs per site or filter by path or lastmod.
• Status checks hit every URL: lower Status checks in parallel for small servers, or use a proxy for sites that block data-centre traffic.

FAQ

Does it crawl the site? No. It reads only what the site publishes in its sitemaps, which is fast and polite. Pages missing from the sitemap won't appear.

My sitemap is broken XML. Will it work? Usually yes: the actor recovers URLs from <loc> tags and flags the file in the summary.

Something wrong? Open an issue on the actor's Issues tab and it will be fixed.