Broken Link Checker
Scan any page for broken links. We extract every <a href> on the page and run a HEAD check on each — surfacing 4xx errors, 5xx errors, and redirects. Up to 50 links per scan.
Dead links cost rankings and trust.
Every link on a page is a promise to the reader and a path for a crawler. When that path dead-ends in a 404 or a server error, you spend user goodwill and crawl budget for nothing. Broken links are one of the cheapest SEO problems to fix and one of the most common to ignore — which makes auditing them a fast, high-leverage win.
Crawl waste
Googlebot's crawl budget is finite. Every 404 it fetches is a page it isn't fetching instead.
User trust loss
Visitors who hit dead links bounce. Bounce signals leak back into ranking algorithms.
Link equity drains
Outbound links to dead pages waste authority. Inbound links to your own dead pages lose equity entirely.
AI citation drag
Answer engines weight source quality. Pages full of dead references get cited less.
Every link, tested in real time.
No crawler database, no cached guesses — we hit each URL live the moment you run the scan, so the results reflect what's actually happening right now.
Extract
We fetch the page and pull every <a href> link out of the rendered HTML — internal and external.
Request
Each unique URL gets a lightweight HEAD request (falling back to GET) so we read the status without downloading the whole page.
Classify
Responses are bucketed: 2xx healthy, 3xx redirect, 4xx client error, 5xx server error, plus timeouts and DNS failures.
Report
You get a per-link table with status codes, redirect targets, and the exact anchor text — so each fix is one click away.
Reading the results.
Every link the scan returns carries an HTTP status code. Here's what each family means and what to do about it.
Success
The link works. 200 OK is the target; 204/206 are valid too. No action needed.
KeepRedirect
301/302 forwards to another URL. Fine occasionally, but chains waste crawl budget.
Point directClient error
404 Not Found, 403 Forbidden, 410 Gone. The destination is broken or off-limits.
Fix or removeServer error
500/502/503 — the destination server failed. Often transient, sometimes chronic.
Recheck / replaceHow to fix what the scan finds.
Repoint or remove
For a 404/410, link to the live equivalent if one exists, or delete the link if the content is gone for good.
Collapse redirect chains
If a link 301s through two or three hops, update the href to the final destination so crawlers and users skip the detour.
Set up 301s for your own URLs
When you move or retire a page, redirect the old URL to the most relevant live page to preserve its link equity.
Recheck flaky 5xx targets
Server errors are sometimes momentary. Re-scan; if a destination is reliably down, swap it for a stable source.