Why does a website migration need a redirect map at all?
Every URL on your current site has accumulated its own ranking signals — backlinks, search history, trust — and when a migration changes those URLs without a plan, all of that accumulated value simply disappears rather than transferring to the new page, leaving both search engines and real visitors stuck at dead ends.
Think of it as a change-of-address form for your website. Just as forwarding your mail keeps letters reaching you after a move, a redirect map tells browsers and search engines exactly where each old page has gone, so nothing gets lost in transition.
What actually is a redirect map, structurally?
A redirect map is simply a spreadsheet with at least two columns — the old URL and its corresponding new URL — along with the redirect type used for each pair, typically 301 for a permanent move, serving as the single source of truth your developers work from during the migration.
- Old URL: the exact current address of each page
- New URL: the closest, most relevant equivalent on the new site
- Redirect type: almost always 301 for a genuine migration
- Status: whether that redirect has been tested and confirmed working
Why does the redirect type matter this much?
A 301 redirect tells search engines the move is permanent and passes nearly all of the original page's ranking signals to the new URL, while a 302 redirect signals a temporary change and search engines are far more cautious about transferring any authority through it — using 302 by mistake for a permanent migration is one of the most common, costly errors in this process.
If you spot 302 redirects anywhere in your configuration for URLs that should have moved permanently, convert them to 301 immediately. That single fix often resolves a meaningful chunk of unexplained post-migration ranking loss.
How do you actually build the URL inventory to start with?
Crawl your existing site with a tool like Screaming Frog or Sitebulb to export a full, complete list of every URL the crawler finds, treating this as a comprehensive inventory rather than a sample — missing even a handful of high-traffic pages here creates gaps that surface as broken links weeks after launch.
- Export your complete current URL list using a crawler, your XML sitemap, and analytics data together, since no single source is fully complete on its own
- Cross-reference with Google Search Console to catch older URLs still receiving search traffic that a fresh crawl might miss
- Note each URL's current traffic and backlink count so you can prioritize the migration's riskiest pages first
How do you match old URLs to their new destinations?
Crawl your new site (or staging environment) the same way, then manually match each old URL to the new page covering the closest, most similar content — a direct one-to-one match, never a wildcard assumption that "everything under this folder just goes to the new equivalent folder," since that approach reliably creates mismatched redirects.
Where the content genuinely no longer exists on the new site, redirect to the most topically relevant page available rather than defaulting to the homepage. A mass redirect to the homepage wastes the individual ranking value each old page had built and sends a poor signal to both users and search engines.
What mistakes cause the most damage during this process?
Redirect chains, redirect loops, and mass homepage redirects are the three most damaging mistakes in a redirect map, since each one either wastes ranking signal, confuses crawlers, or actively breaks the user experience the redirect was supposed to protect.
- Redirect chains: URL A redirects to B, which redirects to C — every hop adds delay and can dilute the ranking signal passed along; redirect A directly to C instead
- Redirect loops: a page that eventually redirects back to itself, which breaks the page entirely for both users and crawlers
- Mass homepage redirects: sending every unmatched old URL to the homepage rather than its actual closest equivalent, which wastes individually earned ranking value at scale
Does trailing slash and capitalization handling actually matter?
Yes — inconsistent handling of trailing slashes, www versus non-www, and HTTP versus HTTPS variations creates duplicate, competing versions of the same redirect that confuse search engines about which URL is actually canonical, so pick one consistent convention and redirect every variant to it.
Decide these conventions once, early, and apply them consistently across the entire redirect map rather than handling each URL's formatting ad hoc as you go.
How long should redirects actually stay in place after launch?
Keep redirects active for at least one year after migration, since external sites linking to your old URLs often don't update those links for months or even years, and every time a search engine crawler follows one of those old external links, the redirect needs to still be there to pass the ranking value through.
For high-authority pages or URLs with many external backlinks, maintaining the redirect indefinitely is the safer long-term choice. Removing redirects too early — based on an assumption that "Google has probably updated its index by now" — is a common misconception that causes real, lasting ranking damage.
What should you test before the migration actually goes live?
Test every single row in the redirect map inside a staging environment until each source URL resolves in exactly one hop to a live, correct destination — this single testing step is what separates a migration that preserves rankings from one that quietly loses them.
- Confirm the correct status code (301, not 302) fires for every redirect
- Check for broken destinations, redirect chains, and redirect loops specifically
- Verify HTTP-to-HTTPS and www/non-www behavior is handled consistently
- Document who owns redirect deployment, validation, and rollback, so nothing falls through the cracks if something breaks after launch
What should happen after the new site goes live?
Update your internal links to point directly to the new destination URLs rather than relying on the redirect chain to handle navigation, and update your XML sitemap to include only the new, live URLs — redirects protect old links, but your new site's everyday navigation shouldn't depend on them.
Monitor Search Console closely in the weeks immediately following launch for crawl errors, unexpected 404s, or sudden ranking drops, since this window is when any gaps in the redirect map typically surface first.