Back to Community

Why Broken Link Checker Reports False Errors (And How to Fix Them)

101 threads Sep 16, 2025 PluginBroken link checker

Content

If you've found that the Broken Link Checker plugin is flagging perfectly good links as broken, you're not alone. This is a common frustration reported by many users. Links to sites like Facebook, Instagram, YouTube, Google Maps, Airbnb, and Etsy often show errors like 403, 429, 503, or 529 even though they work perfectly in a browser.

This article explains why these false positives happen and provides the most effective solutions to resolve them.

Why Does This Happen?

The core issue is that the Broken Link Checker plugin does not browse the web like a human. It sends automated requests from your server to check links. Many large websites employ security measures that can misinterpret these automated checks as malicious activity, such as:

  • Aggressive Bot Blocking: Sites like Facebook, Instagram, and Airbnb use sophisticated systems to block what they perceive as scraping bots or suspicious traffic. The plugin's request can be blocked, resulting in a 403 (Forbidden), 429 (Too Many Requests), or 400 (Bad Request) error.
  • Redirection Handling: Some services, like DOI links (e.g., doi.org) or URL shorteners, use complex chains of redirects. The plugin may time out during this process or misinterpret a redirect (like a 302) as an error state, leading to a 503 error.
  • Geographic or Network Blocking: The server your website is hosted on might be in a geographic region or on a network blocklist that the target website (e.g., Google Maps) temporarily restricts, causing a 529 or 503 error.
  • Required User Interaction: Links to platforms like LinkedIn, which require a login to view content, will redirect to a login page. The plugin sees this non-200 response code and reports the link as broken.
  • API Changes: For services like MediaFire that have special integration, an API key might be required for the plugin to check links correctly. Without it, links may be reported with a "302 Unknown Error."

Common Solutions and Workarounds

Based on community reports and troubleshooting, here are the most effective ways to address false positives.

1. Use the "Not Broken" or "Ignore" Function

For links you have verified are working, the simplest solution is to tell the plugin to stop reporting them. In the Broken Link Checker list, you can:

  • Select the link and choose Not broken from the bulk actions dropdown.
  • Right-click on the link and select Dismiss or Ignore.

This will remove the false error from your report. This is often the only practical solution for links to major social media platforms that aggressively block bots.

2. Check Plugin and API Settings

For specific services, the plugin may have special settings that need to be enabled:

  • MediaFire: Navigate to Settings -> Link Checker -> Protocols & APIs and ensure the MediaFire API option is enabled.
  • General Settings: Review the plugin's settings for options like throttle speed, which can help make its requests appear less like an attack on the target server.

3. Understand the Limitations

It's important to recognize the plugin's technical limitations:

  • It checks raw page code, not the final rendered output. If you use a page builder or shortcodes (e.g., [tcb_post_the_permalink]) that generate the final URL dynamically, the plugin will try to check the shortcode itself as a URL, resulting in a false error.
  • It cannot handle links that require a login or human interaction (like cookie consent banners) to access the content.

4. When to Manually Verify

The plugin is a powerful tool for finding genuine broken links, but it is not infallible. It is always recommended to manually verify any link it flags, especially if it points to a major, well-established website. If the link works in your browser, it's safe to mark it as "Not Broken" in the plugin.

By understanding these common causes, you can more efficiently manage your broken link reports and focus your efforts on fixing genuine issues.

Related Support Threads Support