Broken Link Checker

Paste a URL to check every link on the page. Each link gets a real request and an honest classification: truly broken links separated from blocked, transient and ambiguous responses, with the evidence shown for every row.

Checks every link in the page HTML, up to 200 unique targets per scan. HEAD first, GET retry when HEAD is rejected; identifies as DevDomeLinkChecker.

How results are classified (reference)

A dead link checker that labels every non-200 response "broken" sends you to fix links that work. This one classifies each response honestly, and the headline broken count contains only strong evidence: 404, 410, dead DNS or failed TLS. Everything else gets its own label with the evidence shown.

ResultWhat it meansWhat to do
Broken Strong evidence the link is dead: 404 Not Found, 410 Gone, a domain that no longer resolves in DNS, or a failed TLS handshake. Fix the URL, point it at the new address, or remove the link. These are the ones worth acting on.
Blocked 401, 403 or 407: the destination refused this automated request. Many sites block checkers while serving browsers normally. Open the link in a browser. If it loads, nothing is broken; the site just blocks bots.
Transient 429 rate limiting, 5xx server errors, or a timeout. The page probably exists but this particular request failed. Recheck later. Treat as broken only if it fails repeatedly over days.
Redirected The link reached a working page after one or more redirect hops. Works for visitors. Updating the link to the final URL skips the hop and keeps link equity direct.
Working The destination answered normally with a 2xx status, no redirects. Nothing to fix.
Unknown Ambiguous evidence: a connection that refused, more than 3 redirects (possible loop), or an unusual 4xx like 400. Verify these manually. The tool refuses to guess for you.
Not checked The scan hit its request budget or time limit, or the target is outside what this checker may fetch. The result explicitly says the scan was incomplete. Run again or check these by hand.

Broken links, user trust and crawl waste

Every broken link is a dead end for a real person. Visitors who hit a 404 rarely hunt for the content, they leave, and a page full of dead links reads as a page nobody maintains. That erosion of trust is the quiet cost, and it compounds on the pages you care about most, because those are the pages people actually click through.

Search engines feel it too. Crawlers spend a limited budget on your site, and every request that ends in a 404 or a redirect loop is budget not spent discovering your real content. Link equity flowing into a dead URL simply evaporates. Cleaning up broken links is one of the cheapest technical SEO wins available.

Honest scope note: this tool reads the page HTML as served, so links added purely by JavaScript after load are not seen, and it tests one page at the moment you run it. That is exactly right for spot checks and pre-publish reviews, but links rot silently, on every page, all the time. DevDome Site Health monitors your whole site continuously, so a link that breaks on Tuesday gets flagged on Tuesday, not whenever you remember to recheck.

Broken link checker FAQ

What is a broken link?

A broken link, also called a dead link, points to a destination that no longer answers with a working page. The most common cause is a 404 Not Found from a deleted or moved page, but expired domains, removed pages (410 Gone) and dead TLS configurations break links too. To a visitor they all look the same: a click that leads nowhere.

How do I find broken links on a page?

Paste the page URL into the checker above. It fetches the page HTML, extracts every link (up to 200 unique targets), requests each one and classifies the result: Broken only on strong evidence like 404, 410 or a dead domain, and separate labels for blocked, transient and ambiguous responses. Every result shows the request method, redirect hops and timing, and the scan reports exactly how many links it examined, checked and skipped.

Why does this tool not count a 403 as broken?

Because a 403 from an automated checker usually means bot blocking, not a missing page. This checker identifies itself honestly as DevDomeLinkChecker instead of impersonating a browser, and some sites refuse identified bots while serving people normally. Counting those as broken would send you off to fix links that work. They get their own Blocked label with instructions to verify in a browser.

What is the difference between a 404 and a 410?

A 404 Not Found says the page is not at that address right now, with no promise about the future. A 410 Gone says the page was removed deliberately and permanently, and search engines drop 410 pages from the index faster. For your links the fix is similar, update or remove, but a 410 tells you not to wait for the page to come back.

Do broken links hurt SEO?

Indirectly, yes. A few broken links will not tank rankings on their own, but they waste crawl budget, leak link equity into dead ends, and degrade the user signals search engines do measure, like visitors bouncing after a 404. On large sites, hundreds of broken internal links also make crawlers less efficient at discovering your real content.

How does the checker make its requests?

Each link gets a HEAD request first, retried as a GET when the server rejects HEAD (400, 403, 405 or 501), with redirects followed up to 3 hops and every hop revalidated. The user agent identifies itself as DevDomeLinkChecker with a link back to this page. Every result row shows which method produced it, how many redirect hops were followed, and how long the request took.

What happens to the URLs I check?

The page URL you submit is fetched once, its links are requested once, and the results are returned to your browser. Results are not stored, shared or sent to analytics. Avoid submitting URLs that contain secrets such as password-reset tokens: any URL you check is, by definition, requested by our server.

How often should I check for broken links?

Links rot constantly: pages get deleted, domains expire, sites restructure. A manual pass with a 404 checker like this one is great before publishing and for occasional audits. For everything you cannot recheck by hand, use continuous monitoring. DevDome Site Health watches your whole site on a schedule and flags broken links before a visitor finds them.