Pricing

Rating

Developer

Actor stats

Categories

Share

HTTP Status Scanner: Check URL status codes and redirect chains in bulk

HTTP Status Scanner checks the HTTP status code, redirect chain, and response time for any list of URLs. Drop in a batch of URLs and get a dataset showing what each one actually returns: a 200, a redirect chain ending somewhere unexpected, a 404, or a server error. Good before site launches, after migrations, and during SEO audits when you need to know what your URLs are doing without opening each one by hand.

Use cases

• SEO auditing: find pages returning 404 errors or unexpected redirects before they show up as crawl issues
• Site migration: verify that old URLs redirect correctly to new destinations after a domain change or URL restructure
• Pre-launch QA: confirm that every published URL resolves before a site goes live
• Broken link detection: scan URLs from a sitemap or crawl export to catch dead links in bulk
• Redirect chain cleanup: identify chains longer than two hops that add latency and split link equity across hops

Input

Example input

{
"urls":[
"https://apify.com",
"https://apify.com/store",
"http://apify.com/blog"
],
"followRedirects":true,
"maxRedirects":10,
"maxUrls":100,
"requestTimeoutSecs":30,
"proxyConfiguration":{"useApifyProxy":true}
}

What data does this actor return?

The actor stores one record per URL in the Apify dataset. Each record contains:

{
"url":"http://apify.com/blog",
"finalUrl":"https://apify.com/blog",
"statusCode":200,
"statusText":"OK",
"redirectCount":1,
"redirectChain":["https://apify.com/blog"],
"responseTimeMs":312,
"contentType":"text/html; charset=utf-8",
"checkedAt":"2025-03-04T10:22:45.123456+00:00",
"error":null
}

How it works

1. The actor reads the url and urls inputs, deduplicates them, and adds https:// to any URL missing a scheme.
2. For each URL, it sends an HTTP GET request with a realistic browser User-Agent and follows up to maxRedirects redirects.
3. It records the status code, final destination, every redirect hop, the response time, and the Content-Type header.
4. If a request times out, exceeds the redirect limit, or fails for any other reason, it records an error instead of stopping.
5. Results are pushed to the Apify dataset as they complete, one record per URL.

Integrations

Connect HTTP Status Scanner with other apps using Apify integrations. Schedule it to run on a cron, pipe results into Google Sheets via Make or Zapier, or trigger downstream workflows with webhooks whenever new results are ready.

FAQ

Can this actor check HTTP status codes without following redirects? Yes. Set followRedirects to false and the actor returns the first response status code without following any 3xx redirects.

How many URLs can it check per run? Up to 1000 URLs per run (set via maxUrls). For larger lists, run the actor multiple times or split the input across runs.

What counts as an error in the output? Timeouts, connection failures, SSL errors, and too-many-redirects all produce a record with a non-null error field. The actor never stops on a single bad URL.

Does it work with HTTP and HTTPS URLs? Yes. Both protocols are supported. URLs without a scheme get https:// prepended automatically.

Can I use this to monitor URLs on a schedule? Yes. Save your URL list as the actor input, then set up a schedule in the Apify console to run it daily or weekly.

If you manage a large site, this handles the kind of URL checking that otherwise eats an afternoon of clicking through browser tabs.