Aggregated 404 Log
Repeated requests for the same missing URL are counted in one record and ranked by hits, with unresolved and resolved states so finished work drops out of view.
Free WordPress plugin
See which broken URLs visitors actually hit, ranked by traffic, and fix each one with a 301 redirect or a 410 Gone response, straight from the 404 log.
Direct answer
A focused 404 monitor and redirect manager for WordPress administrators who want to fix broken links by impact, not by guesswork.
KM 404 Redirect Manager is a free WordPress 404 redirect plugin that records the URLs returning “404 Not Found” on your site, groups repeated requests into a single row ranked by hit count, and lets you turn any entry into a redirect rule. Rules support exact, wildcard and regular-expression matching with 301, 302, 307 or 308 redirects, or a 410 Gone response for content that was removed on purpose.
After a redesign, a migration, a permalink change or a product clean-up, old URLs keep getting requested by visitors, bookmarks, emails and search engines. A long, unsorted list of errors makes it hard to know where to start.
KM 404 Redirect Manager aggregates each broken URL into one record and ranks it by hits, so the URLs that lose the most visitors rise to the top. You can then create the right redirect in the same screen and mark the issue as resolved.
Plugin features
Everything happens inside your WordPress dashboard under Tools → 404 Redirects.
Repeated requests for the same missing URL are counted in one record and ranked by hits, with unresolved and resolved states so finished work drops out of view.
Turn a broken URL into a redirect rule without copying paths between screens. Each rule has its own hit counter and can be enabled or disabled individually.
Match a single path, a whole folder with an asterisk, or a pattern with a PCRE regular expression, and reuse captured parts in the destination with $1, $2 and so on.
Choose permanent or temporary redirects, method-preserving 307 and 308 responses, or 410 Gone when content has been removed for good. Destinations can be internal paths or external HTTP(S) URLs.
Export all rules to CSV, download a sample file, and import up to 2,000 rows per file. Every row is validated and previewed first, and matching rules are updated instead of duplicated.
Filter common bots and administrator visits, set automatic log retention, and decide whether to record referrers, user agents or a salted IP hash. Raw IP addresses are never stored.
Matching rules
Pick the simplest match type that covers the URLs you need to fix.
| Match type | Example source | Example destination | Use it when |
|---|---|---|---|
| Exact | /old-page/ |
/new-page/ |
A single page moved to a new address. |
| Wildcard | /old/* |
/new/$1 |
A whole folder or section moved and the rest of each URL stays the same. |
| Regular expression | ^/legacy/([0-9]+)/?$ |
/archive/$1/ |
URLs follow a pattern, for example numeric IDs from an old system. |
| 410 Gone | /discontinued-product/ |
No destination | The content was removed on purpose and has no relevant replacement. |
Status codes
The response code tells browsers and search engines whether a move is permanent, temporary or a removal.
| Code | Meaning | Typical use |
|---|---|---|
| 301 | Moved permanently | The standard choice when a page has a new permanent URL. |
| 302 | Found (temporary) | A short-term move, such as a seasonal page or maintenance detour. |
| 307 | Temporary redirect, method preserved | A temporary move where form submissions must keep their request method. |
| 308 | Permanent redirect, method preserved | A permanent move for endpoints that receive form or API requests. |
| 410 | Gone | Content deleted intentionally, so search engines can drop it sooner than a 404. |
Redirect each old URL to its closest relevant replacement. Sending every broken link to the homepage is a poor experience for visitors and is often treated as a soft 404 by search engines.
Getting started
From installation to your first redirect in a few minutes.
Use cases
Useful whenever URLs change and old links still bring in visitors.
Catch the old URLs that real visitors still request after moving to a new theme, page builder, permalink structure or host.
Redirect discontinued products to their replacements or categories, or return 410 Gone for items that will never return.
Consolidate merged or outdated posts into stronger pages without leaving broken links behind.
Prioritize the broken URLs with the most hits and keep useful old links pointing at relevant content.
Prepare redirect maps in a spreadsheet and move them between client sites with CSV import and export.
Monitor 404s without sending data to outside services. The more sensitive logging options are off by default.
Privacy and data
All logs, rules and settings stay in your own WordPress database.
| Data | Default | Details |
|---|---|---|
| Broken URL and hit count | On | One aggregated record per URL, not one row per visit. |
| Referrer | Optional | Shows which page linked to the broken URL. |
| User agent | Off | Browser and device information, for troubleshooting only. |
| IP address | Not stored | Optionally a salted one-way hash. Raw IP addresses are never saved. |
| External services | None | No analytics, logs, rules or settings are sent anywhere. |
| Data on uninstall | Kept | Enable “Delete plugin data on uninstall” to remove the plugin’s tables and settings. |
Common questions
Quick answers about setup, matching rules, privacy and data.
Yes. It is free and open source under the GPLv2 (or later) license and is distributed through the official WordPress.org Plugin Directory.
After activation, open Tools → 404 Redirects. The screen has tabs for 404 Logs, Redirects, Import / Export and Settings.
No. Redirect rules are evaluated on public front-end requests, so an administrator can also redirect an existing path on purpose. The 404 log itself only records requests that WordPress resolves as 404 responses.
Yes. A destination can be a site-relative path such as /new-page/ or a full HTTP or HTTPS URL on another domain.
An asterisk (*) captures matching text, and captures can be reused in the destination as $1, $2 and so on. For example, /old/* can redirect to /new/$1.
Enter a delimiter-free PCRE pattern such as ^/legacy/([0-9]+)/?$. Capture groups can be reused in the destination.
Not by default. If you enable the IP option, the plugin stores a salted one-way hash instead of the raw IP address.
Yes. Import a CSV file of up to 2,000 rows. Every row is validated and previewed before it is saved, and existing rules with the same source and match type are updated.
By default the data is kept to prevent accidental loss. Turn on “Delete plugin data on uninstall” in Settings if you want uninstalling to remove the plugin’s tables and settings.
The official WordPress.org listing always shows the current version, required WordPress and PHP versions, tested WordPress release, last update and installation instructions.
Use the official KM 404 Redirect Manager support forum. Include the plugin version, WordPress version and clear steps for reproducing the issue.
Release history
The official listing is the single live source for release information, so this page never shows a stale version number.
Open the WordPress.org development section to view the latest version, release notes, source code and previous releases. Compatibility requirements are shown on the main WordPress.org plugin page.
Ready to fix your broken links?
Install the official WordPress.org release, see which broken URLs your visitors hit most, and fix them with the right redirect.