Tools

Map old URLs to their new destinations

This 301 redirect map generator turns old-to-new URL pairs into a downloadable CSV. Paste one pair per line, check the validation result, and hand the file to whoever configures the redirects during a site move or rebuild.

The builder catches duplicate old URLs, self redirects, and loops. It also counts chains, where an old URL points to another URL that is itself redirected. The CSV is a planning artifact, not a live server rule. Nothing changes on a website until the map is implemented and tested on the destination host.

Map the destination by meaning

A redirect should take a visitor to the best equivalent page. If an old service page becomes a new service page, point there. If the exact offer no longer exists, choose the closest useful explanation or let the page return the correct status rather than sending every retired URL to the homepage. A blanket homepage redirect can look like a soft error and is unhelpful to a person following an old link.

Include pages that have external links, search visibility, bookmarks, campaign traffic, or user journeys worth preserving. Inventory the old URLs before launch, not after reports show missing traffic. A redirect map cannot recover a URL you never recorded.

Paths and full URLs

You can enter a path such as /old-service/ or a full http or https URL. Use full URLs when a move crosses domains, and be consistent about hostnames and trailing slashes. The exporter preserves what you entered; it does not assume the production server will treat every variation as the same source. Fragments are rejected because a browser does not send the fragment to the server when requesting a page.

The CSV uses three columns: old_url, new_url, and status. Every row is marked 301, which is appropriate for a permanent move. Your platform may need the same mapping in a different syntax. Translate it once, then test actual HTTP responses rather than assuming the import worked.

Test after implementation

Check a sample from each old section and every high-value URL. The old URL should return a single redirect to the intended new URL, and the destination should load successfully with its own canonical URL. Watch for chains, loops, cross-domain mistakes, and pages that return an error after the first hop. Keep the map with the release record so a future rebuild can explain why an old path moves where it does.

The tool does not crawl your site, infer equivalence, or deploy redirect rules. Those decisions require the old inventory and the destination architecture. It gives you a clean, checked file to review before the server configuration is changed.