Erriflow 404 Manager

Description

Erriflow 404 Manager keeps your WordPress 404 journal useful instead of filling it with automated scanner garbage.

The plugin records meaningful missing URLs, suppresses obvious security probes before they enter the journal, and gives administrators a practical workflow for deciding whether a URL needs a 301 redirect, a 410 response, or no action at all.

Free features include:

  • Live 404 monitoring with hit counts and timestamps.
  • Smart bot/security probe suppression before the main journal.
  • Individual 301 and 410 redirect management.
  • Ignore and reopen workflow for URLs that do not require action.
  • Exact redirect rules with a WordPress runtime fallback.
  • Apache/LiteSpeed .htaccess synchronization when the file is writable.
  • Search, source filters, retention controls, and environment diagnostics.
  • Internationalized interface, ready for WordPress.org community translations.

Erriflow 404 Manager Pro also includes:

  • Internal broken-link scanner for posts, pages, Bricks content, media references, and WordPress menus.
  • Bulk 301, 410, ignore, reopen, and journal cleanup actions.
  • Google Search Console CSV import, generic CSV import, and CSV export.
  • Suggested redirect targets based on existing site content.
  • Redirect-chain and loop diagnostics.
  • .htaccess backup and restore tools.

The Pro edition is distributed separately from the WordPress.org package. Pro implementation code is not included in the WordPress.org Free package; the Free plugin only shows which additional features are available in the separately distributed Pro edition.

Erriflow 404 Manager does not automatically redirect every 404 to the homepage. Redirects should be relevant to the missing URL; unrelated or intentionally removed URLs can remain 404 or use 410.

Privacy and local data

Erriflow 404 Manager stores its 404 journal locally in your WordPress database. Depending on the request, stored fields can include the requested URL/path, first and last seen timestamps, hit count, referrer, user agent, source/classification, redirect target, and internal source references discovered by the scanner.

By default, unresolved and ignored journal entries are retained for 180 days. The retention period is configurable, and administrators can choose whether plugin data is deleted when the plugin is fully uninstalled. Obvious bot/security probes suppressed before logging are represented only by aggregate counters.

The plugin also adds suggested text to WordPress’ Privacy Policy Guide so site administrators can document this behavior.

External services

Erriflow 404 Manager bundles the Freemius WordPress SDK. Freemius is used for optional Pro checkout, licensing, account management, premium downloads/updates, billing/support account features, and deactivation feedback when submitted.

The Free edition does not require a Freemius account. When an administrator intentionally uses Freemius-powered features, information required for those services may be sent to Freemius, such as the site URL/title, WordPress/PHP/plugin versions, administrator/account details, license status, and billing information supplied during checkout.

Freemius terms: https://freemius.com/terms/
Freemius privacy policy: https://freemius.com/privacy/

Screenshots

Installation

  1. Install Erriflow 404 Manager from the WordPress Plugins screen or upload the plugin ZIP.
  2. Activate the plugin.
  3. Open Erriflow 404 Manager in the WordPress admin menu.
  4. Review the default noise filtering and retention settings.
  5. Let the journal collect real 404 requests, then create redirects only where a relevant replacement exists.

For Pro, install the Premium package provided after purchase and activate your license. The Premium edition contains all Free features, so the deactivated Free plugin can then be removed safely.

FAQ

Does it redirect every 404 to the homepage?

No. That usually creates irrelevant soft-redirect behavior. Erriflow 404 Manager encourages relevant replacements only. Unrelated missing URLs can remain 404, be ignored in the journal, or return 410 when appropriate.

Does it work on Nginx?

Yes. Managed redirects can run through WordPress on any supported server. On Apache and LiteSpeed, Erriflow 404 Manager can additionally synchronize exact rules to .htaccess when the file is writable.

Does it store bot/security scans?

Obvious technical probes are suppressed before they enter the main journal. The plugin keeps aggregate counters so administrators can see how much noise was filtered without filling the journal with probe URLs.

What data does the 404 journal store?

The journal can store the requested URL/path, timestamps, hit count, referrer, user agent, source/classification, redirect target, and internal source references. Data stays in the site’s WordPress database unless an administrator intentionally uses a documented external service such as Freemius for Pro licensing or checkout.

Does the Free edition require an account?

No. The Free edition opens directly into the plugin and does not require a Freemius account. Freemius-powered checkout, licensing, billing/account, or feedback features are used only when an administrator intentionally opens or submits them.

Is Google Search Console connected through an API?

No. The current Pro workflow imports CSV files exported from Search Console. It does not request access to a Google account.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Erriflow 404 Manager” is open source software. The following people have contributed to this plugin.

Contributors

“Erriflow 404 Manager” has been translated into 1 locale. Thank you to the translators for their contributions.

Translate “Erriflow 404 Manager” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

2.0.6

  • Renamed the plugin to Erriflow 404 Manager with the new erriflow-404-manager slug and text domain.
  • Moved all Pro-only local implementations out of the WordPress.org Free package.
  • Kept Free 301/410 management fully functional without license checks.
  • Updated Freemius integration settings for the new Free and Premium slugs.
  • Removed bundled translation binaries from the WordPress.org package; translations are handled through WordPress.org.

2.0.5

  • Fixed the final WordPress.org Plugin Check internationalization error for the Freemius privacy-policy placeholder.

2.0.4

  • WordPress.org compatibility and security hardening.

2.0.3

  • Fixed Free/Premium package detection so the generated Free build can never initialize as Premium.
  • Hardened internal HTTP checks and redirect diagnostics against unsafe remote requests.
  • Kept query-string-specific redirects in the WordPress runtime layer instead of writing over-broad .htaccess rules.
  • Moved .htaccess backup snapshots out of the public web directory and into non-autoloaded WordPress storage.
  • Fixed release metadata and Ukrainian translation coverage.

2.0.2

  • Fixed the in-dashboard Pro checkout route while keeping the Freemius pricing menu hidden.
  • Preserved Freemius’ native hidden checkout handler for the custom Buy button.

2.0.1

  • Routed all upgrade links through the native Erriflow 404 Manager Pro screen and suppressed the duplicate Freemius Upgrade submenu.
  • Kept the actual Buy button connected to the Freemius checkout flow.

2.0.0

  • First public release of Erriflow 404 Manager by Ivan Nosenko.
  • Added live 404 monitoring with smart bot/security noise suppression.
  • Added individual 301/410 management, ignore/reopen workflow, filters, retention, and diagnostics.
  • Added Apache/LiteSpeed .htaccess synchronization with WordPress runtime fallback.
  • Added responsive WordPress admin UI and Ukrainian localization.
  • Added Freemius-based Free/Pro packaging, checkout, licensing, and Premium delivery.
  • Pro: added internal broken-link scanning, bulk actions, Search Console/CSV tools, redirect recommendations, chain diagnostics, and .htaccess backup/restore.
  • Added privacy-policy guidance and additional input/remote-request hardening for the public release.