301 Redirects – Redirect Manager vs Redirect multisite user to their own site (UNMAINTAINED)

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

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.