A blocked link is one the scanner could not check, because the other site turned it away. By the end of this page you will know how to confirm the link works and how to silence it.
Why a link shows as blocked
Some sites refuse automated checkers but serve people normally. LinkedIn and Facebook are the best-known examples. They answer the scanner with a refusal, or they drop the connection.
A 403 or 429 answer from any site lands in blocked too. Firewalls often send a 403 to bots, and a 429 means the site slowed the scanner down. So neither answer proves the link is broken.
A blocked link never counts as broken and never lowers your health score. A real 404 from those same sites still counts as broken.
Where blocked links show up
- Scan reports and public report pages list them in a separate Blocked links note below the table.
- The Broken links page of a project and its CSV export leave them out.
Links that timed out or got no answer show on the Broken links page under Needs check. They do not lower your score either.
Check the link yourself
- Open the link in your browser.
- If the page loads, the link works. You do not need to do anything.
- If you see an error page, fix or remove the link on your site.
Keep the link out of future scans
For a row on the Broken links page:
- Click Exclude on the row.
- A message confirms that the pattern is excluded from future scans.
Exclude on a link to another site skips that whole domain. On a link to your own site, it skips that exact path.
For any other link, add a pattern by hand:
- Open the project and click Scan settings.
- Add a part of the address to Excluded URL patterns, one per line. A domain such as
linkedin.comworks. - Click Save exclusions.
Exclusions apply from the next scan. The current results stay as they are.
When your own site shows as blocked
Your firewall or CDN may turn away the scanner. Then links to your own pages land in blocked. If your start page refuses the scanner, the scan stops with a message instead.
Allow the BrokenLinkCheckerBot user agent in your firewall or CDN settings. The crawler page shows the exact user agent string. Then run the scan again.