404 to 301 – Redirect Manager, 404 Error Logs & Notifications vs Redirect multisite user to their own site (UNMAINTAINED)

404 to 301 is a complete redirect manager and 404 error monitor for WordPress. Build your own custom redirects (301, 302, 307 and more) with exact, prefix or regex matching, automatically redirect every remaining 404 error to any page you choose, and keep a full log of every broken link that hits your site — so you can fix the real problem instead of just hiding it. An optional email alert lets you know the moment a URL starts getting hit. Whether you are managing redirects after a site migration, cleaning up old URLs following a redesign, or simply protecting your SEO and visitor experience from dead links, 404 to 301 gives you precise redirect management and a 404 logging safety net for everything you miss — all from a fast, modern admin. Custom redirects Take full control of your URLs with a built-in redirect manager: Create unlimited custom redirects with your choice of redirect type (301, 302, 307 and more). Match URLs by exact path, prefix or regular expression (regex) for precise or pattern-based rules. Enable or disable individual redirects without deleting them. See a hit counter and last-hit timestamp on every redirect so you know what’s actually being used. Manage everything from a full-featured table with search, filters, bulk actions and pagination. Automatic 404 redirection Don’t have a custom rule for a broken URL? Set a global fallback and automatically redirect every leftover 404 error to your homepage, a custom page, or any URL — with the redirect type of your choice. No more dead-end 404 pages costing you visitors and link equity. 404 error logs Know exactly which links are breaking on your site: Log every 404 error with the requested URL, referrer, IP address, user agent and timestamp. Duplicate hits are deduplicated and counted, so a busy broken URL is one row with a hit count — not thousands. Track each error through a lifecycle status (open / ignored / fixed) and filter logs by date. Turn any logged 404 into a redirect in a couple of clicks. GDPR-friendly: IP addresses can be masked, and you can exclude paths you don’t care about from logging. Email notifications Get an email alert when broken links appear, with a configurable hit threshold so busy sites don’t flood your inbox. Stay on top of new 404s without living in the dashboard. Built for performance and developers The plugin does work only on a 404 request — healthy page loads are never touched. Custom redirects are matched by a hashed, indexed lookup for near-instant resolution. REST API at /404-to-301/v1/ for every admin operation. Full WP-CLI command set: wp 404-to-301 logs|redirects|settings. A filterable action pipeline so developers can hook in their own logic. Multisite compatible — each site keeps its own redirects and logs. Add-ons Extend 404 to 301 with official add-ons. Browse the full catalogue at https://duckdev.com/addons/404-to-301/, or open the Add-ons tab inside the plugin. Free add-ons Redirects Importer — Bulk import custom redirects into 404 to 301 from CSV files, or migrate them in from other redirect plugins like Redirection by John Godley and 301 Redirects – Redirect Manager by WebFactory — no manual re-entry. Logs Exporter — Export the 404 error log table as a downloadable CSV file directly from the Logs page. Premium add-ons Logs Cleaner — Auto-prune the 404 log table by age, by row count, or on a periodic schedule to keep your database lean. Email Reports — Periodic email reports — daily, weekly or monthly digests of your 404 activity, each with an attached CSV. Telegram Alerts — Real-time Telegram alerts for 404 errors and redirects, delivered in the background so visitors never wait on the API call. Documentation & Support Documentation: https://docs.duckdev.com/404-to-301/ Support forum: https://wordpress.org/support/plugin/404-to-301/ Add-ons: https://duckdev.com/addons/404-to-301/

THIS PLUGIN IS NO LONGER MAINTAINED. If the current user in a multisite environment accesses a subsite to which access has not been granted, then redirect the user back to their own site. If the user has been granted access to more than one site in the Multisite installation, then no redirect can occur. (Because there is no way of finding out which one is “correct”.) Information for developers There are three action hooks available to developers. You can use them, for example, to write a log file or notify an email address when an action is carried out. redirect-multisite-user-to-their-own-site/no-sites fires when the user is logged in but does not have specific access to any sites in the current Multisite installation. Receives the values $current_user (WordPress User object) and $current_site_id (integer) as attributes. redirect-multisite-user-to-their-own-site/redirecting fires immediately before the user is redirected to the appropriate site. Receives the values $current_user (WordPress User object), $current_site_id (integer) and $user_target_site->siteurl (the URL to which the user will be redirected) as attributes. redirect-multisite-user-to-their-own-site/not-allowed fires when the user has authorized access to more than one site in the installation, and can therefore not be redirected. Receives the values $current_user (WordPress User object), $current_site_id (integer) and $user_sites (array) as attributes. This plugin requires PHP 5.3 or newer because it uses PHP namespaces.