301 Redirects – Redirect Manager vs Simple URLs Legacy

301 Redirects helps you manage and create 301, 302, 307 redirects for WordPress site to improve SEO & visitor experience. 301 Redirects is easy to use. Perfect for new sites or repairing links after reorganizing your old content, or when your site has content that expires and you wish to avoid sending visitors to a 404 error page and want to create redirection instead. Use the 404 error log to identify problematic links & create new redirections. Having problems with spam, bots, or AI scrapers? Have a look at our free Captcha plugin used on over 200,000 sites. 301 Redirects GUI is located in WP Admin – Settings – 301 Redirects 404 Error Log widget can be found in the WP Admin – Dashboard – 404 Error Log Features Choose from Pages, Posts, Custom Post types, Archives, and Term Archives from dropdown menu to create redirection Or, set a custom destination URL! Retain query strings across redirects Super-fast redirection 404 error log 404 error log widget Import/Export feature for bulk redirects management Simple redirect stats so you know how much a redirection is used Fully compatible with translation plugins (Weglot, TranslatePress, Gtranslate, Loco Translate) that use lang prefix in URL Need more features? WP 301 Redirects PRO offers wildcard & regular expression URL matching, auto-typo fixing in URLs, complete redirect and 404 log, link scanner, and a centralized SaaS dashboard to monitor redirects on all your sites from one place. What is a 301 Redirect? A redirect is a simple way to re-route traffic coming to a Requested URL to different Destination URL. A 301 redirect indicates that the page requested has been permanently moved to the Destination URL, and helps pass on the Requested URLs traffic in a search engine friendly manner. Creating a 301 redirect tells search engines that the Requested URL has moved permanently, and that the content can now be found on the Destination URL. An important feature is that search engines will pass along any clout the Requested URL used to have to the Destination URL. When Should I use 301 Redirects? * Replacing an old site design with a new site design * Overhauling or re-organizing your existing WordPress content * You have content that expires (or is otherwise no longer available) and you wish to redirect users elsewhere Is the 404 error log GDPR friendly? The 404 error log does not collect user IPs. It collects the following data: timestamp of the event, the (404) URL that was opened, and the user-agent string. Having problems with SSL? Moving a site from HTTP to HTTPS? Install our free WP Force SSL plugin. It’s a great way to enable SSL and fix SSL problems. External libraries used in the project * PHP User Agent Parser

Simple URLs Legacy is a fork of the plugin by Nathan Rice. A URL management system to create, manage, and track outbound links from your site. Usage Simple URLs Legacy adds a new custom post type to your admin menu, where you can create, edit, delete, and manage URLs. It stores click counts in the form of a custom field on that custom post type, so it scales really well. And, by avoiding page based redirects, which is the current trend in masking affiliate links, we avoid any issues with permalink conflicts, and therefore avoid any performance issues. Upload the entire simple-urls-legacy folder to the /wp-content/plugins/ directory DO NOT change the name of the simple-urls-legacy folder Activate the plugin through the ‘Plugins’ menu in WordPress Navigate to Settings > Permalinks. That’s it. Just open that screen and WordPRess automatically flushes redirects. Trust me. Navigate to the Simple URLs Legacy menu Create a new URL, or manage existing URLs. Publish and use the URLs however you want! = 1.0.4 = * 05/27/2025 * Add capability to reset click counter on any simple url. * ‘Reset Clicks’ to 0 from link edit screen or using Quick Edit hover navigation. * 1.0.3 12/16/2024 Updated Tested To vesion for WP 6.7.1 Applied wp_unslash correctly to url sanitization. Corrected text domain setting in admin class. Aligned license declaration between readme and plugin header. Added license comment block. Addressed issues with lengthy short description in header. Added original contributors back into readme header. Adjust loading of constants and get_plugion_data to accomodate WP 6.7 changes in text_domain loading. 1.0.2 11/13/2023 Updated Tested To version for WP 6.4.1 Added logic to pull plugin version from main file header 1.0.1 03/31/2023 #5FTF #WebDevStudios Updated Tested To vesion for WP 6.2 Clean up documentation 1.0.0 12/30/22 #5FTF #WebDevStudios Initial release of Simple Urls Legacy 0.10.3 11/25/2022 #5FTF #WebDevStudios Add Published date to Simple URLs Legacy admin page 0.10.2 11/25/2022 #5FTF #WebDevStudios Applied WordPress coding standards Tweaked plugin description. Added required license declarations in readme.txt 0.10.1 10/28/2022 #5FTF #WebDevStudios Added conflict notice in admin if Simple URLs plugin is running. Reworked constants for better readability. Added build/dependency source files back in with updated dependencies. 0.10.0 08/09/2022 Reverted plugin to last known state under original author – Nathan Rice (v0.9.9). Renamed plugin from Simple URLs to Simple URLs Legacy. URL structure modifier filter changed from ‘simple_urls_slug’ to ‘simple_urls_legacy_slug’. Reworked naming conventions to use simple-urls-legacy namespace and package name. Removed build/dependency source files. 0.9.9 Fixed URLs not properly redirecting. 0.9.8 Coding standards. Added composer. Added Circle CI integration. Added new filter to change the slug. Added REST support to ensure Simple URLs appear in list when linking text. Added cast string to int to avoid type error. 0.9.7 WordPress compatibility. 0.9.6 Add plugin header i18n Add textdomain loader 0.9.5 Changed messages and labels. Updated textdomain. Generated POT file. 0.9.4 Fixed saving bug 0.9.3 Removed capability line from the register function. Users with permission to edit posts can create/edit URLs. Bumped to show compatibility with WordPress 3.0.4 0.9.2 Fixed a type in the plugin URL Bumped to show compatibility with WordPress 3.0.2 0.9.1 Fixed bug with URLs with ampersands in them Added 'with_front' => false to the post type registration 0.9 Initial Beta Release