Description
The Fix 404 Error Links WordPress plugin shows you which pages are missing, how often people hit them, and where those visitors should go instead.
A product URL changed after a redesign. An old blog post was renamed. Someone bookmarked a page you deleted. Google still sends people there, and they land on “Page not found”. This plugin records that 404, counts the hits, and lets you point the old URL at the right page with a 301. The next visitor arrives where they meant to go.
Full setup, redirect rules, and notification options are in the official documentation.
How it works
- Open Fix 404 Links in the WordPress admin. The Control Panel lists broken URLs and how many times each one was hit.
- Click Fix This Error on a row. The redirect form opens with that URL already filled in.
- Choose the destination and save. The next request to that address is redirected, and the hit counter on the rule shows that it is working.
Logging starts as soon as the plugin is active. No extra plugin is required. See Managing redirects and 404 logs.
Features
- Automatic 404 log: every broken URL is stored once, with a running hit count, so repeat visits do not create duplicate rows. Error logs »
- Control Panel: total 404s, active redirects, the URLs hit most often, and the redirects that fire most often. Control Panel »
- Flexible redirect rules: match the full URL, or use Contains, Starts with, Ends with, or Find and replace (with regular expressions and captured groups). Send visitors to a URL, a WordPress menu item, or an error page. Redirect codes 301, 302, 303, 304, 307, and 308. Error page codes 400, 401, 403, 404, 410 Gone, and 418. Adding a redirect »
- One-click Fix it: the source URL is filled in for you. A plain-English sentence updates as you type, so you can read what the rule will do before you save it.
- Do nothing: count hits on a URL you are not ready to redirect yet. Visitors still see the normal 404 page. FAQ »
- Publish, reorder, and bulk edit: turn a rule on or off, drag rules so a specific match wins over a broad one, and activate, deactivate, or delete many rules at once.
- Bot filter: crawler 404s stay out of the log by default. Turn Enable Bot Logging on only when you want them. Logging »
- Email alerts: an HTML email to the site admin address with the broken URL, referrer, IP, browser, and a button that opens the fix screen. Send once per URL, or only after a hit threshold. Off until you turn it on. Notification limits »
Documentation
- Introduction
- Installation
- Managing redirects and 404 logs
- Settings
- Configuration case studies
- FAQ
- Get support
Source Code
The PHP source of this plugin is readable directly in the distributed files.
The admin screens are a React single-page application compiled into public/js/admin-view.js and public/css/admin-view.css.
The complete, unminified source code, development files, and build configurations are included directly within this plugin package under the react-src/ directory.
To build the JavaScript and CSS bundle from source:
1. Navigate to the react-src/ directory: cd react-src
2. Install dependencies: yarn install (or npm install)
3. Build the production bundle: yarn build (or npm run build)
The build output is automatically placed into public/js/admin-view.js and public/css/admin-view.css.
External Services
This plugin does not call an external service. 404 detection, the log, and redirects run on your server. Notification emails are sent with your site’s wp_mail().
Installation
The plugin is simple to install.
From the WordPress dashboard
- Go to Plugins → Add New.
- Search for Fix 404 Error Links by Web357.
- Click Install Now, then Activate.
- Open Fix 404 Links.
Manual upload
- Download
web357-fix-404-error-links.zipfrom the product page. - Go to Plugins → Add New → Upload Plugin, choose the zip, and click Install Now.
- Activate the plugin.
- Review logging under Fix 404 Links → Settings.
Logging starts immediately. Step-by-step screenshots: Installation guide.
FAQ
What does this plugin do, in one sentence?
It records 404 errors, shows you which broken URLs get the most visits, and lets you redirect those URLs to a live page.
Why should I fix 404 errors?
A missing page wastes the visit and the links that still point at the old address. A 301 sends people and search engines to the replacement page. For a page that should stay gone, choose the 410 Gone error page so crawlers drop it. Why use it »
Will logging 404s slow down normal pages?
No. The plugin only acts when WordPress is already returning a 404. Ordinary pages are not logged. If a cache plugin serves a stored 404 page by itself, exclude 404 responses from that cache so this plugin can see the request. FAQ »
A new redirect does not seem to run. What should I check?
- The rule status must be active.
- Rules run from top to bottom. Drag a more specific rule above a broader one.
- The target must be different from the source. Identical source and target are skipped so visitors are not sent in a loop.
- Another redirect plugin may be handling the same URL.
Which HTTP code should I use?
Use 301 when the page has moved for good. Use 302 or 307 when the move is temporary. Use the 410 Gone error page for content that should be removed from search results. Status codes »
Can I redirect a whole folder, not one URL?
Yes. Use Contains, Starts with, Ends with, or Find and replace with a regular expression and capture groups. Capture groups »
Will I get an email for every 404?
Only if you turn notifications on. They are off until you enable them. The site admin gets one email per URL, or one after a URL reaches a hit count. Email settings »
A 404 never shows up in the log. Why?
Confirm Enable Logging is on. Bot hits are ignored unless you opt in. A caching plugin may be answering before WordPress runs. Troubleshooting »
Does the plugin send my traffic to an outside service?
Logging, redirects, and notification emails stay on your server. Emails go out through WordPress wp_mail(). GeoIP »
Where is the full documentation?
Start here: Fix 404 Error Links docs. For help, contact support.
Screenshots





Changelog
v1.0.0
- First release
