KitJade

Broken Link Checker

Test a short list of links for broken responses.

Use the Broken Link Checker tool

Uses a KitJade API for the live checkUpdated Report a problem

What this broken link checker does

Broken Link Checker sends each URL in a list to a small server-side endpoint that requests the page and returns its HTTP status, final URL and elapsed time. Redirects are followed, so a link that lands on a 404 is reported as broken with the final address shown.

The Worker only requests public http and https addresses. Localhost, private network ranges and cloud metadata addresses are refused. Per-IP rate limiting and a 20-URL cap keep the endpoint usable, which also means this is a spot check rather than a full site crawl.

Why use it

  • Confirm that links in an article still point somewhere useful.
  • Catch redirects that hide a deleted page.
  • Check a short list of URLs before publishing a resource page.

How to use it

  1. 1Paste one URL per line, up to 20.
  2. 2Run the check and wait for all rows to finish.
  3. 3Sort your attention by error rows and long redirect chains.
  4. 4Open any flagged URL yourself to confirm before changing the link.

Worked examples

Working link

Input

A live product page

Output

HTTP 200 with the final URL and response time.

Redirect to a missing page

Input

A URL that redirects to /404

Output

The final status is 404 and the redirect target is shown.

Common mistakes

  • Expecting it to crawl a whole sitemap; only listed URLs are checked.
  • Assuming a 403 from a bot-protected site means the link is broken.
  • Checking URLs behind a login, which the Worker cannot access.

Frequently asked questions

Why is the limit 20 URLs?
The endpoint is rate limited to protect the service. Checking 20 at a time stays within a normal minute's budget for one visitor.
Why do some sites return 403?
Some servers block automated requests regardless of the link being valid. Verify those in a browser.
Are private addresses allowed?
No. Localhost, private ranges and metadata endpoints are blocked to prevent misuse.
Does it check page content?
No. It checks HTTP status and redirects, not whether the content you wanted is still there.
All tools