301 Redirect Map Generator | .htaccess & Nginx Rules

Turn a migration list into ready-to-deploy 301 rules for Apache, Nginx or a redirect plugin, with chain detection. Runs entirely in your browser — nothing is uploaded, nothing is stored.

Migrations fail on redirects, not on design

Almost every traffic collapse after a redesign traces back to the redirect map: URLs mapped to the homepage instead of their equivalent, chains three hops deep, or whole sections forgotten. This tool converts your old-to-new list into deployable rules and flags any source that redirects to another redirected URL.

Rules for a clean map

• Redirect every old URL to its closest equivalent, never to the homepage in bulk.
• Use 301 for permanent moves; 302 only for genuinely temporary ones.
• One hop, always — chains waste crawl budget and leak signal.
• Preserve query strings only when they change the content.
• Keep the map in version control; you will need it again.

Migration checklist

1. Crawl the live site and export every indexable URL before launch.
2. Pull the top 500 URLs by clicks and links — these must be mapped by hand.
3. Generate rules here and deploy them with the new site, not after.
4. Re-crawl the old URL list post-launch and confirm every one returns a single 301.
5. Submit updated sitemaps and watch Search Console coverage for two weeks.

Verify what you deployed

Test the live behaviour with the redirect checker to confirm each URL resolves in one hop with the right status code.