Free migration redirect mapper
Build your site migration redirect map in minutes
Add your old and new sitemaps. We match old URLs to their new homes, explain every match, and hand you a reviewed 301 redirect map to export or publish on RedirHub.
Frequently asked questions
Two lists of URLs: one from the old site and one from the new site. A sitemap URL works best, but you can also paste URLs (one per line) or upload a CSV exported from a crawler such as Screaming Frog. Full URLs and bare paths both work.
Redirect them to the closest relevant parent page (a category or section) where one exists. If the content is gone for good and nothing on the new site replaces it, mark it 410 Gone. Avoid sending everything to the homepage: search engines often treat that as a soft 404.
Use 301 (permanent) for a migration. It tells search engines the move is final so they update their index. Use 302 only for pages you’re moving temporarily, such as a staged rollout you plan to reverse.
Keep them for at least a year, and longer if old URLs still get traffic or backlinks. Removing redirects early turns those links back into 404s. Google recommends keeping site-move redirects in place for as long as possible.
Yes. Export a CSV, an Apache
.htaccess file, or an Nginx config and deploy it on your own server. Import it to RedirHub if you’d rather manage redirects without deploys, with analytics on every redirect and SSL on the old domain handled for you.A redirect map is a list that pairs every URL on your old site with its closest equivalent on the new one, plus the HTTP status to use (usually 301). Search engines and existing backlinks follow those redirects, so the traffic and ranking signals earned by old pages carry over instead of hitting a 404.