Redirect Mapper Documentation

Overview: Generate redirect rules for site migrations, redesigns, and URL structure changes. Supports Apache .htaccess, Nginx, Cloudflare, Vercel, Netlify, and IIS formats with loop detection.

Key Features

  • Bulk URL mapping — paste old and new URLs
  • Multiple output formats (Apache, Nginx, Cloudflare, Vercel, Netlify, IIS)
  • Redirect chain and loop detection
  • 301 (permanent) and 302 (temporary) redirect support
  • Copy-to-clipboard output

How to Use

  1. Enter your URL mappings — one pair per line (old URL → new URL).
  2. Choose the redirect type — 301 for permanent, 302 for temporary changes.
  3. Select your server format — Apache, Nginx, Cloudflare, etc.
  4. Review for loops or chains and copy the generated rules.

When to Use Redirects

Site migrations need proper redirects

Without redirects, you lose link equity, traffic, and rankings. Always map old URLs to their closest equivalent on the new site.

Best Practices

  • Use 301 redirects for permanent URL changes to preserve SEO value.
  • Avoid redirect chains — each URL should redirect directly to the final destination.
  • Test all redirects before deploying to production.
  • Monitor crawl errors in Google Search Console after migration.
Supported Platforms
  • Apache (.htaccess)
  • Nginx
  • Cloudflare
  • Vercel
  • Netlify
  • IIS
Need Help?

If you have questions about the Redirect Mapper, feel free to reach out:

Contact Support
Try Redirect Mapper Back to Tools