Dev.to WebDev 🛠 Dev 👁 0 📖 2 min read

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 si

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 background monitoring, no alerts. This post shows the input, a real output, and where the tool deliberately stops.

The input

  • urls: public http/https URLs you supply.
  • sitemapUrls: up to 10 public sitemap.xml files; <loc> entries are expanded.
  • maxUrls: 1–200 per run (default 200). concurrency: 1–10. timeoutMs: 1,000–30,000.

Exact duplicates are removed. Larger catalogues are checked in separate runs.

A real result

The following is the Actor's own local reproduction output (2026-11-18), used here because it shows the exact field shape. It is not a paid customer run.

{"status":"ok","statusCode":200,"inputUrl":"https://example.com/",
 "finalUrl":"https://example.com/","redirectChain":[],"redirectCount":0,
 "contentType":"text/html; charset=utf-8","elapsedMs":105}

{"status":"broken","statusCode":404,
 "inputUrl":"https://example.com/definitely-not-a-real-page-r011",
 "finalUrl":"https://example.com/definitely-not-a-real-page-r011",
 "redirectChain":[],"redirectCount":0,
 "contentType":"text/html; charset=utf-8","elapsedMs":61}

{"status":"network_error","statusCode":null,"inputUrl":"https://invalid.invalid/",
 "finalUrl":"https://invalid.invalid/","error":"fetch failed",
 "redirectChain":[],"redirectCount":0,"contentType":"","elapsedMs":12}

Three cases in one run: a healthy page, a confirmed dead page, and a host that could not be reached. The distinction matters — network_error is not proof that a page is broken, so a QA pass should investigate it rather than file it as a 404.

Each record also carries redirectChain as ordered from → status → to hops, which is useful when a migration produced chains instead of single 301s.

What this is good for

  • Pre-launch QA of a redirect map on staging.
  • A bounded post-launch check of the URLs that carry traffic or backlinks.
  • Verifying a sitemap subset after a domain or platform move.

What it does not do

  • Maximum 200 URLs per run. It is not a full-site crawler.
  • On demand only — no scheduling, continuous monitoring, alerts or webhooks.
  • No authentication, private pages, personal data, or resale of third-party data.
  • Results reflect the moment of the check.

Price

Pay per event: US$ 1.20 per 1,000 URLs checked (US$ 0.0012 per URL) on the primary event. A full 200-URL run is about US$ 0.24. No subscription is required.

Try it: https://apify.com/deyvison-md91/sitemap-integrity-auditor

I am the author of the Actor; this post discloses that interest. The example output comes from my own local reproduction, not from a customer.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.