Redirect Mapper — Help & Documentation

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

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

Enter your URL mappings — one pair per line in the format: old URL → new URL.

Choose the redirect type — 301 for permanent changes, 302 for temporary.

Select your server format — Apache, Nginx, Cloudflare, etc.

Review for loops or chains, then copy the generated rules to your server config.

When to Use Redirects

Site migrations need proper redirects. Without redirects, you lose link equity, traffic, and search rankings. Always map old URLs to their closest equivalent on the new site before launch.

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 in a staging environment before deploying to production.
Monitor crawl errors in Google Search Console after migration.
Keep redirects in place for at least one year after migration.

Supported Platforms

Apache — .htaccess redirect rules
Nginx — server block rewrite rules
Cloudflare — Page Rules or Redirect Rules format
Vercel — vercel.json redirects array
Netlify — _redirects file format
IIS — web.config rewrite rules

301 vs 302: Use 301 (Moved Permanently) when the URL change is permanent and you want to transfer SEO value. Use 302 (Found/Temporary) for short-term changes, A/B testing, or when the original URL will return.