Link Checker screenshot

Link Checker

Crawl a public page's same-origin links and inventory each as ok, redirect or broken, with hop chains recorded. Externals inventoried, 200-link cap.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
No account needed
Private addresses refused
Nothing stored from the responses

Which links still work, and which redirect

A page rots one link at a time: a moved section leaves a redirect, a deleted page leaves a 404, and nobody notices until a visitor does. This page fetches one public URL, walks the links that stay on the same origin, and reports each as ok, redirect (with the hop chain) or broken (with the status or the error).

How to use it

Enter a public https:// URL and press Check the links. You get one row per checked link with its verdict and chain, a summary count, and the skipped list with the reason each URL was not checked.

Same origin only, and the cap is reported

A crawler that followed external links would fetch the whole web on your behalf, so links off the page's origin are inventoried and never fetched. Redirect chains are reported hop by hop and stop at the redirect cap rather than followed forever. At most 200 links are checked per run; the remainder is listed as skipped with the reason over-cap, not silently dropped. Fragments, mailto addresses and empty addresses are classified without a request.

A real capture

This is the recorded output for https://208.67.222.222/, a host that answers 404 with no links at all: the inventory is empty on both sides and the summary is all zeros — the shape a linkless page honestly produces.

Privacy and safety

The server fetches the URL you name and every same-origin link it finds, so this page does not claim to run in your browser. Private, loopback and reserved addresses are refused before a connection is opened, and every redirect hop of every link is checked again. Each request has its own timeouts and read cap, and no response is written to disk or logged.

Enter a public URL and this page fetches it, walks the links that stay on the same origin, and reports each as ok, redirect with the hop chain, or broken with the status or the error — plus the skipped list with the reason each URL was not checked.

Links off the page's origin are inventoried and never fetched. Redirect chains are reported hop by hop and stop at the redirect cap rather than followed forever. At most 200 links are checked per run and the remainder is listed as skipped, not silently dropped.

The requests are made by the tool server. Private and reserved network addresses are refused at the start URL, at every link and at every redirect hop; each request has its own timeouts and read cap.

What each verdict means

Ok answered 2xx with no hops. Redirect moved at least once: the chain is recorded hop by hop, and a link that redirects but lands is still a redirect, because the link itself should point at the final URL. Broken answered 4xx or 5xx, failed to connect, or hit the redirect cap.

Skipped is not a verdict on the link: it is the reason no request was made — external, fragment, special scheme such as mailto, empty, unresolvable, or over the 200-link cap.

  • ok, redirect, broken: one request per checked link
  • Redirect chains recorded, capped, never followed past the cap
  • Skipped rows carry the reason, never a guess

How the crawl is bounded

The start page is fetched through the same hop-validating reader as the audit tools, then each same-origin link is fetched the same way, so a public URL cannot land on a private address through a redirect at any depth.

Duplicates are checked once. A refusal or a transport failure on one link ends that row, not the run: the inventory completes and the summary counts what was actually checked.

How to use the URL field

Enter the public page URL and run. The start page is fetched through the guarded reader, then each same-origin link is fetched the same way; links off the origin are inventoried and never fetched, and at most 200 links are checked per run.

Read each row as ok, redirect with its hop chain, or broken with the status or error, plus the skipped list with the reason no request was made. Duplicates are checked once, and one failing link never ends the run.

What to Expect

Best for

  • Finding broken links after a migration or redesign
  • Listing redirecting internal links to point at final URLs
  • Inventorying a page's external links without opening them

Not ideal for

  • Checking links on a client-rendered page, which require JavaScript
  • Crawling a whole site: one run is one page plus its links
  • Anything behind a login or on a private network address

What this tool keeps

  • Every link the start page carries, checked or skipped with reason
  • The hop chain of every redirect
  • A scope note stating the same-origin limit and the cap

What may need cleanup

  • Redirecting links that work but should point at the final URL
  • An empty inventory on a page that genuinely carries no links
  • Fragment links, which are classified without a request

Common errors

  • Reading skipped-external as unchecked-broken
  • Expecting the crawl to follow links onto other sites
  • Testing a localhost or private address, which is refused

Example use cases

  • Post-migration broken-link sweep of key pages
  • Redirect-chain inventory before a URL cleanup
  • External-link inventory for a content audit

Sample input

Enter the public URL of a section index and run the check.

Sample output

One row per link with ok, redirect or broken, hop chains for the redirects, skipped rows with reasons, and summary counts.

Who this is for

  • Site owners after a redesign or migration
  • Content teams auditing link rot
  • Developers verifying a sitemap's targets resolve

Frequently asked questions

Which links does the link checker open?

Only the start page's same-origin links, up to 200 per run. External links are inventoried and never fetched.

What happens to redirects and pages past the cap?

Redirect chains are reported hop by hop and stop at the redirect cap; links past the 200-link cap are listed as skipped with the reason, never silently dropped.

Can it check a page on a private address?

No. Private, loopback and reserved addresses are refused before a connection is opened, at the start URL and at every redirect hop.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.