Redirect Mapping & Canonicalization

The Redirect Mapping Planner estimates the SEO risk of a site migration based on how old URLs are handled. ## Concept Overview * **301 Redirect:** "I moved here forever." Passes equity. * **404 Not Found:** "Gone." Equity evaporates. * **Redirect Chain:** A -> B -> C. Bad for speed and crawling. * **Canonical:** "I am a copy, credit the original." Similar to a redirect but the user stays on the page. ## Key Variables & Intuition * **Link Equity:** The SEO value (authority) a page has accumulated. Deleting the page destroys it. * **User Experience:** Landing on a 404 is a bad UX. Landing on an irrelevant page (homepage) is also bad. ## Assumptions * All 301s are implemented correctly. * Direct 301s pass 100% equity (Google's stated stance). * Chains lose efficiency (simulated as 15% loss). ## Limitations & Edge Cases * **Orphan Pages:** Pages not linked internally but indexed. They need redirects too. * **PDFs:** Harder to redirect on some platforms. * **External Links:** You can't control links pointing to you. You *must* redirect the inbound URL. ## Practical Tips * **Keep the Old Domain:** If rebranding, keep the old domain active with redirects forever. * **Audit Chains:** Screaming Frog can find chains. Fix them by pointing A -> C. * **Wildcard Redirects:** Use Regex to redirect `/blog/2023/*` to `/blog/*` to save manual mapping. ## Common Mistakes * Letting the old domain expire. * Redirecting everything to Home. * Forgetting to update internal links (why force a user to redirect if you can link directly?).

Redirect mapping is the 'plumbing' of the internet, ensuring that when content moves, users and bots can still find it. ## Origins & Why It Emerged In the early web (1990s), moving a file physically moved its URL. "Link Rot" was rampant. The HTTP status code 301 (Moved Permanently) was defined in RFC 2616 (1999) to solve this. SEOs quickly realized that search engines used 301s to pass "PageRank," making redirects essential for site migrations. ## How It Evolved in Practice Initially, SEOs feared 301s caused a "Damping Factor" (loss of PageRank, rumored to be 15%). In 2016, Google's Gary Illyes confirmed that 301s no longer lose PageRank. The focus shifted from "Equity Preservation" to "Crawl Budget Optimization" and "Latency Reduction." ## Modern Usage Today Modern migrations use automated logic (Regex redirects) to handle millions of URLs. "Edge Redirects" (Cloudflare/Akamai) handle redirects at the CDN level, reducing server load. Canonical tags (`rel=canonical`) work alongside redirects to manage duplicate content without forcing a browser redirect. ## Common Misconceptions * **"302 is fine":** 302 means "Temporary." Google might not pass equity. Always use 301 for permanent moves. * **"Redirect to Home":** Redirecting a specific product to the homepage is treated as a Soft 404 by Google. Redirect to a relevant category instead. * **"Wait for Google to find it":** No. Submit a sitemap containing the OLD urls to force Google to crawl the redirects faster.