Broken Link Checker
Enter a page URL and we request every link on it one by one, so you can see which ones are genuinely broken and which are simply refusing bots.
One page per scan. Links pointing at the same address are merged and up to 50 unique targets are checked.
What is the Broken Link Checker?
This tool loads the page you enter, pulls out every link it contains and sends a request to each one to measure whether it actually works. Results land in four classes: working, broken, unreachable because the target blocks automated traffic, and skipped because the link is not an HTTP address. That distinction matters more than anything else here. A link returning 403 is not broken, it is a firewall turning us away, and mixing the two sends you off to repair links that were fine all along.
How to use it
- 1Enter the full address of the page you want to audit.
- 2Press "Check the links" and the tool fetches the page, then requests every link on it.
- 3Start with the red rows; the amber ones usually need no fix at all.
- 4Download the whole table as CSV if you want to share it with your team.
How to read the results
When to use it
Refreshing Old Articles
Sites you cited in a guide written years ago may have shut down. Audit the links before you publish the update.
After a Site Migration
When the URL structure changes, internal links keep pointing at the old addresses. Audit your highest-traffic pages once the move is done.
Before Publishing Guest Posts
Check the links in contributed content before it goes live, and catch broken or unwanted destinations early.
Common mistakes
Treating Bot Blocks As Breakage
Deleting links that return 403 throws away working, valuable sources. Open the amber rows in a browser before you remove anything.
Auditing Only The Home Page
Broken links pile up in old blog posts. A clean home page tells you nothing about the content pages that bring in traffic.
Ignoring Redirect Chains
Multi-hop redirects end in a 200 and therefore look healthy. Point internal links at the final address to win back speed and link equity.
Frequently asked questions
Can it crawl a whole site?
No, this version audits a single page. The reason is courtesy rather than capability: a full-site crawl puts real load on the target server. Auditing the pages that actually earn organic traffic, one at a time, is both faster and more accurate.
Why are some links marked "blocked"?
The target site refuses automated access with a code such as 401, 403 or 429. That link almost certainly opens fine in a browser; it is not broken. Protections like Cloudflare turn bot traffic away this way. Click the address yourself if you want to be sure.
How many links are checked?
Up to 50 unique targets per page. Links pointing at the same address collapse into one row, so the limit applies to real targets rather than raw anchors. At most three requests run at once, deliberately low so we do not hammer the target site.
Why are mailto and phone links not tested?
They are not HTTP addresses, so they have no status code. They still appear in the list with a note explaining why they were skipped, rather than being dropped silently and leaving the total link count looking wrong.
How are redirects handled?
The chain is followed, the status of the final address is reported, and the number of hops is shown. A single 301 is not a problem, but long chains slow the page down and dilute link value, so pointing your internal links straight at the final address is better.