BugWP logo BugWP
Back to Community
Home / Community / Plugin → Broken link checker

Why Broken Link Checker Reports Valid Links as Broken (And How to Fix It)

20 threads Sep 16, 2025 Plugin → Broken link checker

Content

One of the most common frustrations users report with the Broken Link Checker plugin is its tendency to flag perfectly functional links as broken. This issue can manifest in several ways, from 403 errors on accessible pages to problems with specific file types like .webp, or even misinterpreting relative links. If you're constantly dismissing false positives, this guide will help you understand why it happens and how to resolve it.

Common Causes of False Broken Link Reports

Based on community reports, here are the most frequent reasons Broken Link Checker might incorrectly identify a link as broken:

  • Server Configuration and Firewalls: The plugin's automated requests can sometimes be blocked by server security rules, firewalls, or rate limiting, resulting in 403 or other errors even though a human visitor can access the URL without any problem. This is a common issue for links behind corporate firewalls or on security-conscious hosting platforms.
  • URL Encoding and Page Builders: Some visual page builders and themes store links using percent-encoding (e.g., https%3A%2F%2Fexample.com instead of https://example.com). The Broken Link Checker may not decode these URLs before checking them, leading to failed requests for malformed web addresses.
  • Specific File Types: There is evidence that the plugin may not correctly recognize newer file formats like .webp, reporting them as missing even when they are present and accessible in the media library.
  • Relative Link Resolution: A bug in the local (old) version of the plugin can cause it to incorrectly resolve relative URLs (e.g., /about-us/), sometimes even incorporating quotation marks into the final URL it tries to check, which naturally results in a 404 error.
  • Redirect Handling and Safemode: If the plugin encounters a server-level restriction (like PHP's open_basedir directive or safemode), it may be unable to follow redirects. This can cause it to log a warning and stop checking a chain of redirects before reaching the final—potentially broken—destination.
  • Third-Party CDNs and Domains: If your site uses a Content Delivery Network (CDN) or has undergone a domain change, the plugin might be detecting and checking the URL from the CDN's domain (e.g., something.netdna-ssl.com) instead of your own, which could lead to errors if that CDN URL is not configured correctly.

Troubleshooting Steps and Solutions

If you are experiencing a flood of false positives, work through these potential solutions.

1. Adjust Check Settings

One of the first things to try is decreasing the plugin's checking intensity. Lowering the number of simultaneous connections and increasing the wait time between requests can help avoid tripping server-side security measures and rate limits that cause 403 errors.

2. Manually Mark Links as "Not Broken"

For links you know are correct, you can manually mark them as "Not Broken." However, some users report that these links are sometimes rechecked and flagged again later. Keep an eye on this behavior.

3. Investigate URL Encoding

If you use a page builder like Visual Composer, WPBakery, or Divi, check your database to see if links are stored in a percent-encoded format. If they are, this is a known limitation, and the Broken Link Checker team may need to address it in a future update.

4. Check for CDN or Domain Issues

If your image or file links are pointing to a strange domain (like a netdna-ssl.com subdomain), your site's configuration might be causing the wrong URL to be stored. This often requires fixing the underlying URL in your media library or reviewing your CDN settings.

5. Review Server Logs

Check your server's error logs around the time a false positive occurs. Look for HTTP 403 errors originating from the plugin's IP address. This can confirm that the block is happening on the server side, not because the link is actually broken.

When to Seek Further Help

If these steps don't resolve your issue, your specific case might be related to a more complex conflict with your theme, another plugin, or a unique server environment. When seeking help in community forums, be prepared to provide specific examples of the URLs being mislabeled and any relevant details about your hosting setup.

Related Support Threads Support