Description
Web Makinası – 404 Manager helps site administrators find missing URLs and create deliberate redirect rules without installing a large SEO suite.
The plugin stores one aggregated record per missing path instead of creating a separate row for every visit. It does not store IP addresses, user accounts, or full browser user-agent strings.
Main features
- Aggregated 404 records with first-seen, last-seen, and hit counts.
- Open, resolved, and ignored record states.
- Manual 301 permanent redirects.
- Manual 302 temporary redirects.
- 410 Gone responses for permanently removed content.
- Search and select published WordPress content as a target.
- Use a custom internal URL or, when enabled, an external URL.
- Redirect hit counts and last-hit dates.
- Separate switches for 404 logging and redirect processing.
- Configurable 30, 90, 180-day, or unlimited retention.
- Configurable protection against unbounded unique 404 records.
- No automatic homepage redirects.
- No telemetry, advertising, or paid-version notices.
What the plugin does not do
The first version does not include regular expressions, wildcard redirects, CSV import/export, domain migration profiles, Search Console integration, server configuration changes, or automatic target suggestions.
Privacy
The plugin may store the requested path, request count, first and last occurrence dates, and a cleaned referrer. Internal referrers are stored as paths. External referrers are stored as domain names. Query parameters are removed.
The plugin does not store IP addresses, user accounts, visitor identities, or full user-agent strings.
Support policy
Individual installation, configuration, and site-specific technical support is not provided for this free plugin. Reproducible product bugs are reviewed and verified bugs are fixed. Reasonable feature suggestions may be evaluated according to product scope and maintenance cost.
Installation
- Upload the plugin folder to
/wp-content/plugins/or install the ZIP file from the WordPress Plugins screen. - Activate Web Makinası – 404 Manager.
- Open Web Makinası > 404 Manager.
- Visit a missing URL to verify that 404 logging is working.
- Create redirect rules from the 404 Records tab or the Redirects tab.
FAQ
-
Does the plugin redirect every 404 page to the home page?
-
No. Each redirect must have a deliberate source and target. Redirecting every missing URL to the home page can hide broken links and create poor visitor and search-engine behaviour.
-
What is the difference between 301 and 302?
-
301 indicates a permanent move and may be cached by browsers. 302 indicates a temporary redirect. Use 302 when the change is not permanent.
-
When should I use 410?
-
Use 410 when content has been permanently removed and there is no suitable replacement URL. A 410 rule does not redirect the visitor.
-
Does the plugin store visitor IP addresses?
-
No. It stores aggregated path-level records and does not store IP addresses or user accounts.
-
Can I redirect to another domain?
-
External redirects are disabled by default. Administrators can enable them in the plugin settings. Only HTTP and HTTPS URLs are accepted.
-
Why does a new redirect not work immediately?
-
A page cache, server cache, or CDN may be serving an older response before the request reaches WordPress. Clear the relevant cache and test again.
-
Does it support multisite?
-
The plugin can be used on individual sites within a multisite installation. Central network-wide rule management is not included in version 1.0.4.
-
Are translations bundled in the plugin ZIP?
-
No. WordPress.org translations are delivered through the standard WordPress language-pack system.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Web Makinası – 404 Manager” is open source software. The following people have contributed to this plugin.
Contributors
“Web Makinası – 404 Manager” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “Web Makinası – 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
1.0.4
- Updated the plugin namespace and JavaScript localization object to use a more distinct plugin-specific prefix.
- Removed a redundant hard-coded admin-ajax.php path from protected path matching; AJAX requests continue to use WordPress-generated admin_url() values.
- Restored the valid public Plugin URI.
1.0.3
- Hardened request handling with field-level sanitization before validation or transient storage.
- Added explicit permission checks to bulk actions and retained nonce checks for all privileged requests.
- Strengthened plugin-specific prefixes for WordPress-facing actions, nonces, transient keys, and list-table identifiers.
- Improved review-readiness for plugin metadata and request handling.
1.0.2
- Fixed remaining Plugin Check placeholder-count and dynamic SQL inspection warnings.
- Scoped uninstall schema-change exceptions to the explicit user-requested data removal path.
1.0.1
- Fixed Plugin Check SQL preparation, nonce, translation-comment, and naming warnings.
- Sanitized request URI handling.
- Improved custom-table query safety and documented intentional direct database access.
1.0.0
- Initial release.
- Added aggregated 404 logging.
- Added manual 301, 302, and 410 rules.
- Added WordPress content target search.
- Added redirect statistics, retention controls, record limits, and privacy text.