A redirect map is a list pairing every old URL with the new URL it should redirect to. During a site migration, domain change, or URL-structure change you implement these pairs as 301 redirects so visitors and search engines land on the right page and your ranking signals transfer instead of being lost to 404 errors.

You paste your list of old URLs, then enter a string to find and a string to replace it with. The tool applies that swap to every URL — for example replacing https://old.com with https://new.com, or replacing /blog/ with /articles/. The result is an old → new table. You can preview it before exporting, so it is easy to verify the rule did what you expected.

No. The Redirect Map Generator runs entirely in your browser and does not contact any of the URLs you paste. It is a pure text-transformation tool. To verify that the redirects you build actually work once deployed, run the new URLs through a redirect chain checker.

This generator applies a single find/replace pass to keep the rule transparent and predictable. For multi-step transformations, run it once, copy the output, paste it back into the old-URL box, and apply your second rule. For complex regex-based rewrites you will want server config rules (Apache/Nginx) instead.

For permanent moves — migrations, domain changes, retired URLs — use 301 (permanent). A 301 tells search engines the change is permanent and consolidates ranking signals onto the new URL. Use 302 (temporary) only for genuinely temporary situations like A/B tests or short-lived promotions. This map is direction-agnostic; you choose the status code when you implement it.

Export the map as CSV with old and new columns. Most CMS redirect plugins, CDN redirect rules, and hosting redirect importers accept a two-column CSV directly. For server config you can transform the pairs into RewriteRule (Apache) or rewrite/return (Nginx) lines. Keep the CSV as your source of truth for the migration.

The find/replace is literal, so whatever you type is matched exactly, including query strings and trailing slashes. If your old and new sites differ in trailing-slash behaviour, include that in the find/replace (for example find example.com/page and replace example.com/page/). Preview the output first to confirm edge cases before you ship the redirects.