Bulk URL checker: status codes for 100 links at once
Paste up to 100 addresses, one per line or straight from a spreadsheet column. For each one you get its status code, where it ends up after redirects, and whether a reader gets the page. You also see when a bot wall answered instead of the site.
- harbor.example/pricing200Works
- harbor.example/old-pricing301→200Redirects, then works
- harbor.example/careers/2019404Link is dead (404)
- status.harbor.example/api503Destination is returning a server error
- linkedin.com/company/harbor999Blocks link checkers, works in a browser
Reading the result
Codes shows the first answer and the last one. 301 → 200 means the address redirects and the page at the end works. One code means it answered directly.
- Broken is a page a reader won’t get: a
404or410, a domain that no longer resolves, a redirect that ends at an error, or a page that answers200but says it isn’t there (a soft 404). - Need attention works for now: a long redirect chain, a plain
403, or a server that took more than 5 seconds. - Couldn’t check means bot protection answered for the site. LinkedIn’s
999, Cloudflare’s challenge and a429are the common ones. The page usually works in a browser, so open those yourself. Why link checkers see 403 and 429 explains why.
To see every hop of one address, use the redirect checker. To check the links on a page without making a list first, use the page link checker, or the free scan for 25 pages of a site.
Find the 404s in a list
Paste the list and let the last batch finish. The Broken count is how many won’t open for a reader, and ticking Only show problems hides the rest. In the CSV, filter final_status for 404 and 410. A row with a final_status of 200 and a result of fail got an answer with no real page behind it, such as a soft 404 (a page that says it isn’t there) or a parked domain. The detail column says which. An empty final_status means no answer at all, usually a domain that no longer resolves, a certificate error or a timeout.
Check redirects in bulk
Every row shows the first answer, the last one and where the address ends up, and the CSV adds a redirects column with the number of hops. After a migration, sort by it and read the columns together:
redirectsis 1 andfinal_statusis200: the old address lands in one hop. Check thatfinal_urlis the page you meant it to go to.redirectsis 2 or more: a chain. Point the first redirect straight at the final address. Redirect chains and loops has the server rules.- Many different old addresses with the home page as
final_url: Google can treat those as soft 404s. Redirect each one to its closest replacement, and let the rest return 404. first_statusis302or307for a page that moved for good: make it a301or308.
Where a list of URLs comes from
- A migration. Paste the old addresses and check each one redirects to a page that works, in one hop. Checking redirects after a migration covers what to look for.
- Search Console. Export the “Not found (404)” list and check which are still broken before you fix them. Finding broken links in Search Console shows where the list is.
- Your outbound links. The links in a resources page or a newsletter archive go to other people’s sites, which change without telling you. How to check external links covers what to do with each dead one.
A dead link to a page that’s gone for good can often be swapped for an archived copy. The Wayback Machine checker finds one, and how to fix broken links covers the other options.
It runs in your browser with nothing to install, 100 addresses at a time. For a longer list, split it, or use the short script in checking a list of links yourself. If the list is really every link on your site, a crawl finds them for you and records which page each one is on.
