Treat 404 and 410 as the clear failures
These responses say the destination is not available. Update or remove the source link, or restore and redirect the destination when an equivalent page exists.
Public page check
Check the links on one important public page without treating every block or timeout as a broken link. The report confirms 404 and 410 responses and keeps uncertain states separate.
Read the result correctly
An automated request can be blocked even when a human can open the page, and a green HTTP response can still lead to irrelevant content. Fix confirmed failures first, then review uncertain and redirected destinations with context.
These responses say the destination is not available. Update or remove the source link, or restore and redirect the destination when an equivalent page exists.
Authentication, bot protection, rate limits and temporary server trouble can prevent verification. Open important destinations yourself before changing the source.
Check navigation, service, campaign, contact and top organic landing pages first. A bounded tool is most useful when the starting-page choice reflects customer and search value.
Limits and next steps
No. It performs a bounded page-level check of up to 20 eligible links found in the starting page HTML. Use it on important pages individually or use an authorized crawler for a complete site inventory.
Only an HTTP 404 Not Found or 410 Gone response is labeled confirmed broken. Access restrictions, rate limits, timeouts and server errors are shown as separate review states because they do not prove the link is permanently missing.
The checker skips same-page, mail, phone, script, credentialed, private-network and query-string links. This avoids triggering actions, reaching sensitive states or turning the free tool into an unrestricted crawler.
Yes. A successful response proves only that the destination answered. A person should still confirm that redirected and high-value links lead to useful, relevant content.
It uses signed same-site sessions, a hidden honeypot, minimum session age, per-visitor and per-host rate limits, private-network blocking, short timeouts, redirect limits and a hard outbound-request budget.
WANT A PERSON TO REVIEW THE RESULT?