The 301 Redirect Map Builder helps turn an old URL inventory and a new URL inventory into a migration map you can review before launch.
How the redirect mapping works
The tool normalizes URL paths and first pairs old and new URLs whose final slugs match exactly. Remaining URLs are paired by line order. It then flags old URLs without a destination and new URLs that were not used.
Review every redirect before deployment
Automated matching can speed up migration work, but topical equivalence still requires judgment. An old service page should redirect to the closest replacement resource, not merely a URL with a similar-looking slug.
Why redirect maps matter for SEO migrations
Good 301 mapping preserves user paths, helps search engines transfer signals to replacement URLs and reduces 404s after redesigns, CMS changes and domain migrations. Redirecting every removed page to the homepage is usually a poor substitute for one-to-one mapping.
Apache and CSV output
The Apache export uses simple Redirect 301 rules for mapped rows. The CSV output is better when redirects will be imported into a plugin, CDN, spreadsheet or deployment workflow.
Migration QA after the map is installed
Crawl the old URL list, confirm every redirect returns the intended status, check for chains and loops, update internal links to point directly to final URLs, and verify canonical tags and XML sitemaps use the new URLs.
Frequently asked questions
Should every old URL be redirected?
No. URLs with no useful replacement may appropriately return 404 or 410. Redirect only when a meaningful destination exists.
Are 302 redirects okay for a permanent migration?
For a permanent replacement, 301 is the clearer signal. Temporary redirects are better reserved for genuinely temporary changes.