404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring vs Custom Permalinks

404 to 301 is a redirect manager and 404 error monitor for WordPress. Create your own custom redirects with 301, 302 or 307 redirection, send every remaining 404 error to a page of your choosing, and keep a full log of the broken links visitors and search engines actually hit. Broken links cost you traffic. A visitor who lands on a 404 page usually leaves, and Google eventually drops the URL from its index along with whatever link equity it had earned. This redirect manager fixes both halves of that problem. You get precise redirection rules for the URLs you know about, and 404 error logs that surface the ones you don’t. Need more than redirects? 404 to 301 is free and every feature is included, with no license key and no upsell. If you also want full-site and .htaccess redirect rules, automatic 404 monitoring across large sites, Google Search Console crawl error data, and a complete SEO toolkit alongside your redirection, take a look at AIOSEO Pro. 🔀 Custom 301 Redirects and Redirection Rules Take control of your URLs from one redirect manager. Create as many custom redirects as you need and pick the redirect type per rule, so a permanent move uses a 301 redirect and a temporary campaign URL uses a 302 or 307 redirect. Match URLs by exact path when you know the address, by prefix when a whole folder has moved, or by regular expression when you need a pattern. Prefix matching covers the wildcard redirect cases, where every URL under /old-shop/ should land on its counterpart under /shop/. Regex redirect rules handle the messy ones, like a query string that changed format or a date-based permalink structure you have retired. Every redirect carries a hit counter and a last-hit timestamp, so you can see which rules are earning their keep and which are dead weight. Toggle a rule off without deleting it when you want to test, and manage the whole set from a table with search, filters, bulk actions and pagination. 🎯 Automatic 404 Redirection to Any Page You will never catch every broken URL by hand. Set a global fallback and 404 to 301 redirects every leftover 404 error automatically, to your homepage, a specific page, or any URL you like, using the redirect type you choose. That turns a dead end into a route back into your site. Visitors who would have bounced off a 404 page keep browsing, and search engines following an old inbound link reach real content instead of an error. 📋 404 Error Logs and Broken Link Monitoring The 404 error logs tell you which links are breaking and where the traffic is coming from. Each entry records the requested URL, the referrer, the IP address, the user agent and the timestamp, so you can tell a mistyped address apart from a broken inbound link that deserves a redirect. Busy broken URLs stay readable. Repeat hits are deduplicated into a single row with a hit count, so one popular dead link is one entry instead of thousands. Sort by hits and the URLs worth fixing rise to the top on their own. Two filters do most of the triage for you. Filter by referrer source to separate the 404 errors your own pages are linking to, which are yours to fix in the content, from the ones arriving off other sites, which want a redirect. Filter by request type to split real page and post requests from missing files and assets, so a hotlinked image or a stale script does not sit in the same queue as a lost article. Each 404 error carries a status of open, ignored or fixed, so the log works as a queue rather than a pile. Filter by date range, search by URL, then turn any logged 404 into a redirect in a couple of clicks. Privacy is covered too: IP addresses can be masked, and paths you do not care about can be excluded from logging entirely. 📊 404 Monitoring Without Opening the Plugin Most 404 error monitoring fails for a boring reason. Nobody remembers to go and look. So the numbers come to you instead. A Recent 404s widget on the WordPress dashboard lists your busiest broken URLs from the last 30 days, and the admin menu carries a count of the 404 errors still waiting on a decision, the same way WordPress flags pending updates. Summary cards above the log split the totals by status, so you can see what is still open against what you have already fixed or ignored. WordPress Site Health runs its own checks on your 404 monitoring setup and tells you when logging is switched off, when the log table has grown large enough to need pruning, or when another redirect plugin is installed alongside this one and the two could fight. 🔍 Protect Your SEO After a Site Migration A site migration is where redirects earn their reputation. Change a permalink structure, move to a new domain, or retire a batch of old posts, and every inbound link and every indexed URL points somewhere that no longer exists. Map the old URLs to the new ones with prefix or regex redirection and the link equity follows. For everything you miss, the 404 error logs act as a safety net: watch the log for a week after launch and you will see the URLs Google and your visitors are still asking for, then redirect them. Those are the same URLs that show up as crawl errors in Google Search Console, caught on your own site without waiting for the next crawl. The same routine works long after launch. Link rot is constant, external sites link to pages you later rename, and a redirect manager plus 404 monitoring is how you keep finding those before they cost you rankings. Catch broken links before your visitors do 404 to 301 handles the visitors who already hit a dead URL. To find the dead links still sitting in your content, install Broken Link Checker — it’s free, scans your posts, pages and comments for internal and external links that no longer resolve, and lets you fix or unlink them from one screen. 🔁 Automatic Redirects When a Permalink Changes Renaming a post is the most common way to break your own URLs. Switch on slug change monitoring and 404 to 301 writes the redirect for you: rename a post or page, and the old permalink starts pointing at the new one before anyone hits a 404. You also get control over the guessing WordPress does on its own. Core quietly tries to match an unknown URL to a similar post before this plugin ever sees the request, which hides real 404 errors from your logs and can send a visitor to the wrong article. Leave that behavior alone, block just the closest-post guesses, or block guessing altogether so every miss is logged and redirected by your rules instead. 📧 404 Email Alerts and Scheduled Reports Nobody wants to live in the dashboard. Set a hit threshold and 404 to 301 sends an email alert when a broken link starts getting real traffic, so a busy site does not flood your inbox over a single stray request. Switch on Email Reports and you also get a daily, weekly or monthly digest of your 404 activity with the log attached as a CSV. It is a five-second read that tells you whether anything needs attention. 📥 Import Redirects in Bulk, Export Your 404 Logs Moving in from another redirect plugin does not mean retyping your rules. The redirects importer does a bulk redirect import from a CSV file, previews what it found and flags duplicates before anything is written, so you can see the damage before you commit to it. Exports work the other way. Download the 404 error log as a CSV whenever you want it, filtered exactly the way the Logs page is showing, so a report you built with the referrer and date filters is the report you get. Your settings travel too: export them as JSON on one site and import them on the next, which turns a redirect and logging configuration you like into something you can roll out across every site you run. Log cleanup keeps the table honest. Prune by age, by row count, or on a schedule, so a high-traffic site does not grow an unbounded 404 log, with a purge action for when you want to start over. 🧰 Redirect Manager Use Cases Site migration redirects – Map old URLs to new ones after a redesign, domain change or permalink update. Ecommerce URL changes – Redirect discontinued products and retired category pages to live alternatives. Blog cleanup – Point merged or deleted posts at the article that replaced them. Broken inbound links – Recover traffic from external sites linking to URLs that have moved. Campaign URLs – Use short, memorable paths with a 302 or 307 redirect to a landing page. Fixing 404 errors at scale – Work through the 404 error logs by hit count and redirect what matters. Missing images and files – Spot hotlinked assets and dead downloads with the request type filter. ⚡ Built for Performance and Developers The plugin does its work only on a 404 request. Healthy page loads are never touched, so a redirect manager that sits on a busy site costs nothing on the pages that are working. Custom redirects resolve through a hashed, indexed lookup. Developers get a REST API at /404-to-301/v1/ covering every admin operation, a full WP-CLI command set (wp 404-to-301 logs|redirects|settings), and a filterable action pipeline for hooking in custom logic. It is multisite compatible, and each site in the network keeps its own redirects and 404 error logs. Full 404 to 301 Feature List Everything the free redirect manager includes. For the wider SEO toolkit, see All in One SEO. Custom redirect manager with unlimited redirects 301 redirect (permanent) support 302 redirect (found) support 307 redirect (temporary) support 410 Gone and 451 status responses Exact URL matching Prefix matching for folders, URL sections and wildcard redirect patterns Regex redirect rules for pattern-based redirection Query string handling per rule (ignore or require) Enable or disable any redirect without deleting it Hit counter on every redirect rule Last-hit timestamp on every redirect rule Automatic 404 redirection with a global fallback Redirect all 404 errors to the homepage Redirect all 404 errors to a chosen page or URL Full 404 error logs with requested URL and referrer IP address and user agent logging Deduplicated 404 logs with hit counts 404 error status workflow (open, ignored, fixed) Referrer source filter (linked from your site, from elsewhere, or no referrer) Request type filter (pages and posts, or files and assets) Date-range filtering and URL search on logs One-click redirect creation from a logged 404 Bulk actions on redirects and 404 logs Recent 404s dashboard widget for at-a-glance 404 monitoring Open 404 count badge on the admin menu Summary cards for today, this week and all-time 404 totals Broken link monitoring across the whole site 404 email alerts with a configurable hit threshold Scheduled email reports (daily, weekly, monthly) with CSV attached Bulk redirect import from CSV, with a preview and duplicate detection Migration from other redirect plugins Logs exporter with filter-aware CSV download Settings export and import as JSON for reuse across sites Log cleanup by age, row count or schedule, plus a purge action Pruning that keeps the 404s you have already linked to a redirect IP address masking for GDPR Path exclusions to keep noise out of the logs Skip search engine bot 404s so crawlers don’t fill the log Admin-area 404 tracking, on or off Control over WordPress URL guessing, from untouched to fully blocked Slug change monitoring with automatic redirect creation REST API for every admin operation WP-CLI commands for logs, redirects and settings Multisite compatible, per-site redirects and logs Site Health checks covering logging, log size, cron jobs and plugin conflicts 🏆 Built by the All in One SEO Team 404 to 301 has been running on WordPress sites since 2014 and is active on more than 100,000 of them. It is maintained by the team behind All in One SEO, Broken Link Checker and more, used on over 3 million sites. A Redirection Alternative Without the Bloat If you have been comparing redirect plugins you have probably looked at Redirection, 301 Redirects, Safe Redirect Manager and the redirect modules inside Yoast SEO Premium and Rank Math. They are capable tools and some of them are very widely used. The difference here is scope. 404 to 301 does redirect management and 404 error logging, and it does not ask you to install an SEO suite to get them or pay for a license to unlock the importer. Every feature listed above is free, the log table keeps itself trimmed, and the plugin stays out of the request path on pages that are not 404ing. Branding Guidelines 404 to 301 is a product of All in One SEO. When writing about the plugin, please use the correct branding: 404 to 301 (correct) 404to301 (incorrect) 404 To 301 (incorrect) Redirect Manager 404 (incorrect)

You want to take control of your WordPress site’s URLs? The Custom Permalinks plugin gives you the power to set unique, custom URLs for any post, page, tag, or category. This means you can design your site’s structure exactly how you envision it, rather than being limited by WordPress’s default settings. When you set a custom permalink, the original post URL will be automatically redirected to your new, customized URL. Key Features Individual Permalink Control: Assign unique URLs to any post, page, tag, or category. Site Structure Control: Gain ultimate control over how your site’s URLs are organized. Post Type Permalink Structures (v3.0.0+): Define custom permalink structures for each public Post Type using predefined tags, automatically generating URLs upon content creation. You can still manually edit any permalink. If left empty, default settings will apply. Automatic Redirects: Old URLs keep working — visitors and search engines are redirected to the new custom permalink automatically. Getting Started: Plugin Settings You can configure Custom Permalinks by navigating to Settings > Custom Permalinks in your WordPress Dashboard. To set a permalink for an individual post, page, category, or tag, edit that item and look for the Custom Permalink field near the top (or in the sidebar) of the editor screen — enter the URL path you want and save. Available Tags for Permalink Structures When setting up your custom permalink structures, you can use a variety of tags that will dynamically populate the URL. Here’s a breakdown of what’s available: %year%: The year of the post in four digits, eg: 2025 %monthnum%: Month the post was published, in two digits, eg: 01 %day%: Day the post was published in two digits, eg: 02 %hour%: Hour of the day, the post was published, eg: 15 %minute%: Minute of the hour, the post was published, eg: 43 %second%: Second of the minute, the post was published, eg: 33 %post_id%: The unique ID of the post, eg: 123 %category%: A clean version of the category name (its slug). Nested sub-categories will appear as nested directories in the URL.. %author%: A sanitized version of the post author’s name. %postname%: A clean version of the post or page title (its slug). For example, “This Is A Great Post!” becomes this-is-a-great-post in the URL. %parent_postname%: Similar to %postname%, but uses the immediate parent page’s slug if a parent is selected. %parents_postnames%: Similar to %postname%, but includes all parent page slugs if parents are selected. %title%: The title of the post, converted to a slug. For example, “This Is A Great Post!” becomes this-is-a-great-post. Unlike %postname% which is set once, %title% automatically updates in the permalink if the post title changes (unless the post is published or the permalink is manually edited). %ctax_TAXONOMY_NAME%: A clean version of a custom taxonomy’s name. Replace TAXONOMY_NAME with the actual taxonomy name. You can also provide a default slug for when no category/taxonomy is selected by using ?? (e.g., %ctax_type??sales% will use “sales” as a default). %ctax_TAXONOMY_NAME_name%: The custom taxonomy term’s name (instead of its slug). Replace TAXONOMY_NAME with the actual taxonomy name. Supports a default value using ?? when no term is selected (e.g., %ctax_type_name??Sales%). %ctax_parent_TAXONOMY_NAME%: Similar to %ctax_TAXONOMY_NAME%, but includes the immediate parent category/tag slug in the URL if a parent is selected. %ctax_parent_TAXONOMY_NAME_name%: Similar to %ctax_TAXONOMY_NAME_name%, but includes the immediate parent term’s name if a parent is selected. %ctax_parents_TAXONOMY_NAME%: Similar to %ctax_TAXONOMY_NAME%, but includes all parent category/tag slugs in the URL if parents are selected. %ctax_parents_TAXONOMY_NAME_name%: Similar to %ctax_TAXONOMY_NAME_name%, but includes all parent term names if parents are selected. %custom_permalinks_TAG_NAME%: Developers have the flexibility to define their own custom tags(replace _TAG_NAME with your desired name). To ensure these tags resolve to the correct permalinks, simply apply the custom_permalinks_post_permalink_tag filter. Important Note: For new posts, Custom Permalinks will keep updating the permalink while the post is in draft mode, assuming a structure is defined in the plugin settings. Once the post is published or its permalink is manually updated, the plugin will stop automatic updates for that specific post. Custom Permalinks: Fine-Tuning with Filters Custom Permalinks offers a range of filters that empower developers to precisely control its behavior. You can explore all available filters, complete with example code snippets, in our GitHub repository. For Assistance: Premium Users: If you need assistance implementing these filters, please don’t hesitate to reach out to us via our Premium contact support. Other Users: You can also directly reach out to the plugin author via LinkedIn. Need Help or Found a Bug? Support: For one-on-one email support, consider purchasing Custom Permalinks Premium. While some basic support may be provided on the WordPress.org forums, email support is prioritized for premium users. Bug Reports: If you encounter a bug, please report it on GitHub. Make sure to provide complete information to reproduce the issue. GitHub is for bug reports, not general support questions. If you experience any site-breaking issues after upgrading, please report them on the WordPress Forum or GitHub with detailed information. You can always revert to an older version by downloading it from https://wordpress.org/plugins/custom-permalinks/advanced/.