Redirect Mapping for Migrations: The Complete 2026 Guide

Site migrations are the highest-risk SEO operation most organizations undertake. A domain change, URL restructuring, or CMS migration can erase years of ranking investment. The difference between a successful migration and a catastrophic one comes down to one file: the redirect map.

A redirect map is a structured mapping of every old URL to its new URL equivalent. Every page, image, PDF, and API endpoint must have an entry. Without an entry, that URL returns a 404.

A typical redirect map is a CSV with columns for old URL, new URL, status code, and priority.

Before mapping redirects, you must know every URL on the site. Use a crawler to export a complete URL inventory.

Include all HTML pages, images and PDFs with inbound links, API endpoints used by third parties, pagination URLs, filter and sort URLs, AMP and canonical variants, and legacy URL patterns from previous migrations. Export the full list to a CSV as your source inventory.

For every URL in the source inventory, determine the correct destination in the new site structure.

Mapping priorities run from exact match (same content, same path, ideal) through content match (same content, different path, preserves link equity) to category match (similar content, parent category, acceptable). Homepage fallback is last resort and should be avoided. For URLs with no equivalent content, return a 410 Gone instead of redirecting to the homepage. Homepage redirects dilute link equity and confuse crawlers.

A redirect map with errors will cause failures during the migration. Check for broken formats, self-referencing redirects, circular redirects, chains longer than one hop, and protocol mismatches. Write a validation script or use Google's redirect mapper template.

Choose implementation method based on infrastructure. Server-level redirects via .htaccess or nginx are fastest. CMS plugins work for smaller sites. CDN redirects via Cloudflare or Fastly offload processing from the origin server.

Deploy to a staging environment and test every mapped URL. Verify each old URL returns the correct status code and redirects to the expected destination without chains. Verify response times stay under 300ms per hop and mobile redirects match desktop redirects.

Monitor for at least 90 days post-migration. Watch Google Search Console for 404 spikes and indexing errors. Check crawl reports for new redirect chains. Segment organic traffic by page type and compare pre and post migration.

Homepage fallback for everything creates confusion and wastes crawl budget. Missing trailing slash consistency causes partial failures. Case sensitivity mismatches produce unexpected 404s. Ignoring query parameters leaves edge cases unhandled.

You crawl and inventory every URL on the live site. You build the redirect map CSV with old URL, new URL, and status code columns. You validate the map for chains, loops, and format errors.

You implement redirects using server-level rules. You test every redirect in staging before production deployment. You monitor Google Search Console daily for 90 days post-migration.

Note the gap. This post synthesizes 2025 and 2026 data from three sources: Google Search Central's site moves documentation, Moz's redirect mapping guide, and Screaming Frog's site migration checklist. Two non-public migration patterns from enterprise deployments remain undisclosed. Replication required.

Redirect maps determine migration success or failure. Audit every migration.