DETECT EVERY HTTP ERROR
SecurityBot doesn't just find 404s. It detects the full range of HTTP error status codes so you can understand exactly why each link is failing and prioritize your fixes.
TL;DR: SecurityBot's broken link checker detects 404 Not Found, 403 Forbidden, 400 Bad Request, 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and more. Filter results by status code to focus on the errors that matter most. Each status code tells a different story about what's wrong — and how to fix it.
START FREE TRIALSTATUS CODES WE DETECT
Every HTTP error tells a different story. SecurityBot catches them all.
Not Found
The most common broken link error. The page has been deleted, moved without a redirect, or the URL was mistyped.
Fix: Set up a 301 redirect to the correct page, restore the deleted content, or remove the link.
Forbidden
The server understood the request but refuses to authorize it. Often caused by incorrect file permissions or IP restrictions.
Fix: Check file permissions, .htaccess rules, or firewall settings that may be blocking access.
Bad Request
The server cannot process the request due to malformed syntax. Usually caused by corrupted URLs or invalid query parameters.
Fix: Check the link URL for encoding issues, special characters, or truncated query strings.
Internal Server Error
A generic server-side error. The destination page has a bug or misconfiguration that prevents it from responding.
Fix: Check the server error logs for the target page. This is a code or configuration problem on the destination server.
Bad Gateway
A reverse proxy or load balancer received an invalid response from the upstream server. Often a temporary infrastructure issue.
Fix: If it persists across multiple scans, investigate the upstream server health or proxy configuration.
Service Unavailable
The server is temporarily unable to handle the request, usually due to maintenance or overload.
Fix: Typically transient. If persistent, check server capacity and maintenance mode settings.
WHY STATUS CODES MATTER
Not all broken links are the same. A 404 means the page is gone. A 403 means it's blocked. A 500 means the server is broken. Knowing the difference lets you take the right action.
-
Prioritize Critical Errors
500-level errors indicate server problems that affect all visitors — fix these first
-
Identify Access Issues
403 errors reveal pages that are unintentionally blocked from visitors or crawlers
-
Distinguish Permanent from Temporary
503s may resolve themselves; 404s and 410s require action on your part
-
Filter and Focus
Filter your broken link report by status code to tackle one category at a time
Quick Reference
Client Errors
The problem is with the link itself (wrong URL, missing page, blocked access)
Server Errors
The destination server has a problem (crashes, overload, misconfiguration)
Redirects
The link works but goes through redirect chains that may slow down your site
FREQUENTLY ASKED QUESTIONS
Common questions about HTTP status code detection
What's the difference between a 404 and a 410?
A 404 means the page was not found but might return in the future. A 410 (Gone) explicitly tells search engines the page has been permanently removed. SecurityBot detects both so you can decide whether to set up a redirect or confirm the removal.
Should I fix 403 errors on external links?
A 403 on an external link usually means the destination site is blocking automated requests. This doesn't always mean the link is broken for real visitors. However, if users report the link doesn't work, you should find an alternative URL or remove the link.
How do I filter by status code?
After a crawl completes, your broken link report includes a status code column. You can sort or filter this column to focus on specific error types — for example, showing only 500 errors to prioritize server-side issues, or only 404s to set up redirects.
Are 500 errors always a problem?
A single 500 error could be a transient server hiccup. But if SecurityBot detects the same 500 error across multiple weekly scans, it's a persistent problem that needs attention. The crawl history lets you see whether an error is new or recurring.
Does SecurityBot follow redirect chains?
Yes. SecurityBot follows redirects (301, 302, 307, 308) and reports when a link goes through multiple redirects before reaching its destination. Long redirect chains slow down page loads and waste crawl budget — ideally, links should point directly to the final URL.
FIND EVERY BROKEN LINK
Start detecting 404s, 403s, 500s, and more across your entire site. SecurityBot catches what other tools miss.
START FREE TRIAL