How do I tell a dead link from a slow one?
A checker that calls everything broken makes you chase ghosts. When the target answers, you get the HTTP status in its own column. When there is no answer, the error column says dns_error, connect_timeout, read_timeout, ssl_error or too_many_redirects. A slow but healthy server shows up as read_timeout, not as a 404, and this run waits 30 seconds before giving up instead of the usual 15.
Input
Output fields
Sign up on Apify or log in
The Find Broken Links on Your Whole Site: 404 Link Checker Actor is ready to run with the inputs already set for "How do I tell a dead link from a slow one?". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "How do I tell a dead link from a slow one?" task
The Find Broken Links on Your Whole Site: 404 Link Checker Actor will start running based on the input automatically. You can also change all the input fields, like website, max pages to crawl, and more, to match your specific use case.
Receive the "How do I tell a dead link from a slow one?" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as row type, broken url, HTTP status, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "How do I tell a dead link from a slow one?" task via API.
Integrate "How do I tell a dead link from a slow one?" into your workflow
Connect "How do I tell a dead link from a slow one?" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay