Redirect Mapper

Map old URLs to new URLs and export as .htaccess, Nginx config, or CSV. Perfect for site migrations, URL restructuring, and redirect audits.

Redirect Rules 

    

    
    
    

  






  
Frequently Asked Questions

  

    
    
A 301 redirect is permanent — it tells search engines that the resource has moved permanently and to transfer PageRank (link equity) to the new URL. A 302 redirect is temporary — search engines keep the old URL in the index and do not transfer PageRank. Use 301 for site migrations and permanent URL changes; use 302 for temporary promotions or A/B testing.

  

  

    
    
Redirect chains (A → B → C) slow down page load and dilute PageRank at each hop. Google recommends keeping chains to a maximum of 3–5 hops, but ideally every URL should redirect directly to its final destination. When mapping redirects, always check that new URLs are not themselves redirects — link old URLs directly to the final destination.

  

  

    
    
Google has confirmed that 301 redirects pass full PageRank (previously there was a small loss, but Google updated their algorithm around 2016 to treat 301s the same as direct links). However, links pointing to deeply chained redirects may still lose some value due to crawl inefficiency.

  

  

    
    
Redirect directives in .htaccess should be placed before your RewriteRule block so they are processed first. If using Redirect directives, place them at the top. If using RewriteRule for redirects, include them at the top of your RewriteEngine block. Always test redirects in staging before applying to production.

  

  

    
    
No — server-side redirects (HTTP 301/302) are always preferred over JavaScript redirects. JavaScript redirects require the browser to first download, parse, and execute JavaScript before redirecting — adding significant latency. Googlebot can process JavaScript redirects but they are slower and less reliable for PageRank consolidation. Always implement a true HTTP 301 at the server or CDN level for any SEO-critical redirect.

  

  

    
    
A redirect map is critical for preserving SEO during a migration. Steps: 1. Crawl the old site using Screaming Frog to get every URL; 2. Map old to new in a spreadsheet; 3. Prioritize high-value pages with backlinks and traffic; 4. Implement before launch so redirects are in place before DNS changes; 5. Verify after launch by spot-checking key redirects; 6. Monitor for 404s in Google Search Console.

  






  
About This Redirect Mapper

  
This free tool generates correctly formatted redirect rules for Apache .htaccess, Nginx server blocks, or a clean CSV for import into other tools. Add old URL → new URL pairs manually, or paste a CSV to import dozens of redirects at once.

  
When to use this tool

  
    
    
  • Verifying that old URLs redirect correctly to new ones after a migration
    • 
    
  • Finding and eliminating multi-hop redirect chains
    • 
    
  • Checking whether a redirect is permanent (301) or temporary (302)
    • 
    
  • Auditing redirects set up by a CDN or reverse proxy
    • 
  

  
Standards & References

  





  
Related SEO Tools

  

    Canonical Tag Generator
    Robots.txt Generator
    XML Sitemap Generator
    Link Extractor
  







          

        
                        

          

            

              

                
Related Articles

                
In-depth guides and technical articles.

              

              View all →
            

            

                            

                
                                    
                                  
                

                  

                                        Seo
                                        Jul 21, 2026                  

                  Why You Should Never Remove a 301 Redirect — Maintenance, Chain Accumulation, and Latency Impact Over Time
                                    
301 redirects from URLs with meaningful inbound links should stay active indefinitely — removing them after "Google processes them" breaks all external links pointing to the old URL. Here's why redirect chains accumulate silently through multiple migrations, how redirect loop sources (HTTPS + WWW conflicts, CDN-origin conflicts) form, the latency impact of each additional redirect hop on Core Web Vitals, and when to use 308 instead of 301 for API method preservation.

                                  

              

                            

                
                                    
                                  
                

                  

                                        Seo
                                        Jun 24, 2026                  

                  How to Build a Redirect Map That Won't Create Chains — Inventory, Validation, and Format Selection
                                    
A redirect map looks manageable until 40 entries point to destinations that are themselves redirected — creating chains that slow crawlers and bleed equity. Here's the four-source URL inventory methodology (crawl + logs + GSC + sitemap), the three redirect types (one-to-one, pattern-based, 410 Gone), pre-implementation chain and loop detection algorithms, and why a CSV master reference generating server-specific formats is more maintainable than writing .htaccess directly.

                                  

              

                            

                
                                    
                                  
                

                  

                                        Seo
                                        Jun 21, 2026                  

                  301 Redirects Don't Work Instantly: How Search Engines Actually Process Them and How Long It Takes
                                    
A 301 redirect tells search engines a page has permanently moved — but they don't immediately forget the old URL or instantly transfer its signals to the new one. Here's the actual multi-phase timeline (recrawl, re-index, signal transfer), why temporary ranking drops post-migration are normal, what signals do and don't transfer through 301s, and why redirect chains reduce signal transfer even when they technically work.

                                  

              

                            

                
                                    
                                  
                

                  

                                        Seo
                                        Jun 12, 2026                  

                  Redirect Chains and Loops: How Years of Migrations Quietly Stack Redirects — and How to Flatten Them
                                    
A redirect chain often isn't deliberately created — it accumulates through years of independent, individually-reasonable migrations, each adding one more hop without anyone updating the original redirect. Here's why accumulated hops risk search engines failing to fully traverse a chain, the "flattening" fix, and the common CDN-to-origin protocol mismatch that causes HTTPS redirect loops.

                                  

              

                            

                
                                    
                                  
                

                  

                                        Seo
                                        Jun 10, 2026                  

                  JavaScript Redirects and Their SEO Pitfalls: How They Differ from Server-Side 301s
                                    
JavaScript redirects require Googlebot to execute JavaScript before discovering the destination — which adds a multi-hour or multi-day delay compared to server-side 301s. Here's how each redirect mechanism works for SEO, the Next.js server vs client distinction, and how to audit and collapse redirect chains.