Title: 404 Solution Author: Aaron Published: 5 Márta, 2017 Last modified: 15 Lúnasa, 2026 --- Search plugins ![](https://ps.w.org/404-solution/assets/banner-772x250.jpg?rev=1614763) ![](https://ps.w.org/404-solution/assets/icon-256x256.jpg?rev=1610739) # 404 Solution By [Aaron](https://profiles.wordpress.org/aaron13100/) [Download](https://downloads.wordpress.org/plugin/404-solution.4.3.3.zip) * [Details](https://ga.wordpress.org/plugins/404-solution/#description) * [Reviews](https://ga.wordpress.org/plugins/404-solution/#reviews) * [Installation](https://ga.wordpress.org/plugins/404-solution/#installation) * [Development](https://ga.wordpress.org/plugins/404-solution/#developers) [Support](https://wordpress.org/support/plugin/404-solution/) ## Description Stop losing visitors and search rankings to broken links. **404 Solution automatically redirects 404s to the right page** — not just your homepage — using a 7-engine matching pipeline that includes a spell-checking algorithm to find what visitors actually typed. **Example:** A visitor hits `/prodcut/awesome-item` (typo). Most 404 redirect plugins send them to your homepage. 404 Solution’s spell-checker finds `/product/awesome- item` and redirects them there automatically. #### Why 404 Solution Is Different Most redirect plugins fall into two categories: tools that require you to manually write every rule, or tools that blindly send every 404 to your homepage. 404 Solution does neither. * **A spell-checking algorithm that actually matches typos.** Using Levenshtein distance and N-gram scoring, 404 Solution catches `/prodcut/`, `/categroy/`, and `/wooocmmerce/` and finds the real destination — something no other free plugin does. * **7 matching engines, in sequence.** Slug match URL fix Title keywords Category/ tag paths Content search Spelling similarity Archive fallback. The first engine with a confident match wins. * **Automatic, from day one.** Install and activate. 404 Solution starts capturing and redirecting immediately. You can tune it; you don’t have to. * **Redirect management when you need it.** Full manual redirect editor, regex support, bulk actions, and CSV/JSON import compatible with Redirection’s export format. * **Debug mode that shows its work.** Enable debug logging and see exactly which engine chose a redirect and why — a level of transparency no competing plugin offers. * **Built for real-world hosting.** Self-healing database tables, auto-recovery from corruption, automatic log trimming, and zero wp-admin-wide banners. * **Ships with extras most plugins sell separately.** HTTP 410 Gone, 307/308/451 status codes, Google Search Console integration, REST API, WP-CLI support, email digest reports, and security probe detection — all free. #### Unlike plugins that blindly redirect to your homepage A 404-to-homepage redirect tells Google your broken URL is the same page as your homepage. That creates a soft 404 — a page Google may index as duplicate content, eroding crawl budget and ranking over time. 404 Solution redirects to the _correct_ destination, or returns a proper 410 Gone when content is permanently removed. Both outcomes are better for search engines and for visitors. #### How It Works 1. A visitor reaches a URL that returns a 404. 2. 404 Solution runs the URL through its 7-engine pipeline. 3. Each engine tries to find a confident match above its score threshold. 4. The first engine to find a match wins. The visitor is redirected to the correct page. 5. The redirect is logged. You can review, edit, or delete it from the dashboard. The whole process adds no perceptible latency for visitors on non-404 pages. The matching pipeline only runs when a genuine 404 occurs. #### Key Features **Intelligent Automatic Matching** * 7-engine matching pipeline (slug, URL fix, title, category/tag, content, spelling, archive) * Levenshtein distance + N-gram scoring catches genuine typos * Per-engine confidence thresholds — tune aggressiveness per engine * Conditional engine groups — override the matching strategy for specific URL patterns * Slug-change auto-detection — redirects created automatically when you rename a post * Trash/deletion monitoring — redirect created automatically when a post is deleted **Redirect Management** * Manual redirect editor with bulk actions * Full regular expression support * CSV and JSON import/export (compatible with Redirection plugin format) * .htaccess and Nginx server-level export * Per-post and per-term exclusion via meta box * HTTP status codes: 301, 302, 307 (method-preserving temporary), 308 (method-preserving permanent), 410 Gone, 451 Unavailable For Legal Reasons, and Meta Refresh * GDPR-compliant: IP addresses are hashed before storage — never written to disk in plain text **404 Monitoring and Logging** * Captures every 404 hit with referrer, user agent, and timestamp * Automatic log trimming with configurable disk usage limits * Security monitoring — flags vulnerability scanner probes (.env, /wp-config.php, phpMyAdmin, etc.) **Reporting and Diagnostics** * Stats dashboard with traffic trend charts (404s, redirects, captures over time) * Email digest reports * Debug logging — see which engine fired and why * Google Search Console integration — import crawl errors and push fixes * Internal link scanner to find broken links before visitors do **Developer and Integrator Tools** * REST API for redirect management * WP-CLI subcommands (list, create, delete, import, export) * Scheduled maintenance cron * Full WordPress Multisite support **Compatibility** * WooCommerce (products, variations, categories, custom URLs) * Yoast SEO, Rank Math * WPML, Polylang, TranslatePress * Easy Digital Downloads * All custom post types and custom taxonomies #### Perfect For * **eCommerce sites** (WooCommerce, EDD) with changing product URLs * **Content sites** with evolving permalink structures * **Migrated sites** where old URLs need to map to new content * **Large sites** with thousands of pages where manual redirects are impractical ## Screenshots [⌊Redirect Dashboard — Active redirects with color-coded status badges (301, 302, 307, 308, 410, 451), match confidence scores, and engine names. Filter by manual, automatic, or regex. Sort by any column.⌉⌊Redirect Dashboard — Active redirects with color-coded status badges (301, 302, 307, 308, 410, 451), match confidence scores, and engine names. Filter by manual, automatic, or regex. Sort by any column .⌉[ **Redirect Dashboard** — Active redirects with color-coded status badges (301, 302, 307, 308, 410, 451), match confidence scores, and engine names. Filter by manual, automatic, or regex. Sort by any column. [⌊Statistics — Summary cards for redirects, captured URLs, and daily stats. Match confidence donut chart and 30/90-day trend analytics for 404 hits.⌉⌊Statistics — Summary cards for redirects, captured URLs, and daily stats. Match confidence donut chart and 30/90-day trend analytics for 404 hits.⌉[ **Statistics** — Summary cards for redirects, captured URLs, and daily stats. Match confidence donut chart and 30/90-day trend analytics for 404 hits. [⌊Debug Log — Real-time debug output showing engine processing, spell-check scoring, candidate evaluation, and redirect decisions for every 404 request.⌉⌊Debug Log — Real-time debug output showing engine processing, spell-check scoring, candidate evaluation, and redirect decisions for every 404 request.⌉[ **Debug Log** — Real-time debug output showing engine processing, spell-check scoring, candidate evaluation, and redirect decisions for every 404 request. [⌊Captured 404s — Every unhandled 404 logged with URL, hit count, first-seen and last-seen timestamps. Filter by captured, ignored, or later status.⌉⌊Captured 404s— Every unhandled 404 logged with URL, hit count, first-seen and last-seen timestamps. Filter by captured, ignored, or later status.⌉[ **Captured 404s** — Every unhandled 404 logged with URL, hit count, first-seen and last-seen timestamps. Filter by captured, ignored, or later status. [⌊Settings — Configure automatic redirect behavior, custom 404 page, auto-deletion rules, default redirect type, and notification preferences.⌉⌊Settings — Configure automatic redirect behavior, custom 404 page, auto-deletion rules, default redirect type, and notification preferences.⌉[ **Settings** — Configure automatic redirect behavior, custom 404 page, auto-deletion rules, default redirect type, and notification preferences. [⌊Email Digest — Weekly HTML email summarizing captured 404s, resolution rate, and a ranked table of top 404 URLs with color-coded hit badges.⌉⌊Email Digest — Weekly HTML email summarizing captured 404s, resolution rate, and a ranked table of top 404 URLs with color-coded hit badges.⌉[ **Email Digest** — Weekly HTML email summarizing captured 404s, resolution rate, and a ranked table of top 404 URLs with color-coded hit badges. ## Installation 1. Unzip the files and upload the contents to `/wp-content/plugins/`. 2. Activate the plugin. 3. Use the `Settings -> 404 Solution` options page to set the options. ## FAQ ### How is this different from the Redirection plugin? Redirection is a manual redirect manager — you write the rules, it applies them. That is useful when you know in advance which URLs will break. 404 Solution handles the URLs you don’t know about: it automatically finds the right destination using a 7-engine matching pipeline and a spell-checking algorithm. **Example:** If a visitor types `/prodcut/awesome-item`, Redirection does nothing unless you manually created that specific rule. 404 Solution finds `/product/awesome- item` automatically. The two plugins are complementary. Many sites run both: Redirection for planned migrations and 404 Solution for everything else. ### How is this different from 404 to 301? 404 to 301 redirects ALL 404 errors to one fixed destination (usually the homepage). 404 Solution finds the actual page the visitor was looking for. Sending visitors to your homepage is poor UX and can create soft 404 problems in Google Search Console. ### How is this different from WP 404 Auto Redirect to Similar Post? WP 404 Auto Redirect uses keyword matching, which works when the URL contains recognizable words from a post title. It fails on character-level typos — a URL like `/prodcut/` has no keyword that matches “product.” 404 Solution adds Levenshtein spell-checking, which catches transpositions and typos regardless of whether the keywords match. It also includes: full 404 logging, manual redirect management, CSV import/export, 410/451 status codes, GDPR IP hashing, debug logging, REST API, and WP-CLI support. ### What HTTP status codes are supported? **301** (permanent redirect), **302** (temporary redirect), **307** (temporary, method-preserving), **308** (permanent, method-preserving), **410 Gone** (correct response for permanently deleted content — better for SEO than a 301 to homepage),** 451 Unavailable For Legal Reasons**, and **Meta Refresh** (client-side HTML redirect). Using 410 instead of redirecting deleted content to your homepage produces better results in Google Search Console and prevents soft-404 indexing. ### Will this slow down my site? No. The matching pipeline only runs when a genuine 404 occurs — normal page loads are unaffected. For large sites, 404 Solution uses N-gram indexing and caching tables to keep matching fast. Once a redirect is established, subsequent hits are served from the redirect table directly, bypassing the pipeline. ### Does it work with WooCommerce? Yes. 404 Solution indexes WooCommerce products, product variations, product categories, and tags. When a product URL changes or a product is deleted, the appropriate redirect is created automatically. ### What happens when a redirect destination is deleted? 404 Solution detects when a destination post is trashed or deleted and flags the redirect. Redirects pointing to deleted content are highlighted in the redirect table so nothing slips through unnoticed. The daily maintenance cron automatically removes orphaned auto-redirects. ### Can I import redirects from another plugin? Yes. 404 Solution imports CSV and JSON in the Redirection plugin’s export format. It can also directly import from Rank Math, Yoast SEO, AIOSEO, and Safe Redirect Manager’s database tables from the Tools tab. ### Is it GDPR compliant? Yes. IP addresses are hashed using a one-way algorithm before storage; the original IP is never written to disk. Log retention limits are configurable. By default no data is transmitted to external servers. The “Help the developer by sending error logs” admin checkbox (default off) and the uninstall feedback modal are the only opt-in paths that send data to the plugin author’s reports server. See the plugin’s privacy policy stub at `docs/privacy.md` for the retention period for rows keyed by site_url, the data-subject erasure path, and the processing region for the reports endpoint. ### Does it support regex? Yes. Manual redirect rules support full regular expression syntax for source URLs. Capture-group replacements can use either full HTTP(S) destination URLs or site- relative paths such as `/archive/$1`. ### Does it work with WPML, Polylang, or TranslatePress? Yes. 404 Solution detects the active language from the multilingual plugin’s API and resolves redirect destinations to the correct translated version automatically. ### Can I use WP-CLI to manage redirects? Yes. 404 Solution includes WP-CLI subcommands for listing, creating, deleting, importing, and exporting redirects — useful for scripted migrations and DevOps workflows. ### Does it work after a site migration? Yes. 404 Solution is ideal for site migrations: slug-change auto-detection, URL typo correction (strips `.html`, `.php`, `.asp`), hierarchical category path resolution, and regex redirects for bulk pattern changes. ### Can I redirect all 404s to a specific page? Yes. Go to **Settings 404 Solution Redirect all unhandled 404s to** and select your preferred fallback page. ### How do I manage log files and disk usage? Log cleanup is automatic. Configure maximum log size under **Options General Settings Maximum log disk usage**. You can also manually clear logs from the Logs page. ### Can I exclude certain URLs from being processed? Yes. Use **Options Advanced Settings Files and Folders Ignore Strings** to add paths to ignore. Per-post and per-term exclusion is also available via the edit screen checkbox. ### How do I exclude a specific post or page? Edit the post/page and check the “Exclude from 404 Solution redirects” checkbox in the sidebar. Category and tag terms can also be excluded via term meta on the edit screen. ### Have you written any other programs? Check out [AJ Experience](https://www.ajexperience.com/) for other useful tools and resources. ## Reviews ![](https://secure.gravatar.com/avatar/db387f89bb5ba2ebc324f12526d8d30c6a6cc8df0df692ee6757cf0c18bb57a6? s=60&d=retro&r=g) ### 󠀁[Essential after a migration](https://wordpress.org/support/topic/essential-after-a-migration/)󠁿 [Frédéric POTIER](https://profiles.wordpress.org/plutoonik/) 15 Lúnasa, 2026 1 reply When a site’s domain changes, or numerous pages get new URLs, this extension saves hours of work and keeps your SEO stress-free. ![](https://secure.gravatar.com/avatar/b10f2838ce6c70677f8202067a69b7066270b3de11431f46c8b37dad4fda3132? s=60&d=retro&r=g) ### 󠀁[Plugin is broken. Don’t install it](https://wordpress.org/support/topic/plugin-is-broken-dont-install-it/)󠁿 [Bruno Martinez](https://profiles.wordpress.org/brmartinez/) 1 Meán an tSamhraidh, 2026 1 reply Unfortunately, I have to warn that this plugin is full of bugs and installation is not recommended. I’ve been trying to point this out to the developer and get them fixed. It’s been almost 2 months, and basic functions of the plugin are still broken. Very sad to see this, as the idea of the plugin has potential. ![](https://secure.gravatar.com/avatar/e9addbf23d2e222f1c426a091b6e83b23f0aea1df2ef55254396ae36ffb07b6f? s=60&d=retro&r=g) ### 󠀁[AJAX error](https://wordpress.org/support/topic/ajax-error-78/)󠁿 [ixoyewarrior](https://profiles.wordpress.org/ixoyewarrior/) 30 Aibreán, 2026 3 replies when I look at all or captured 404s I get this message after a lengthy spinning wait:404 Solution: AJAX error while updating the table.HTTP status: textStatus: timeout errorThrown: timeout action: ajaxUpdatePaginationLinks subpage: abj404_captured ![](https://secure.gravatar.com/avatar/d1a6ede61023b135c5288e1c28a9cf3ec22babdae7333a48d2f65d2b68699ae8? s=60&d=retro&r=g) ### 󠀁[Works as expected; fast support!](https://wordpress.org/support/topic/works-as-expected-fast-support/)󠁿 [PluginRx](https://profiles.wordpress.org/apos37/) 30 Aibreán, 2025 1 reply I haven’t tried all of the features that this plugin has to offer as I intended to just use it temporarily to redirect users to a designated 404 page, but it does so much more. I really appreciate the logs that show me the crazy urls people/bots are trying to access. Had a minor issue with a php notice that I reported, and the developer quickly jumped on it and released an update. Kudos! ![](https://secure.gravatar.com/avatar/89f236fbda264a5de710ae9168d31437b3bd4c5468973c46a249a6688e62a72c? s=60&d=retro&r=g) ### 󠀁[Thank you for your great plugin!!!!](https://wordpress.org/support/topic/thank-you-for-your-great-plugin-2/)󠁿 [frondmedia](https://profiles.wordpress.org/frondmedia/) 3 Deireadh Fómhair, 2024 1 reply It is working great, frequent updates from the developer and is our seo saver!!! Thank you for your great job! ![](https://secure.gravatar.com/avatar/3b2b6685590fff4e957ab3f2d881691c4d6fb4ae6decce9930db3d1086069b65? s=60&d=retro&r=g) ### 󠀁[Type to filter error](https://wordpress.org/support/topic/type-to-filter-error/)󠁿 [fikret20](https://profiles.wordpress.org/fikret20/) 1 Eanáir, 2024 2 replies Ajax error when I want to search in the filtering section. I get Result: “parsererror”, error: {} error. Is there a solution? Thank you in advance for your reply. [ Read all 44 reviews ](https://wordpress.org/support/plugin/404-solution/reviews/) ## Contributors & Developers “404 Solution” is open source software. The following people have contributed to this plugin. Contributors * [ Aaron ](https://profiles.wordpress.org/aaron13100/) “404 Solution” has been translated into 4 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/404-solution/contributors) for their contributions. [Translate “404 Solution” into your language.](https://translate.wordpress.org/projects/wp-plugins/404-solution) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/404-solution/), check out the [SVN repository](https://plugins.svn.wordpress.org/404-solution/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/404-solution/) by [RSS](https://plugins.trac.wordpress.org/log/404-solution/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### Version 4.3.3 (August 12, 2026) **New Features** * Regex redirect destinations can now be site-relative paths such as `/archive/ $1`, not only full http(s):// URLs. **Bug Fixes** * Fixed the Page Redirects and Captured 404s tabs being able to hang after their data was already built. When something else on the site holds an output buffer open that cannot be closed, whether that is PHP output compression or another plugin, the response could keep trying to flush buffers until the host’s execution limit killed the request. Flushing is now bounded, so the table finishes rendering instead of spinning. * Fixed a fatal error that could happen while updating from 4.2.x, when the server’s PHP bytecode cache was still handing out the previous version’s files as the new ones loaded. This guard protects future updates; it cannot protect the update that installs it. * Fixed a crashed or killed request being able to leave an internal lock behind, which left redirect lookups on a slower fallback path until the lock expired ( more than 24 hours was observed on one site). Locks are now released even when the request dies, and an abandoned lock is reclaimed after at most 5 minutes instead of after the server’s maximum execution time. * Fixed “Illegal mix of collations” database errors on sites whose plugin tables do not all share the same collation. This affected 404 log cleanup, the admin list counts, the email digest, and the dead-destination check. * Fixed the plugin running a schema-wide collation repair in the middle of an admin page load, which could make that page slow or time out. The repair now happens outside the page request. * Fixed slow sorting on the Captured 404s tab. The timestamp sort had no supporting database index, so a large site re-sorted the whole table on every page load. * Fixed the plugin trusting one of its own sort indexes by name alone. A database server silently narrows an index when a column it referenced is dropped, and an index narrowed that way was treated as correct forever, so the sorts it was built for scanned the entire table instead of reading a single page of rows. Indexes are now compared against the definition the plugin ships and rebuilt when they differ. * Fixed the plugin rebuilding a database index on the strength of index information it could not read. When a database server left out or garbled the field that says whether an index is unique, the plugin decided the index differed from the one it ships and repaired it, which on the page-suggestion cache meant emptying that table and rewriting the index. Index information that cannot be read is now treated as unknown, and an index the plugin cannot describe is left alone. * Fixed the Page Redirects and Captured 404s tabs waiting on their own row counts on large sites. Pagination and the per-status counts now load in separate stages, and a count that is still being computed is shown as incomplete instead of holding up the table. * Fixed a regex redirect whose source pattern starts with an anchor (for example` ^/products/(.*)`) being rewritten on save into a pattern that could never match. * Fixed the Add Redirect dialog rejecting valid regex destinations, and checking them against a stale copy of the validation rules after an update. * Fixed the “Hits” counts on the admin tabs falling behind. The roll-up that keeps them current was no longer running from a page view, and the counts could also sit empty on sites whose WordPress cron is backed up. Both paths are restored. * Fixed 404 URLs containing `@` (retina images such as `logo@2x.png`) and PHP static- call frames in stack traces being mangled by the redaction that runs before a debug log or automatic report is written. * Fixed page suggestions staying poor for months after an interrupted rebuild. A partially built suggestion cache recovered at about 50 entries a day rather than rebuilding; it is now completed at full rebuild speed. * Fixed a multisite network where deleting a site part way through the page-suggestion rebuild could leave a later site with an empty suggestion cache that was marked fully built and never rebuilt. The rebuild now tracks the last site it finished instead of counting positions in a list that shifts whenever a site is removed. * Fixed transient database failover and connection-state errors, including Galera nodes that are temporarily unavailable and “Commands out of sync,” being treated as permanent failures. Affected queries now recover and retry through the shared database path. * Fixed an admin table database failure being mistaken for a successful empty result, which could make the table appear empty instead of showing the real error. * Fixed the 404 and redirect trend charts reading all zeros on sites whose database server is not set to UTC, which is common on shared hosting. Each database row was matched to a calendar day by comparing two dates produced in different time zones, so on those sites no row ever matched a day and the chart drew a flat line with no error shown. The Search Console date range was built the same way and is fixed too. * Fixed the “Post types” and “Categories” settings fields being able to alter the database queries built from them. Values from those two fields were placed into queries without being escaped, so a value containing a quote could change what the query did. Both fields are now escaped, and text carrying invalid characters is repaired before it reaches the database. * Fixed automatic redirects being able to save a destination that cannot be reached. The destination was checked as a positive number but stored exactly as entered, so a value such as `-3` was checked against page 3 and then stored as `-3`. Automatic redirects are created with nobody watching, so nothing later would have questioned it. * Fixed 404 URLs losing their hit counts and their “View Logs” row action when their log rows had no canonical URL recorded. Those rows were dropped from the hit-count roll-up entirely, with nothing to say so. * Fixed the “Hits” columns going stale, or being rebuilt on every check along with a repeating admin notice, on sites whose database server is not set to UTC. The age of the hit-count roll-up was measured by comparing a time the database rendered in its own time zone against a time measured in UTC, so it was wrong by that server’s offset, in one direction or the other depending on which side of UTC the server sits. **Improvements** * The hit-count roll-up no longer runs at the very end of an admin request, where it added as much as 21 seconds to the page on a 900,000-row test site. * On LiteSpeed servers the admin table response is handed back as soon as it is ready, instead of waiting for the rest of the request to finish. * Creating, editing or deleting a redirect no longer scans the whole WordPress options table. The plugin was still clearing a results cache it stopped using in 4.3.1, and the pattern it searched for could not use an index, so on a site with a large options table every redirect change read the entire table to delete nothing. * When an admin action fails because the server or its gateway rejected the request, the message now names the underlying failure (for example “502 Bad Gateway”) instead of a generic “An error occurred”, and the full detail is written to the browser console. Saving settings, restoring defaults, switching settings mode and trashing a redirect each had their own copy of this handling, and two of them discarded the failure entirely. * Automatic error reports and support previews now include log evidence for the error they describe, even when the error falls outside the most recent log tail. Admin table retries also preserve a diagnostic trail under the plugin’s shipped default settings. #### Version 4.3.2 (July 11, 2026) * FIX: Fixed the email digest sending every day even when the notification frequency was set to Weekly (thanks to gardendarts for reporting this). The weekly/daily cadence is now enforced against the time the last digest was actually sent, and changing the frequency in Settings now takes effect on the very next save instead of the next unrelated one. * FIX: Fixed automatic error and heartbeat reports silently failing to send on some sites when an internal reporting component was unavailable. * FIX: Fixed debug logs and automatic reports sometimes over-redacting the plugin’s own file names, option names, and URLs, including incorrectly truncating URLs that contained a query string. * FIX: Fixed a rare issue where saving, publishing, or deleting content, or changing a category, during a plugin update could interrupt a scheduled background maintenance task. * Improvement: Hardened several internal WordPress integration points (404 handling, REST API setup, log maintenance, and permission checks) so an unexpected internal error in one can no longer interrupt that request or affect other plugins. * Improvement: Out-of-memory diagnostic reports now preserve the exact memory sizes involved, making them easier to diagnose. * Improvement: Removed an internal AJAX diagnostics footer that no longer reflected real admin activity. * Improvement: If you’ve opted in to “Help the developer with error logs and usage stats,” the optional weekly status ping now sends on a predictable weekly cadence( once the plugin’s been active 5+ days) instead of a rare random daily chance that averaged about once every 6 months. Same opt-in checkbox and same aggregate- only data (site version, URL, 404/redirect counts); just a steadier heartbeat. * New: Added a “Never” option to the Email notification frequency dropdown, so you can fully turn off 404 email notifications without switching to Instant mode and separately zeroing the threshold. * New: Added a “Your Diagnostic Data” card to the Options tab so you can download or delete the diagnostic data this plugin has reported for your site, in line with GDPR data access and erasure rights. #### Version 4.3.1 (June 26, 2026) * FIX: Fixed an out-of-memory error (thanks to johnegg and kalshyre for reporting this). * FIX: Fixed other things that looked like possible out-of-memory errors during maintenance. * Improvement: Made automatic error reporting more robust to cover OOM as best as possible as well as other failure types. #### Version 4.3.0 (June 12, 2026) **Bug Fixes** * Fixed locale-stale labels in the Page Redirects view cache by storing status and type as integer codes only, translating labels at render time, and dropping the legacy translated-label columns during upgrade. * Fixed the Page Redirects and Captured 404s admin tabs still occasionally failing to load on high-traffic sites running 4.2.0. The 4.2.0 release notes claimed this was fixed, but only the cache-warmup race was addressed. A separate internal“ mutation watermark” gate could still abort the cache rebuild mid-stage when 404 traffic arrived during the rebuild, and surface the same “Could not finish refreshing data” message at the 45-second budget. That gate and its supporting machinery( watermark counter table, admin-mutation gate, view-build watermark stamping) have now been removed in full. On Bruno-class data (about 30,000 active redirects, about 384,000 hit rows, sustained 1 request per second or higher 404 traffic), the admin tabs hydrate within budget across consecutive refreshes. * Fixed a stale “No ID(s) found” notice appearing after a redirect was edited and saved successfully. The notice from the prior screen is now cleared so the success message stands alone. * Fixed a stuck “Refreshing data… (stage 4)” badge that could remain on the Page Redirects pagination strip after a background refresh failed. The strip now collapses placeholder-only rows on a failed table load, and the error notice no longer competes with the 5-star review prompt for attention. * Fixed generic “Something went wrong” messages on admin AJAX errors. The underlying cause is now appended in parentheses so the error is self-diagnosable, and the multi-stage diagnostic detail is tucked behind a collapsed Details panel. * Fixed `wp abj404 list` not returning redirects that were just created via `wp abj404 create` in the same session, and corrected the `--status=manual` filter so manually-created redirects are returned. * Fixed CSV-imported redirects not appearing in the Page Redirects table immediately after import. The cached view is now rebuilt synchronously when the import completes, so the table reflects the new rows on the next page load. * Fixed a “table doesn’t exist” error path that could fire during a partial install or upgrade. The data layer now tolerates an unprepared `$wpdb` and surfaces a clean degraded state instead of a fatal. * Fixed the plugin’s settings defaults not being available on the uninstall path, which could leave a stray option behind on some sites. * Fixed a duplicate-accessible-name accessibility warning on the redirects list. The “Add Redirect” submit button inside the modal is now labeled “Add”, which removes the collision with the page-level “Add Redirect” action button. * Fixed a fatal that could occur on the Plugins admin screen when `wp-admin/includes/ plugin-install.php` was unavailable on hardened hosts (the include is now guarded with `is_readable`). * Fixed a fail-open default in the REST captured-404s status filter that could return rows from an unintended status when an unknown filter value was supplied. * Fixed the URL and Destination column-sort “being prepared” progress indicator that could stay stuck at 0% on large sites where a security plugin blocks the WordPress cron loopback. The one-time sort-key preparation is now driven by the admin’s own page view in the background, with a longer and gentler retry window, so column sorting becomes available without depending on WP-cron, and a transient timeout no longer halts the progress. **Improvements** * Several admin surfaces were restyled to match native WordPress chrome and feel quieter on the eye: the top sub-navigation now uses standard `.nav-tab` styling; the Edit Redirect form follows the native `form-table` shape; list-table filter rows use subsubsub pipe-separated links; status badges and pills use the bordered- label shape; checkbox columns and column-header padding match core WP list tables; AJAX error notices use the native `.notice-error` shape; and the self-healing dashboard notice routes through the standard notice template. * Several internal queries that scanned the full `information_schema`, post-type table, or content-keywords index on large sites are now bounded, removing a needless cost during background cache rebuilds. No behavior change for typical sites; smoother performance on sites with thousands of post types or very large content tables. * Changed the internal admin-notice payload schema to store translated message and guidance text directly, removing the message catalog indirection. No user- facing behavior change is expected. * When a background refresh fails, a Support button is now mounted directly on the failure notice so the report path is one click instead of a hunt through Settings. #### Version 4.2.0 (May 23, 2026) **Bug Fixes** * Fixed the “Page Redirects” and “Captured 404s” admin tabs occasionally failing to load on busy sites. The cache-warmup pipeline could race against ongoing 404 traffic and report that the data snapshot was missing even when the underlying query had succeeded. Admin tables on high-volume sites now load reliably. **Improvements** * Substantial internal refactor of the data-access, view-build, and admin-mutation layers for long-term maintainability. No visible behavior change is expected; the version bump from 4.1.x to 4.2.0 reflects the size of the change. #### Version 4.1.19 (May 17, 2026) **New Features** * Regex redirects are now auto-detected. When you save or import a redirect that contains regex characters (wildcards, brackets, pipes), the plugin automatically marks it as a regex redirect and applies the correct syntax. No need to manually check the “Treat as regex” box. An admin notice confirms the auto-promotion with Edit and Undo links. * Debug logs now automatically redact sensitive server details (database name, table prefix, filesystem paths) so logs can be shared safely without manual editing. **Bug Fixes** * Fixed the Confidence dropdown filter on admin tables only working on the initial page load. Changing the filter and then navigating pages or waiting for the background refresh would reset it to “All”, showing every row. * Fixed invalid regex patterns in CSV imports crashing the import. Invalid patterns are now validated during import and suppressed at runtime instead of causing errors. * Fixed the repair-and-retry path continuing to report an error after the repair succeeded. The error is now cleared immediately after a successful repair. * Fixed a potential SQL ambiguity error in log queries on sites with certain JOIN configurations. * Fixed all 6 scheduled tasks not being removed when the plugin is deactivated. Previously some cron hooks were left behind and would trigger errors until manually cleared. * Fixed the “Undo” link on regex auto-promotion notices not reverting the URL on the next page load. The original URL is now correctly restored along with the Manual status. * Fixed a rare race on shared hosting where a dropped database connection during the admin table rebuild could let a second worker drop the rebuild’s working table out from under the first, producing “Table doesn’t exist” or “Can’t find. frm file” errors. The rebuild now releases its database lock between each step so a dropped connection loses at most one step of progress instead of the entire 11-step run. **Improvements** * Bulk CSV and WP-CLI imports are significantly faster. A 10,000-row import that previously issued ~60,000 extra cache-invalidation queries now batches them into a single invalidation at the end. * The admin settings page now validates URL length and rejects negative numeric values, preventing misconfigured redirects. **Internationalization** * Added translations for 6 new strings in all 12 language files. #### Version 4.1.18 (May 13, 2026) **Bug Fixes** * Fixed the admin table cache rebuild getting stuck on the same step after a dropped database connection. The rebuild now auto-resumes from where it stopped on the next request, instead of retrying the same failing query forever. * Fixed admin actions that hit an expired session nonce showing a generic “security check failed” error. The session is now silently refreshed and the action retried, so the expiry is invisible to the administrator. * Fixed transient invalid AJAX responses on admin tables producing “undefined” errors. The admin pages now validate the response shape before reading it and surface a clear error instead. * Fixed the “missing database table” admin notice being cleared by the next successful query in the same request, so the admin never saw it. The generic auto-clear now skips the missing-table notice; that notice is cleared only by the dedicated repair-success path. **Improvements** * Captured 404s and Page Redirects admin tables load noticeably faster on large sites. The total log-count query is now cached on the maximum log id (avoiding a full log-table scan on every page load), log queries no longer sort by non- indexed columns, the Most Unused Redirects report reads from the pre-aggregated hits rollup instead of scanning raw logs, and the dashboard activity trend is cached between admin page loads. * When WordPress cron is broken and the log hits rollup falls behind, the plugin now surfaces an admin notice on its own pages explaining how to fix it, instead of silently letting the admin tables show stale numbers. **Internationalization** * Added translations for 13 admin strings that were previously displayed in English even on non-English sites. #### Version 4.1.17 (May 10, 2026) **Bug Fixes** * Fixed repeated “Access denied” errors and silently-stuck Captured 404s and Page Redirects pages on shared and managed hosting environments where certain database privileges are restricted. The rebuild now skips the affected step and continues, instead of retrying the same denied operation on every cron run and emailing the site administrator. * Fixed the rebuild silently never starting on managed or sharded MySQL services( such as PlanetScale and Vitess) that do not support standard MySQL named locks. The plugin now uses an alternate locking mechanism on these hosts. * Fixed the rebuild getting permanently stuck after a previous run was interrupted( for example, by a server restart mid-rebuild). The plugin now detects and cleans up leftover state at the start of the next rebuild so it can complete normally. * Fixed the rebuild silently waiting forever when WordPress scheduled tasks (cron) are disabled and no external cron is configured. The plugin now shows a clear admin notice with guidance on how to resolve it. * Improved compatibility with multisite networks during long-running rebuilds that span multiple background tasks. * Improved compatibility with persistent object caches (Redis, Memcached) so that rebuild progress is reliably saved even when the cache layer is briefly inconsistent. * Improved compatibility with HyperDB, LudicrousDB, and other custom database drop- ins. **Improvements** * The plugin now self-detects unusual PHP and database hosting limits (memory limit, time limit, strict SQL modes, query packet size) at the start of each rebuild and adapts to work within them, instead of failing on restrictive hosts. #### Version 4.1.16 (May 8, 2026) **Bug Fixes** * Fixed the Captured 404s and Page Redirects admin pages getting stuck on “Creating build buffer (1/11)” forever on hosts with the standard 30-second PHP execution limit (the default on most shared hosting). The cache rebuild was yielding before inserting any rows because it was reserving more PHP time than the request actually had, so each rebuild request returned without making progress. The first batch of every rebuild step now always runs, so the rebuild reliably moves forward on a typical 30-second host. * Fixed Captured 404s and Page Redirects admin pages still failing to load when the database killed a single rebuild step (max statement time exceeded, lost connection, lock timeout): the entire rebuild used to give up, but it now resumes on the next request from where it left off, at every step. * Fixed brief network blips and intermittent 5xx responses during a long rebuild causing the admin page to show “Could not finish refreshing data” instead of continuing to wait. Transient errors are now treated as a no-progress tick and the page keeps polling. * Fixed the rebuild getting stuck retrying the same single-statement step (index build, hit-count update, or sort-index step) when the host’s database statement timeout was shorter than that step needed to complete. Those steps used to retry with the same too-tight timeout forever; now the per-query timeout is extended for the retry so the step can finish. **Improvements** * The admin-table rebuild now adapts its batch size to the host. If a batch is killed by the database, the next attempt uses a smaller batch, and the smaller size is remembered for the rest of the rebuild so slow shared hosts converge on a size they can actually finish. * Per-query timeouts during the rebuild are now sized to the host’s own statement timeout (MariaDB max_statement_time / MySQL max_execution_time), so a kill produces a clean classifiable error the rebuild can resume from rather than a dropped connection. #### Version 4.1.15 (May 6, 2026) **Bug Fixes** * Fixed a plugin load fatal on PHP 7.4 to 8.1 hosts that was introduced in 4.1.14. A constant inside a trait (added with the staged view rebuild) is only valid in PHP 8.2 and later; the declared minimum is PHP 7.4, so this restores compatibility for all supported PHP versions. #### Version 4.1.14 (May 6, 2026) **Bug Fixes** * Fixed Captured 404s and Page Redirects admin tables getting stuck or returning“ Could not load table data” on very large sites while the table cache was being rebuilt. The rebuild now resumes in small background steps and the admin screen keeps polling progress until the data is ready. * Fixed a race where an admin table could retry too soon after a background rebuild started, causing repeated loading failures instead of waiting for the rebuilt data. **Improvements** * The Captured 404s and Page Redirects admin tables now use a staged cache rebuild that splits expensive destination, status, and hit-count work into bounded batches. Large sites should see more reliable table loading without long-running AJAX requests. * Added clearer in-page progress handling while the admin table cache is warming, so administrators can tell the plugin is still working instead of seeing a static loading state. #### Version 4.1.13 (May 2, 2026) **Bug Fixes** * Fixed “Could not load table data” timeouts on the Captured 404s and Page Redirects admin tables. On sites with a large WordPress posts table, the count query now skips unrelated JOINs when no search filter is active, and admin table caches are warmed in the background across multiple short requests instead of one long one — so the tables reliably load even when individual queries are slow. **Improvements** * The plugin admin footer now includes a collapsible Debug Info section showing per-stage AJAX timings, errors, and database query timings for the Captured 404s and Page Redirects views. When reporting a slow or stuck admin table, you can copy this directly without opening browser developer tools. * SQL errors are now recorded before any automatic recovery (table repair, retry with a relaxed collation) runs, so the original cause of a failing query stays visible in the support log instead of being overwritten by the recovery attempt’s own messages. #### Version 4.1.12 (May 1, 2026) **Bug Fixes** * Fixed Captured 404s and Page Redirects table AJAX requests timing out while background log-cache maintenance was running. Maintenance that is triggered by an AJAX table load now runs through scheduled background tasks instead of shutdown work tied to the same HTTP request. * Fixed debug-log setup failing on sites with negative or fractional WordPress timezone offsets. * Fixed diagnostic logging paths that could throw while trying to report another error, which could hide the original problem behind a secondary logging failure. #### Version 4.1.11 (May 1, 2026) **Bug Fixes** * Fixed loss of captured-404 history when the database performed automatic repair of a crashed log table. The plugin previously dropped and recreated the affected table after repeated repair failures, destroying logged hits in the process. It now leaves the table alone if repair cannot succeed, preserving your captured- 404 history. * Fixed loss of log data during repair of damaged plugin tables that were missing their primary key column. This was the underlying cause of the log-history loss reported during the 4.1.6 to 4.1.7 upgrade. The repair now preserves all existing rows instead of recreating the table from scratch. * Fixed timeouts during the nightly log-cache rebuild on sites with aggressive log retention. The rebuild now reliably completes within shared-host time limits. **Improvements** * The Captured 404s list and other admin views that read log data now load substantially faster on sites with large log tables. A new indexed column replaces a slower per-row computation; existing sites are updated in the background during nightly maintenance and speed up over time. #### Version 4.1.10 (Apr 30, 2026) **Bug Fixes** * Fixed disk-full, read-only, and crashed-table conditions encountered during log flush and N-gram cron scheduling escalating to error level and triggering developer email reports. These hosting conditions are now classified as warnings — the plugin already degrades past them — so they no longer spam the admin’s inbox. * Fixed admin AJAX error notices showing only generic HTTP/textStatus information when a paginated admin view timed out or returned a 500. The notice now includes the elapsed request time, the server-side processing stage that was in flight when the failure occurred, and the redacted SQL of the failing query when available, so the cause is identifiable without a server log dump. * Fixed a parse-time fatal on PHP 7.4 through 8.1 caused by two trait-level constants introduced with the canonical-URL backfill work. The constants are now declared on the using class so the trait file parses cleanly on every supported PHP version. **Improvements** * The Page Redirects and Captured 404s admin views are now significantly faster on installs with very large redirects tables. Each redirect now stores a precomputed canonical URL that is indexed and JOINed against the hits rollup, eliminating the per-row CONCAT/TRIM evaluation that could time out the admin AJAX request on sites with hundreds of thousands of captured rows. The column is backfilled in chunks during the upgrade and the nightly maintenance cron, so large sites converge across cron ticks without blocking any single request. * The daily cron that flags dead-destination redirects now scales with URL count rather than raw log-row count. The query now JOINs against the precomputed `logs_hits` rollup with a new `failed_hits` column, completing in milliseconds even on sites with millions of log rows where it previously timed out. * The admin AJAX timeout for explicit user actions (sorting, filtering, pagination) was raised from 15 seconds to 45 seconds. Background detect-only refreshes still use the tight 15-second budget, so the longer timeout only applies when the admin is actively waiting. * Several catch blocks across the plugin that previously swallowed exceptions silently now emit a warning breadcrumb to the support log, so unexpected failure paths are visible in support bundles instead of vanishing. ## Meta * Version **4.3.3** * Last updated **2 lá ago** * Active installations **10,000+** * WordPress version ** 5.0 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Languages * [Chinese (China)](https://cn.wordpress.org/plugins/404-solution/), [Dutch](https://nl.wordpress.org/plugins/404-solution/), [English (US)](https://wordpress.org/plugins/404-solution/), [German](https://de.wordpress.org/plugins/404-solution/), and [Russian](https://ru.wordpress.org/plugins/404-solution/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/404-solution) * Tags * [404](https://ga.wordpress.org/plugins/tags/404/)[404 redirect](https://ga.wordpress.org/plugins/tags/404-redirect/) [broken links](https://ga.wordpress.org/plugins/tags/broken-links/)[redirect](https://ga.wordpress.org/plugins/tags/redirect/) [spell check](https://ga.wordpress.org/plugins/tags/spell-check/) * [Advanced View](https://ga.wordpress.org/plugins/404-solution/advanced/) ## Ratings 4.9 out of 5 stars. * [ 43 5-star reviews ](https://wordpress.org/support/plugin/404-solution/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/404-solution/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/404-solution/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/404-solution/reviews/?filter=2) * [ 1 1-star review ](https://wordpress.org/support/plugin/404-solution/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/404-solution/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/404-solution/reviews/) ## Contributors * [ Aaron ](https://profiles.wordpress.org/aaron13100/) ## Support Issues resolved in last two months: 3 out of 3 [View support forum](https://wordpress.org/support/plugin/404-solution/)