404 to 301 – Redirect Manager, 404 Error Logs & Notifications vs Arreluna – Countdown Visibility Switcher

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/

Countdown Visibility Switcher lets you create reusable countdown timers from the WordPress admin and display them anywhere with a shortcode. The plugin is designed for landing pages, launches, limited-time offers, webinars, course campaigns, and evergreen funnels. It works with the WordPress block editor and most page builders because it does not force you to build the offer layout inside the plugin. Instead, each countdown can generate two simple CSS classes: A before class for content that should be visible before the countdown expires. An after class for content that should be visible after the countdown expires. For example, you can add the countdown shortcode to a landing page, add the generated before class to an offer button, and add the generated after class to an alternative button or message. If you do not want to switch content, you can configure the countdown to redirect visitors immediately when the timer expires. Features Create unlimited countdowns from the WordPress admin. Display each countdown with a shortcode. Evergreen countdowns based on the visitor’s browser localStorage. Fixed date and time countdowns based on the WordPress site timezone. Show or hide content with generated before/after CSS classes. Optional immediate redirect when a countdown expires. Basic redirect loop protection: if the current page is already the redirect URL, the plugin hides the expired countdown instead of redirecting again. Active/inactive status per countdown. Option to keep an expired countdown visible at zero or hide it. Per-countdown unit settings: days, hours, minutes, seconds. Per-countdown labels for each time unit. Global frontend style settings. Evergreen reset tool that restarts a countdown for everyone by incrementing the internal browser storage version. No external services and no visitor tracking. How it works Go to Countdowns > Add New. Choose Evergreen or Fixed date and time. Configure what happens when the countdown expires. Copy the generated shortcode. Add the shortcode to your page. If you choose show/hide mode, add the generated before/after classes to the content you want to control. If you choose redirect mode, enter the destination URL instead. Example shortcode: [acvs_countdown id="123"] Example classes in show/hide mode: acvs-before-123 shows content before the countdown expires. acvs-after-123 shows content after the countdown expires. Example HTML: This content is visible before expiration. This content is visible after expiration. In page builders such as Elementor, Divi, Kadence Blocks, or the WordPress block editor, you usually only need to add the class name to the block, section, row, column, or button. Countdown types Evergreen Evergreen countdowns start individually for each visitor. The expiration timestamp is stored in the visitor’s browser localStorage. This is useful for evergreen offers, automated funnels, or personal deadlines that start when someone first visits the page. Because this mode uses browser storage, a visitor can restart the timer by clearing browser data, using a different browser, using private/incognito mode, or changing device. Fixed date and time Fixed-date countdowns expire at the same date and time for everyone. The fixed deadline uses the WordPress site timezone. This is useful for launches, live campaigns, webinars, and real deadlines. Expiration actions Show/hide content Use this mode when you want to switch page content when the countdown expires. The plugin gives you two classes for each countdown: one for before expiration and one for after expiration. Redirect immediately Use this mode when you want visitors to be redirected as soon as the countdown expires. There is no delay. Avoid redirecting to a page that contains the same expired countdown with the same redirect URL. The plugin includes basic loop protection: if the current page is already the redirect URL, it will hide the expired countdown instead of redirecting again. Privacy Countdown Visibility Switcher does not collect personal data, does not use external services, and does not send visitor data to third parties. For evergreen countdowns, the plugin stores the expiration timestamp in the visitor’s browser localStorage. This data stays in the visitor’s browser and is used only to determine the countdown state.