Article Broken Link Checker
Paste HTML, Markdown or plain article text to extract HTTP links and check up to 20 public URLs for obvious broken-link responses.
Extract and check links from an article draft
Paste HTML, Markdown or plain article text to extract HTTP links and check up to 20 public URLs for obvious broken-link responses.
| URL | Status | Result |
|---|
What the article broken link checker does
This tool helps editors audit outbound links before publication or during content maintenance. It extracts unique HTTP and HTTPS URLs from common HTML anchors, Markdown links and bare URLs, then can request response headers for a limited set of public links.
How broken-link checking is classified
Successful 2xx responses and resolved redirects are treated as reachable. A 404 or 410 is a strong broken-link signal. Authentication responses such as 401 or 403 may still point to a valid resource, while a 405 can simply mean the server refuses HEAD requests. Server errors and unusual responses should be reviewed manually.
Why a link can work in a browser but fail here
Some sites block automated requests, require JavaScript, use bot protection, depend on cookies, or reject HEAD requests. This checker is deliberately conservative and does not bypass those controls. It also checks only public HTTP(S) destinations and blocks private or reserved network addresses.
Editorial workflow
Use the checker before publishing, after migrating a site, and when refreshing older content. For links flagged for review, open the destination manually and replace obsolete sources with the most authoritative current source rather than merely removing useful citations.