Take full control of your WordPress 404 experience. Custom 404 Pro lets you redirect 404 errors to any page on your site or an external URL, log every broken URL your visitors hit, and stay notified — without getting buried in email.

• Redirect to a WordPress page — choose any published page from a dropdown; it just works.
• Redirect to a custom URL — point 404s at any external destination.
• Configurable HTTP status code — choose 301, 302, 307, or 308 depending on whether the redirect is permanent or temporary.
• Disable redirects entirely — keep logging active without touching the 404 response.

• Automatic log capture — every 404 is recorded with the full request path, referring URL, user agent, and timestamp.
• IP address logging — optionally capture the visitor's IP. Disable it with one checkbox if privacy or GDPR is a concern; logged entries show N/A instead.
• Searchable, sortable log table — filter by any column directly from the Logs admin page.
• Bulk actions — delete selected logs, delete all logs, or export everything as a CSV file in one click.

• Admin email alerts — get notified at your site's admin email address whenever a 404 is logged.
• Email cooldown — configure a quiet period between notifications (15 minutes, 30 minutes, 1 hour, 6 hours, or 24 hours). Once an email is sent, the plugin stays quiet until the cooldown expires — no inbox flooding from bot crawls or broken redirect loops.

• Multisite — tables and settings are provisioned per-site on activation and cleaned up per-site on uninstall.
• Polylang & WPML — redirect targets resolve to the correct translated page for the visitor's active language automatically.
• Clean uninstall — all database tables are dropped when the plugin is removed. No orphaned data left behind.

1. Download the plugin ZIP from WordPress.org or clone this repository.
2. Copy the custom-404-pro folder to wp-content/plugins/.
3. Activate the plugin from the Plugins screen in the WordPress admin.
4. Navigate to Custom 404 Pro → Settings to configure your redirect and notification preferences.

Important: If you ever want to remove the plugin, use Deactivate → Delete from the Plugins screen. Do not delete the plugin folder directly — that bypasses the uninstall routine and leaves database tables behind.

	Activate the plugin from the WordPress admin
	Sortable, searchable log table with bulk actions
	Redirect and notification settings

Why is the 404 redirect not working?

Some themes (notably Divi) intercept the request before the template_redirect hook fires. Try switching to a default theme to confirm the plugin is working, then re-enable your theme and check for conflicts with theme-level 404 handling.

Why are my settings not saving after reinstallation?

Always use Deactivate → Delete from the Plugins screen — never remove the plugin folder manually. Manual removal skips the uninstall routine, leaving old database tables in place. When the plugin is reinstalled, it detects the existing tables and skips seeding defaults, so you end up with stale data.

Can I disable email notifications without disabling logging?

Yes. Uncheck Email in General settings. Logging continues independently.

How does the email cooldown work?

After an email notification is sent, a transient is set in the WordPress object cache for the duration of the configured cooldown period. Any 404 that fires during that window skips the email send entirely. The next email goes out after the cooldown expires.

Is this plugin GDPR-friendly?

You can disable IP logging with the Log IP checkbox under General settings. When disabled, the IP column in all log entries records N/A. No IP data is stored or emailed.

Open an issue on GitHub. The WordPress.org support forum is not monitored.

If the plugin is useful to you, a rating on WordPress.org or a GitHub star goes a long way.

Like the plugin? Buy me a coffee via PayPal.

See WordPress.org changelog for the full history.

• Add email notification cooldown to prevent inbox flooding. Configurable from 15 minutes to 24 hours (default: 1 hour).

• Fix IP logging toggle not persisting correctly due to positional row access.

• Fix WPML/Polylang settings overwriting each other when using per-language domains.

• Add load_plugin_textdomain support for translations.

• Add Polylang and WPML support for the 404 redirect page.

• Enforce full WordPress coding standards: PHPDoc comments, input sanitization, file naming convention.

• Improve codebase to meet WordPress coding standards.

• Fix PHP 8.2+ dynamic property deprecation warnings.

• Security: Remediate SQL injection and CSRF vulnerabilities (CVE-2025-9947).
• Update tested up to WordPress 6.9.4.

• Support WordPress 6.6.

• Add Multisite support.

• Export logs as CSV.
• Validate URL format when URL redirect mode is selected.

• IP logging is now optional.

• Complete rewrite with a new logging mechanism and improved architecture.

GPLv2 or later