Home / Tools
Tools

301 Redirect Generator

Assemble 301 redirect rules for Apache (.htaccess) or Nginx. Add single redirects or paste a whole list at once in bulk mode. 301 redirects protect Google rankings and guide users from old URLs after a structure change or migration. Everything is computed in your browser. More in our article on 301 redirects and 404 errors.

Redirects

Enter the source path (e.g. /old-url) and the destination (a path or a full URL).


                    
For Apache paste the rules into .htaccess above the # BEGIN WordPress block. For Nginx paste into the server { } block and reload the configuration. Point old addresses directly to their destination to avoid redirect chains.

                

            

        

    


    

        

            

                
What a 301 redirect is and why to use it

                
A 301 redirect is a permanent redirect from an old URL to a new one. When the server responds with a 301 code, it tells the browser and the search engine that the resource has moved for good. For the user it means a smooth transition to the new address, and for Google a signal to transfer most of the SEO value built up by the old address to the new one. That is why 301 redirects are crucial whenever addresses change: without them, old links from Google and other sites lead to 404 errors, and traffic and rankings drop. Correctly mapped 301s make a structure change or migration almost invisible to the search engine.

            


            

                
When you need a 301 redirect

                

                    

                        Permalink change
                        After changing the URL structure in WordPress, old addresses stop working. A 301 map from old to new preserves traffic and rankings.
                    

                    

                        Migration
                        When moving to a new address or server, 301 mapping is the single most important element of protecting your SEO equity.
                    

                    

                        Removed pages
                        When you remove a page replaced by another, redirect it to the closest topical equivalent instead of leaving a 404 error.
                    

                    

                        Merging content
                        When merging several similar articles into one, redirect the rest to the target version to concentrate the SEO value in one place.
                    

                

            


            

                
Redirect best practices

                
Point the old address directly to the destination, never through intermediate steps, because redirect chains (A to B, B to C) lengthen load time and weaken the transferred value. Redirect to the closest topical match, not everything wholesale to the home page, because Google often treats mass redirects to the home page as a soft 404. Use 301 (permanent) for permanent changes and 302 only for temporary ones. After deploying, check a few old addresses and monitor the 404 error report in Google Search Console, which we cover in our article on 301 redirects and 404 errors.

            


            

                
Frequently asked questions about 301 redirects

            

            

                
A permanent redirect from an old address to a new one. It tells the search engine the page moved for good, so Google transfers most of the SEO value. The user is sent automatically to the new address.

                
On any permanent address change: permalink change, migration, removing a replaced page, merging pages. For temporary changes use a 302.

                
A 301 is permanent and transfers SEO value to the new address. A 302 is temporary, for when the page returns to the old address, and does not transfer full value. For permanent changes choose 301.

                
Apache: into .htaccess in the root directory, above the WordPress block. Nginx: into the server block and reload the configuration. The generator produces both formats.

                
A single one has a negligible impact. The problem is chains (A to B, B to C). Point the old address directly to the destination to avoid chains that lengthen load time.

            


            

                
Tool and write-up: Marcin Szewczyk-Wilgan, WebOptimo. Rules consistent with Apache and Nginx configuration practice and keeping Google rankings after an address change. The generator runs in the browser, with no data sent.

            

        

    


    
Contact
Planning an address change or migration?
We will prepare a 301 redirect map and carry out the change without losing Google rankings. No obligation — a concrete proposal after a short conversation.
Phone
+48 608 271 665
Mon–Fri, 8:00–16:00
E-mail
kontakt@weboptimo.pl
We reply within 24h
Company
WebOptimo
VAT ID: PL6391758393











	Marcin Szewczyk-Wilgan - m4c.pl  Powered by FreeBSD  Edited in Vim