Secure Broken Link Checker & 404 Detector
Scan publicly accessible webpages for broken internal and external links, 404 and 410 errors, redirects, restricted URLs, timeouts, rate limits, and server errors.
Broken Link Checker Studio
Scan Sequence Pipeline
Root crawl
Connects to the root domain and downloads target index pages.
Links parsing
Extracts anchor paths, image src tags, and communication formats.
Trace status
Resolves manual redirect paths, status errors, and loop depths.
Score reports
Calculates health summary grades and exports formatted logs.
Common Link Auditing Remediations
❌ Incorrect Link Config
- Pointing links to redirect hops:
/about-old → /about → /about-us - Loading images over insecure HTTP schemas on HTTPS domains.
- Hashing to anchor section hashes that are spelling-typoed or missing.
- Letting external links point to expired domain names returning 404s.
✅ SEO Studio Resolution
- Update internal routes to point directly to final destinations.
- Serve all image assets over secure SSL protocol structures.
- Coordinate anchor links with active DOM ID element properties.
- Update or remove outbound references that lead to invalid pages.
What is a Broken Link Checker?
A Broken Link Checker scans links found on a publicly accessible webpage and checks how their destinations respond. It helps identify missing pages, outdated references, redirecting URLs, restricted destinations, server failures, rate limits, and requests that time out.
The checker separates internal links from external links and groups results by status. This makes it easier to distinguish genuinely broken destinations from redirects, authentication restrictions, temporary failures, and URLs that require manual verification.
The checker can scan up to 50 publicly accessible internal HTML pages and check the internal and external links discovered during the scan. It is not an unlimited enterprise crawler and should not be treated as a complete site audit.
Internal Link Analysis
Find navigation links, downloads, images, buttons, and references that point to missing or outdated destinations on the same website.
External Link Analysis
Review outbound references to third-party websites and identify destinations that fail, redirect, block automated requests, or time out.
Status-Code Classification
Separate successful, redirected, broken, restricted, rate-limited, timed-out, and server-error responses.
Redirect Destination Review
Inspect final destinations when supported and update source links that still pass through unnecessary redirects.
Why Broken Links Matter
Broken internal links interrupt navigation and prevent users and crawlers from reaching the intended destination.
Redirect chains add extra requests and make website maintenance and crawling less efficient.
Fixing broken links improves navigation, crawl paths, and maintainability, but it does not guarantee an immediate ranking or indexing improvement. Regularly reviewing important links improves overall user experience and keeps your website content accessible and clean.
Fix Internal Links First
Prioritize broken navigation, product links, downloads, form actions, documentation links, and other destinations you control directly.
Internal vs. External Broken Links
Internal and external links require different types of investigation and correction.
| Aspect | Internal Links | External Links |
|---|---|---|
| Destination | A page, file, or resource on the same website. | A page or resource hosted on another domain. |
| Common Causes | Renamed pages, incorrect HTML paths, deleted content, or migration errors. | Removed articles, expired domains, changed URLs, restrictions, or temporary outages. |
| Level of Control | You can usually fix the source link, restore the page, or add a relevant redirect. | You may need to replace, update, or remove the reference. |
| Recommended Priority | Usually higher because it directly affects your navigation and site structure. | Depends on the importance of the source and whether the failure is permanent. |
| Typical Fix | Correct the URL or point directly to the current preferred destination. | Find a working replacement source, update the destination, or remove the link. |
How Link Statuses Are Classified
A failed automated request does not always mean that a link is permanently broken. The response should be interpreted according to its status code or failure type.
| Status | Meaning | Recommended Action |
|---|---|---|
| 200–299 | The destination responded successfully. | No immediate link correction is required. |
| 301, 302, 307 or 308 | The URL redirects to another destination. | Consider linking directly to the final stable URL. |
| 401 or 403 | The destination requires authentication or refuses the automated request. | Open the link manually before classifying it as broken. |
| 404 | The requested destination could not be found. | Correct, replace, remove, restore, or redirect the URL. |
| 410 | The destination was intentionally removed and is not expected to return. | Remove or replace the link unless a relevant alternative exists. |
| 429 | The destination has temporarily rate-limited requests. | Retry later or reduce scanning concurrency. |
| 500–599 | The destination server failed while processing the request. | Retry and verify manually before making a permanent change. |
| Timeout | The destination did not respond within the allowed time. | Retry and check manually because the problem may be temporary. |
404 Not Found vs. 410 Gone
A 404 Not Found response means the server could not locate the requested resource. The response does not necessarily confirm whether the absence is temporary or permanent.
A 410 Gone response explicitly indicates that the resource was intentionally removed and is not expected to return.
Both statuses normally require reviewing the source link. Use a relevant replacement URL when one exists. Avoid redirecting every deleted page to an unrelated homepage because that can create a confusing experience for visitors.
Redirect Chains and Redirect Loops
Redirect Chains
A redirect chain occurs when one URL passes through multiple intermediate destinations before reaching the final page.
Page A → Page B → Page C → Final Page
Redirect chains add extra requests and make website maintenance and crawling less efficient. When the final destination is stable, update the original source link to point directly to it.
Redirect Loops
A redirect loop occurs when URLs repeatedly redirect to each other and no final destination is reached.
Page A → Page B → Page A
Redirect Loop Detected
A redirect loop prevents users and crawlers from reaching the intended destination. Review the website's routing and redirect configuration.
How the Broken Link Checker Works
The checker scans up to 50 publicly accessible internal HTML pages and checks the internal and external links discovered during the scan. The process is governed by the following pipeline:
Fetch Public Pages
Retrieves the entered public webpage and additional internal pages when recursive crawling is enabled.
Extract Links
Finds supported internal links, external links, fragment links, images, and resource URLs from the scanned pages.
Check Responses
Checks HTTP response codes, redirects, request timeouts, rate limits, restricted responses, and server failures.
Classify and Export
Groups results by status and prepares the available downloadable reports.
Common Broken Link Checker Use Cases
Website Migrations
Find links that still point to retired paths, changed folders, old domains, or unnecessary redirect destinations.
Content Maintenance
Check resource pages, blog posts, guides, documentation, and older articles for removed external references.
Pre-Launch Testing
Review navigation, buttons, image references, downloads, and supporting links before publishing a new page or redesign.
Recurring Website Reviews
Check frequently updated pages after content edits, product changes, documentation updates, or large publishing operations.
How to Check Broken Links Online
Enter a Public Webpage URL
Enter the complete address beginning with https:// or http://.
Choose Scan Settings
Select the available internal-link, external-link, page-depth, timeout, or crawl-limit options.
Start the Link Check
Run the scan and keep the browser tab open while the selected links are being reviewed.
Review Link Categories
Compare working, redirected, broken, restricted, rate-limited, timed-out, and server-error results.
Verify Uncertain Results
Open restricted, timed-out, and rate-limited destinations manually before removing or replacing them.
Apply Fixes
Update source links, restore destinations, configure relevant redirects, or replace outdated references.
Common Broken Link Scenarios (Examples)
| Scenario | Problem | Recommended Fix |
|---|---|---|
| Renamed Page | <a href="/old-about-us"> points to a missing destination. |
Update the link to the new URL or add a relevant permanent redirect. |
| Redirect Chain | /services → /our-services → /services-list |
Point the source link directly to the preferred final destination. |
| Expired External Source | A supporting reference points to a removed page or expired domain. | Find a relevant replacement, update the URL, or remove the link. |
| Insecure Resource | Loading images, scripts, stylesheets, iframes, or other embedded resources over HTTP from an HTTPS page. | Use HTTPS versions of embedded resources where available. |
| Missing Fragment Target | A link uses #contact, but no matching element ID exists on the target page. Note that fragments on dynamically rendered pages may not always be verified successfully. |
Ensure that each fragment link points to an element ID that exists on the target page. |
Privacy and Data Handling
The Broken Link Checker uses a TryFormatter server route to request publicly accessible webpages and link destinations. The entered URL and public webpage data required for the scan may pass through TryFormatter infrastructure during processing.
No account is required to run the checker. Avoid scanning private dashboards, local-network addresses, password-protected pages, staging URLs containing access tokens, or websites you are not authorized to test.
Results are displayed in the active browser session and may be included in files you choose to export.
Broken Link Audit Checklist
Track your audit and remediation progress. Your checklist status is saved locally in this browser.
Frequently Asked Questions
What does the Broken Link Checker check?
The tool scans publicly accessible webpages and checks the HTTP response status of their internal and external links, detecting broken URLs (404/410 errors), redirects, restricted endpoints, rate limits, timeouts, and server failures.
Can it check internal and external links?
Yes. The scanner checks both internal links pointing within the same domain and external links pointing to third-party domains discovered on the crawled pages.
Is a redirected link considered broken?
No. A redirected link (3xx status code) points to a valid destination, but updating the source link to point directly to the final URL improves crawl efficiency and website maintenance.
Does a 403 response mean the link is broken?
No. A 403 Forbidden status indicates a restricted URL. The target page likely exists but requires authentication, blocks automated scrapers, or denies access to the crawler.
How many pages can the checker scan?
When recursive scanning is enabled, the checker can scan up to 50 publicly accessible internal HTML pages and check the links discovered during the scan.
Can it scan an entire website?
The checker scans the entered public page and a limited number of supported internal pages when recursive scanning is enabled. It is not an unlimited enterprise crawler.
Does it require an account?
No. You can check pages for broken links and download report logs without creating an account or signing up.
Does the scan happen entirely in the browser?
No. The checker uses a TryFormatter server route to request publicly accessible webpages and link destinations. Avoid entering private URLs, local-network addresses, or links containing access tokens.
Can I scan a private or staging website?
No. The checker cannot access private dashboards, password-protected staging domains, localhost environments, or local network URLs. Use it only for publicly accessible websites.
Can I export the results?
Yes. You can copy the results as Markdown or download them in PDF and JSON formats using the export buttons provided in the dashboard.
Why can some working links appear restricted or timed out?
Some destination servers block automated requests to prevent spam or scrape activity, returning a 403 status or failing to respond within the request timeout limit.
Does fixing broken links guarantee better rankings?
No. Fixing broken links improves navigation, crawl paths, and site maintenance, but it does not guarantee an immediate ranking or indexing improvement.