We provide a collection of professional bulk 301 redirect generators - tools for the batch creation of a special code used to make permanent redirects. We have online generators for pure PHP and Apache .htaccess configuration file. RewriteRule and RedirectMatch supported.
301 redirect is a special information(301 code) sent to the browser or search bot by your server on a certain page visit. 301 code means moved permanently.
If your server is Apache and You have access to .htaccess file You need to choose RewriteRule or RedirectMatch generators. Use RedirectMatch generator only if already have a lot of such redirects you need to keep. In case You have access to PHP files only You can choose our PHP generator.
To keep your site searchable by search engines like Google you need to apply 301 redirects to old pages after url change. Without this information search bots can't understand (in most of the cases) that page url was changed, but the content is the same and valuable for to be visible in search results. If your income depends on organic search, there is a very special reason to do 301 redirects in the right way. So, if you decided to change your domain or just rename page url you need to make redirects. Our 301 redirect generator may help you with many situations.
1. You decided to change url for some page to make it more relevant to page content for a better user experience. - You need redirect from old url to new url.
2. You deleted some page and created a new page with similar content. - You may need to make such redirect to keep PageRank and positions in search.
3. You replaced the whole site with a newly built one and you have a new url structure. You will need to do bulk redirects. A redirect 301 code generator will help with your task list.
If You already have redirect code like Redirect 301 "/old" "http://example.com/new", note that these rules are handled with "mod_alias", but not "mod_rewrite". While both modules can do permanent redirects, "mod_rewrite" is more functional, what will do rewrite system more flexible and can help you in the future. For example, "mod_alias" can't fully handle query strings. These Apache modules have separate flow and Redirect 301 rules can conflict with Your new "mod_rewrite" rules. Also, be careful, because the rule works on a directory basis and all files inside directories and subdirectories will be redirected too. So, If you need to use batch online redirect generator and you have a small amount of Redirect 301 rules, we can recommend rewriting these rules with "mod_rewrite" functionality to keep the logic clean. For simple redirects and some heavy load enterprise solutions, mod_alias can be a good choice too. Mod_alias documentation here. Mod_rewrite documentation here.
Maybe, most popular server for WordPress is Apache. Best practices for WordPress 301 redirects is to use .htaccess file directives. Apache server users can locate .htaccess file in the root directory. You can use FTP connection or special plugins to edit your htaccess file. While many SEO plugins provide a possibility to add and manage 301 redirects in WordPress admin panel, we can't suggest using permanent redirect WordPress plugins because htaccess redirects are much faster and, therefore, better for user experience and for SEO in many cases.