If you’ve ever saved a 301 redirect in Auto Ping Booster Pro and had it just… not work, this update is for you. Version 1.3.16 is a focused bug-fix release that goes straight at the four biggest complaints we’ve heard about the 404 Monitor and Broken Link Detection tools.
No new settings to learn, no migration steps to run — just update the plugin and your 404/301 workflow gets noticeably more reliable.
What was actually going wrong
Under the hood, the 404 log table could end up with more than one row for the exact same broken URL — one saved as a bare path, another as a full URL. When you saved a redirect, it could land on a different row than the one your live site actually checked on the next 404 hit. The redirect looked “saved” in the dashboard, but visitors kept hitting a 404 anyway.
On top of that, saving a redirect never cleared your site’s cache — so even when the redirect logic was correct, a cached 404 page could keep being served until someone manually cleared caches elsewhere in Settings.
What’s fixed in 1.3.16
- 301 redirects now actually redirect. URL matching between the save form and the live 404 handler is fully normalized, and the database now enforces one row per broken URL — no more mismatched duplicates silently eating your redirect.
- Caches clear automatically. The moment you save a redirect, Auto Ping Booster Pro flushes the object cache plus common host/CDN cache plugins (WP Rocket, W3 Total Cache, LiteSpeed, SiteGround, Breeze, and more). There’s also a new standalone “Refresh 404 Pages / Clear Cache” button if you just want to force a refresh.
- Editing a saved redirect works. Change your mind about where a broken URL should go? Update the field and save — it now updates the same row instead of getting lost.
- One master “Save All Redirects” button. The Broken Link table used to reload the whole dashboard and scroll you back to the top for every single row you saved. Now the entire table is one form — fill in as many redirect targets as you want and save them all at once, and you land right back on the same section.
A quick heads-up
A small number of broken URLs — typically static-looking files like .txt or image paths — never reach WordPress at all. Your web server can serve a 404 for these directly, before WordPress ever loads. If a specific URL still won’t redirect after updating, that’s usually a server-level rule rather than anything the plugin can catch. Your host can add a server-side redirect for those cases.
How to update
Update to 1.3.16 from your WordPress dashboard as usual. After updating, open the plugin’s Inter-linking page and you’ll see a one-time banner summarizing these fixes, with a shortcut straight to your Broken Link table.
As always, thanks for the detailed reports — this release exists because you told us exactly what wasn’t working.