Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

404 to 301 · Version history

404 to 301 changelog and version history

Latest version
4.0.5
Sep 30, 2026 (1 month ago)
Releases
61
since 2014
In the last year
7
about one every 21 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 20146 releases
  • 201515 releases
  • 201616 releases
  • 20171 release
  • 20183 releases
  • 20193 releases
  • 20201 release
  • 20215 releases
  • 20223 releases
  • 20251 release
  • 20267 releases

20267 releases

  1. 404 to 301 4.0.5Latest

    • Fix: On sites whose admin is in a language that translates the “Redirects” menu, such as Dutch, the 404 Logs, Settings and About Us pages were blank.
    • Fix: On a server running an outdated version of PHP or WordPress, the admin could crash instead of showing the notice asking you to update.
    • Updated: 404 to 301 now requires WordPress 6.6 or higher.

  2. 404 to 301 4.0.4

    • New: MCP tab in Settings that connects an AI client (Claude, Gemini, Cursor, VS Code) to your site. The plugin registers 11 abilities with the WordPress Abilities API, so an assistant can read your 404 logs, create and repoint redirects, check where a URL lands and change settings from chat.
    • Improve: Redirect matching is faster on sites with a lot of rules. Only the rule that actually matches is loaded now, rather than every candidate, and pattern rules are cached instead of being re-queried for every 404.
    • Improve: The 404 logs list and the Recent 404s dashboard widget are much faster on large log tables. Both columns they sort on are now indexed.
    • Improve: Log trimming is on by default on new installs, keeping 30 days of 404s so the table cannot grow without limit. Existing sites keep whatever they already have.
    • Improve: New page header carrying the 404 to 301 logo, and the admin menu now uses the plugin’s own icon instead of a generic WordPress one.
    • Improve: The “Paths to ignore” setting accepts * as a wildcard, so one entry such as /20*/ covers every year of date-based archive URLs instead of needing one entry per year.
    • Fix: An entry in “Paths to ignore” typed with capital letters never matched anything, and an entry ending in a slash did not match a request that ended exactly there — /feed/ skipped /blog/feed/page/2 but not /blog/feed/. Entries are now matched the same way the request is, so an entry means what i…
    • Fix: On a server using MySQL’s default date handling, any future change to the plugin’s tables would have failed, because the tables were created with a zero-date default that MySQL re-validates whenever it rebuilds a table. The defaults are dropped on upgrade. Both timestamps have always been writ…

  3. 404 to 301 4.0.3

    • New: The Redirects Importer, Logs Exporter, Logs Cleaner and Email Reports add-ons are now built into the plugin and free. Nothing to install, nothing to enable, no licence key. If you have the separate add-on plugins, a notice lists the ones you can delete.
    • New: Recent 404s dashboard widget listing your busiest broken URLs from the last 30 days.
    • New: Open 404 count badge on the admin menu, so unresolved 404 errors are visible without opening the plugin.
    • New: Referrer source filter on the Logs page — separate 404s linked from your own site from those arriving off other sites or with no referrer at all.
    • New: Request type filter on the Logs page — split page and post requests from missing files and assets.
    • New: Site Health checks for logging state, log table size, cron schedules, conflicting redirect plugins and broken link monitoring.
    • New: Settings export and import as JSON, for reusing a configuration across sites.
    • New: “Track admin 404s” setting, so 404s inside wp-admin can be logged or ignored.
    • New: About Us page listing the free plugins from our team, installable in one click.
    • New: The 404 path in the logs is now a link, so you can open it in a new tab and check that your redirect fires.
    • Improve: Settings are reorganised into four tabs — Redirects, 404 Logs, Notifications and Import/Export — with every option filed under what it actually governs.
    • Improve: “Block WordPress URL guessing” is now a choice of three modes rather than a single switch: leave core’s guessing alone, block only its closest-post guesses, or block all of it.
    • Improve: Save Changes now sits above and below the settings cards instead of in a sticky bar.
    • Improve: Clearer setting names, descriptions and section titles throughout Settings.
    • Improve: Fields that depend on a disabled toggle are now hidden rather than shown greyed out.
    • Fix: Trashing a post could end in a fatal error. WordPress does not guarantee it passes a post object to the hook the slug monitor listens on, and a missing one is now skipped instead of stopping the request.
    • Fix: On sites using ALTERNATE_WP_CRON, every 404 was counted twice. WordPress reloads the same URL to run its cron, and that second arrival is no longer counted as another hit.
    • Fix: A redirect rule using regex captures could build a protocol-relative destination from the requested URL, sending the visitor off-site. Captures can no longer introduce a host.
    • Fix: Hardened unserialisation in the v3 migration against object injection.
    • Updated: Telegram Alerts is deprecated. It keeps working on sites that already have a live connection, but is hidden everywhere else and cannot be switched back on once disabled.
    • Updated: The 404_to_301_redirects_importer_sources filter is now 404_to_301_import_sources.
    • Updated: The bundled Portuguese (pt_PT) translation. Every string in it belonged to the version 3 admin, so it could no longer translate anything; translations now come from translate.wordpress.org.
    • Updated: The Add-ons page and per-add-on licence management are gone, along with the Freemius integration. With every feature bundled and free there is nothing left to license, and updates come from WordPress.org. The 404_to_301_freemius_plugin_id and 404_to_301_freemius_args filters were removed w…

  4. 404 to 301 4.0.2

    • Improve: Add-ons catalogue now pulls each free add-on’s icon and banner from the WordPress.org asset CDN and links to its WordPress.org plugin page.
    • Improve: Clearer Redirects Importer description in the add-ons catalogue.
    • Fix: Migration banner no longer shows on fresh installs running on SQLite (such as WordPress Playground).
    • Fix: Restored the spacing below the migration banner so it no longer touches the logs summary cards.

  5. 404 to 301 4.0.1

    • New: Summary card strip above the Logs and Redirects tables for an at-a-glance overview.
    • New: “Purge all logs” action in Settings → Tools → Danger Zone with a confirmation modal.
    • New: Custom redirect modal on the Logs page now also lets you edit an already-linked redirect.
    • Improve: Redesigned log “View details” modal with a cleaner table layout and prominent 404 path.
    • Improve: Log status is decoupled from custom redirect linkage — the redirect link is shown as a separate badge so the workflow status (open / ignored / fixed) stays meaningful.
    • Improve: Linking a custom redirect now sets the log to Fixed only when the redirect is active; toggling a redirect’s active state syncs every linked log automatically.
    • Improve: Deleting a custom redirect now unlinks any logs that referenced it.
    • Improve: Source field is locked when editing a redirect that is linked to a 404 log, so the link can’t be broken accidentally.
    • Fix: Stale per-row cache on logs after bulk status syncs.

  6. 404 to 301 4.0.0

    • New: Custom redirect manager with exact, prefix and regex matching and per-redirect redirect type.
    • New: Active/inactive toggle, hit counter and last-hit timestamp on every redirect.
    • New: Dedicated, indexed database tables for 404 logs and custom redirects.
    • New: Modern React-powered admin with full-featured Logs and Redirects tables (search, filters, bulk actions, pagination).
    • New: Per-log lifecycle status (open / ignored / fixed) and date filters.
    • New: Email notifications with a configurable hit threshold.
    • New: REST API at /404-to-301/v1/.
    • New: WP-CLI command set — wp 404-to-301 logs|redirects|settings.
    • New: Add-ons catalogue for free and premium extensions.
    • Improve: IP masking and path exclusions for GDPR-friendly logging.
    • For the full release history, see the changelog.

  7. 404 to 301 3.1.5

20251 release

  1. 404 to 301 3.1.4

20223 releases

  1. 404 to 301 3.1.3

  2. 404 to 301 3.1.2

  3. 404 to 301 3.1.1

20215 releases

  1. 404 to 301 3.1.0

  2. 404 to 301 3.0.9

  3. 404 to 301 3.0.8

  4. 404 to 301 3.0.7

  5. 404 to 301 3.0.6

20201 release

  1. 404 to 301 3.0.5

20193 releases

  1. 404 to 301 3.0.4

  2. 404 to 301 3.0.3

  3. 404 to 301 3.0.2

20183 releases

  1. 404 to 301 3.0.1

  2. 404 to 301 3.0.0.1

  3. 404 to 301 3.0.0

20171 release

  1. 404 to 301 2.3.3

201616 releases

  1. 404 to 301 2.3.1

  2. 404 to 301 2.3.0

  3. 404 to 301 2.2.9

  4. 404 to 301 2.2.8

  5. 404 to 301 2.2.7

  6. 404 to 301 2.2.6

  7. 404 to 301 2.2.5

  8. 404 to 301 2.2.4

  9. 404 to 301 2.2.3

  10. 404 to 301 2.2.2

  11. 404 to 301 2.2.1

  12. 404 to 301 2.2.0

  13. 404 to 301 2.1.7

  14. 404 to 301 2.1.6

  15. 404 to 301 2.1.5

  16. 404 to 301 2.1.4

201515 releases

  1. 404 to 301 2.1.3

  2. 404 to 301 2.1.2

  3. 404 to 301 2.1.1

  4. 404 to 301 2.1.0

  5. 404 to 301 2.0.9

  6. 404 to 301 2.0.8

  7. 404 to 301 2.0.7

  8. 404 to 301 2.0.6

  9. 404 to 301 2.0.5

  10. 404 to 301 2.0.4

  11. 404 to 301 2.0.2

  12. 404 to 301 2.0.1

  13. 404 to 301 2.0.0

  14. 404 to 301 1.0.8

  15. 404 to 301 1.0.7

20146 releases

  1. 404 to 301 1.0.6

  2. 404 to 301 1.0.5

  3. 404 to 301 1.0.4

  4. 404 to 301 1.0.3

  5. 404 to 301 1.0.1

  6. 404 to 301 1.0.0

Questions about 404 to 301’s releases

What is the latest version of 404 to 301?

4.0.5, released on Sep 30, 2026 (1 month ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is 404 to 301 updated?

7 releases in the last year, about one every 21 days. Its first release on WordPress.org dates from July 2014.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in 404 to 301’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.