How to Check Website Status Codes and Response Times for a List of URLs
13 Nov 2026 · benthepythondev
You have a list of URLs. It might come from a sitemap, an ad campaign, a backlink export or a client handover. You want to know if each one still loads, where it ends up and how long it takes to respond. The Website Status Checker actor on Apify does this. It fetches each URL you give it, follows redirects and saves one row per URL to an Apify dataset.
It is not a crawler. It checks only the URLs you supply, so you need a known list of pages before you start. If you also want the tech stack behind each site, see how to get the tech stack and email provider of any website.
What you get
Each checked URL becomes one record with these fields:
- input: the value you typed in, exactly as given.
- url: the normalized version of that URL.
- final_url: where the request ended up after following redirects.
- domain: the domain of the final URL.
- status_code: the HTTP status code, such as 200 or 404.
- ok:
truefor 2xx and 3xx responses. - response_time_ms: how long the response took, in milliseconds, measured from the Apify runtime.
- redirect_count: how many redirects were followed.
- content_type and content_length: response metadata from the server.
- title: the page's
<title>tag, when there is one in the returned HTML. - server: the server header, when the site exposes it. Otherwise
null. - error: a connection or timeout error message, or
nullif the request worked.
Real example output
The input can be a short list:
{
"urls": [
"https://apify.com",
"https://example.com"
]
}
Here are the two rows that came back from a real run:
[
{
"input": "https://apify.com",
"final_url": "https://apify.com",
"domain": "apify.com",
"status_code": 200,
"ok": true,
"response_time_ms": 165,
"redirect_count": 0,
"content_type": "text/html; charset=utf-8",
"content_length": 514402,
"title": "Apify: Marketplace of ready-to-run tools for AI",
"server": null,
"error": null
},
{
"input": "https://example.com",
"final_url": "https://example.com",
"domain": "example.com",
"status_code": 200,
"ok": true,
"response_time_ms": 33,
"redirect_count": 0,
"content_type": "text/html; charset=utf-8",
"content_length": 577,
"title": "Example Domain",
"server": "cloudflare",
"error": null
}
]
The url field is trimmed here. In both rows it matched the input.
Look at server in these two rows. example.com sends a cloudflare header, but apify.com sent no server header, so the field is null. Plan for that field to be empty fairly often.
Use cases
These come from the actor's README.
Post-migration checks. Save a baseline of your important URLs before a site migration. After launch, run the same list again and compare final_url and status_code. A page can return 200 and still redirect to the wrong place, so check both fields.
Finding broken backlink targets. Export the backlink URLs from your SEO tool, run them through the checker and filter for rows where status_code is not 200 or ok is false.
Validating campaign links. Before a paid or email campaign goes out, check every destination URL. Check them again after any big website release.
Recurring checks for landing pages or client sites. Schedule the actor on Apify (the README gives hourly runs for high-value landing pages as an example). Then use a webhook to send rows with ok = false to Slack, email, Google Sheets, Airtable, Make, Zapier or n8n. Agencies can attach the export to monthly technical reports.
How to run it on Apify
- Open the actor page: https://apify.com/benthepythondev/website-status-checker.
- Add your URLs or domains to the
urlsinput field. - Start the run. When it finishes, the results are in the run's dataset, and you can export them as JSON, CSV or Excel from there.
- If you want regular checks, add a schedule. To act on the results when a run ends, add a webhook.
You can also start runs and read the dataset through the Apify API, so the checker fits into a release QA script or a CI step. No RapidAPI listing exists for this actor at the moment, so use the Apify API directly.
Some tips from the README:
- Keep the list focused. Find URLs first with a sitemap or a crawler, then pass in only the pages that matter.
- Don't check just the homepage. Product pages, blog posts, docs and checkout routes can each fail on their own.
- For alerts, compare against the previous run. A single timeout is often a temporary network issue, not an outage.
Honest limits
- No JavaScript. The actor reads the HTML the server returns and takes the
<title>from it. If a page builds its title or content in the browser, you won't see that here. - Response time is relative.
response_time_msis measured from Apify's runtime, not from your users' locations. It's useful for spotting a page that got slower over time. It doesn't tell you what real visitors experience around the world. - Protected sites may behave differently. The README says some protected sites may return different responses to an automated check. A block page can show up as an error or as a status code that doesn't match what a browser gets.
- No discovery. It won't find pages for you. If a URL isn't in your input, it doesn't get checked.
- Header fields can be missing.
serverandtitleare filled only when the site provides them, as the apify.com row above shows.
If you have a list of URLs and want status codes, redirects and load times in a table, this is a quick way to get them.
Affiliate if you still need an Apify account: apify.com/?fpr=qolupv. I may earn a commission; the price you pay does not change.