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

Troubleshooting the 'Fix Redirects' Feature in Broken Link Checker

20 threads Sep 9, 2025 Plugin → Broken link checker

Content

Many WordPress users rely on the Broken Link Checker plugin to identify and fix broken and redirected links. A common and frustrating issue reported across numerous support threads is the "Fix Redirects" function not working as expected. Users click the button, receive a success message, but the links remain in the redirects list, or the link is not updated correctly in the content.

This guide will explain why this happens and walk you through the most effective troubleshooting steps to resolve it.

What the "Fix Redirects" Feature Is Supposed to Do

First, it's important to understand the intended function. When a link on your site (e.g., http://example.com) points to a URL that redirects to another address (e.g., https://www.example.com), the plugin detects this. The "Fix Redirects" action is designed to find that original link in your page or post content and automatically update it to the final, direct URL, eliminating the unnecessary redirect.

Why "Fix Redirects" Might Fail

Based on extensive community reports, the issue is not usually a single bug but can stem from several different causes:

  1. Caching: Both site and server-side caching can prevent the plugin from seeing the updated link status or can show you an outdated admin screen.
  2. Database Storage Engine: Evidence suggests the plugin may not function correctly if its database tables use an engine other than MyISAM.
  3. Plugin Bugs: There are known instances where the plugin fails to correctly parse or display the final redirect URL, showing the same address in both the "URL" and "Redirect URL" columns, making the fix action useless.
  4. Server Configuration: Server settings like open_basedir or safe mode can interfere with the plugin's ability to follow and detect redirects properly.

How to Troubleshoot and Fix the Problem

Step 1: Clear All Caches

This is the most common and first recommended step. Clear your WordPress caching plugin's cache (e.g., W3 Total Cache, WP Rocket), any CDN cache (like Cloudflare), and if possible, your server-level or object cache. After clearing all caches, recheck the links to see if the "Redirect URL" column populates correctly and if the "Fix Redirects" action now works.

Step 2: Verify the Database Storage Engine

Check the storage engine for the Broken Link Checker tables (blc_links, blc_synch, and blc_filters). You can do this using a tool like phpMyAdmin. They should be using the MyISAM engine. If they are using InnoDB or another engine, you may need to change them to MyISAM. Warning: Always back up your database completely before making any changes.

Step 3: Check for a Correct Redirect URL

Before using "Fix Redirects," you must confirm the plugin has correctly identified the target URL. In the Redirects tab, look for the "Redirect URL" column. If this column is missing, ensure "Redirect URL" is enabled in the "Screen Options" tab at the top of the page. If the "Redirect URL" is identical to the original "URL," the fix action will not work. This indicates the plugin is failing to detect the redirect target, often due to server configuration or a bug with specific sites (like Twitter or CNN).

Step 4: Investigate Server Configuration

Check your server error logs. If you see warnings about open_basedir restrictions or safe mode, this is likely preventing the plugin from following redirects. You may need to contact your hosting provider to adjust these PHP settings or determine a suitable workaround.

Step 5: Manual Fixing

If automated fixing continues to fail, the most reliable method is to fix links manually. Use the information in the "Redirects" tab as a list of links that need attention. Click the "Edit URL" button or the "Details" arrow to see where the link is ultimately redirecting, and then manually update that link in the corresponding post, page, or theme file.

Conclusion

The failing "Fix Redirects" feature is a persistent issue often related to caching, database configuration, or server limits rather than a simple user error. By methodically working through these troubleshooting steps—starting with a full cache clearance—you can identify the root cause and get your redirects fixed, either automatically or manually.

Related Support Threads Support