Sitemap Integrity Auditor avatar

Sitemap Integrity Auditor

Pricing

from $1.20 / 1,000 url checkeds

Go to Apify Store
Sitemap Integrity Auditor

Sitemap Integrity Auditor

Checks a supplied list of public URLs or sitemap entries and returns HTTP status, redirect chain and timing. No proxies, no paid APIs, no private data.

Pricing

from $1.20 / 1,000 url checkeds

Rating

0.0

(0)

Developer

Deyvison Miguel

Deyvison Miguel

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 hours ago

Last modified

Categories

Features

Limited permissions

Share

Check a list of URLs — or the URLs found in a public sitemap — and get evidence-based HTTP status, redirect chains, content type and response timing for every reference. Built for SEO agencies, site-maintenance teams, e-commerce operators and developers managing migrations or large URL catalogs.

No crawling of third-party platforms, no continuous monitoring, no authentication, no personal or applicant data, no proxies and no paid third-party APIs. You supply the references; the Actor checks only those.

What it does

For every public http/https reference supplied, the Actor performs one on-demand check and returns:

FieldMeaning
inputUrlThe URL you supplied
finalUrlFinal URL after redirects
checkedAtUTC ISO timestamp of the check
statusCodeFinal HTTP status code, or null on network failure
statusok, broken, redirect or network_error
redirectChainOrdered hops with from, status, to
redirectCountNumber of redirect hops
contentTypeResponse Content-Type header
elapsedMsTime spent checking this URL
errorPresent only for network_error

Exact duplicate URLs are removed before checking. A SUMMARY record in the key-value store contains status counts, number of charges, sitemap errors and the finish timestamp.

Input

FieldTypeDefaultRangeDescription
urlsarray——Public http/https URLs to check
sitemapUrlsarray——Public sitemap.xml URLs; <loc> entries are added to the check list
maxUrlsinteger2001–200Hard cap on URLs checked per run — this controls your bill
concurrencyinteger51–10Parallel HTTP requests
timeoutMsinteger80001000–30000Per-request timeout in milliseconds

Simple input:

{
"urls": [
"https://example.com/",
"https://example.com/careers/123"
],
"maxUrls": 50
}

Input from a public sitemap:

{
"sitemapUrls": ["https://example.com/sitemap.xml"],
"maxUrls": 200
}

Output

Results are written to the default dataset, one item per checked URL:

{
"inputUrl": "https://example.com/careers/123",
"finalUrl": "https://example.com/careers/123",
"checkedAt": "2026-11-18T21:40:44.544Z",
"statusCode": 200,
"status": "ok",
"redirectChain": [],
"redirectCount": 0,
"contentType": "text/html; charset=utf-8",
"elapsedMs": 105
}

A broken link looks like this:

{
"inputUrl": "https://example.com/old-page",
"finalUrl": "https://example.com/old-page",
"checkedAt": "2026-11-18T21:42:05.309Z",
"statusCode": 404,
"status": "broken",
"redirectChain": [],
"redirectCount": 0,
"contentType": "text/html; charset=utf-8",
"elapsedMs": 61
}

Pricing — Pay per event

EventPriceWhen it is charged
url-checked (primary)$1.20 per 1,000 URLs (US$ 0.0012 per URL)One charge per URL verified
apify-default-dataset-item$0.01 per 1,000 itemsPlatform minimum when a dataset item is written
apify-actor-start$0.00005Actor start; covers the first 5 seconds of compute

You pay only for the work you request. Platform usage costs are included — they are not billed separately to you. You can set a maximum charge per run in Apify Console; the Actor respects that limit.

Example: 200 URLs cost about $0.24 (US$ 0.0012 × 200), plus negligible synthetic events.

Limits and honest scope

  • Maximum 200 URLs per run. Use maxUrls to cap cost; larger catalogs should be split into multiple runs.
  • On-demand only. The Actor does not continuously monitor URLs, schedule checks, crawl websites, send alerts or webhooks.
  • It does not collect job descriptions, applicant data or any private/authenticated content, and it does not resell third-party data.
  • Network failures are reported as network_error and are distinct from a confirmed broken (HTTP error) result.
  • Results reflect the moment of the check; a URL may change afterwards.

Typical uses

  • Find dead apply links in a job board after a migration.
  • Validate URLs imported into a site or CMS from a spreadsheet.
  • Audit a public sitemap before a launch or during routine maintenance.
  • Verify that expected pages return 200 and that unexpected redirects are visible.