Checking Broken URLs After a Site Migration — a small on-demand tool
Checking Broken URLs After a Site Migration — a Small On-Demand Tool Migrations move URLs. A redirect map that looks complete in a spreadsheet can still produce 404s, redirect loops, or unresolved hosts once the new site is live. The annoying part is that you often find out from Search Console days later. I built a small Actor to check exactly the references you hand it — no site crawling, no…
When a website undergoes a migration, the URLs change, which can result in broken links, redirect loops, or unresolved hosts. Often, these issues are discovered only after the new site goes live, frequently revealed through Search Console. To address this, a small on-demand tool was built to check specific references without crawling the site, continuously monitoring, or sending alerts. This article presents the tool's input, output, and limitations.
The tool accepts public HTTP/HTTPS URLs as input, up to 10 sitemap.xml files, a maximum of 200 URLs per run, and sets for concurrency, timeout, and duplicate removal. The tool provides a structured output that includes the status (ok, broken, or network_error), the final URL after redirects, the redirect chain, status code, content type, and elapsed time in milliseconds.
Three scenarios were demonstrated in the tool's output: a healthy page, a confirmed dead page, and a host that could not be reached. For example, a healthy page returns a 200 status code with a redirect chain of zero redirects. A confirmed dead page returns a 404 status code, while a host that could not be reached returns a network_error status code. The distinction between these results is crucial, as network_error does not indicate a broken page.
This tool is useful for pre-launch QA of a redirect map on staging, a post-launch check of traffic or backlink-carrying URLs, and verifying a sitemap subset after a domain or platform move. However, it has limitations, such as a maximum of 200 URLs per run, not being a full-site crawler, on-demand only, lacking scheduling or continuous monitoring, and not providing alerts or webhooks.
The tool does not support authentication, private pages, personal data, or resale of third-party data. Results are accurate only at the moment of the check. Pricing is based on a pay-per-event model: US$ 1.20 per 1,000 URLs checked, which works out to approximately US$ 0.24 for a run of 200 URLs. No subscription is required, and the tool can be accessed at https://apify.com/deyvison-md91/sitemap-integrity-auditor.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.