--- title: "SEO Migration Redirect Mapper & Validator — Free" description: "Map old URLs to new pages with explainable deterministic confidence, manual overrides, conflict detection, live redirect QA, and Apache, Nginx, Cloudflare, Vercel, or CSV export." canonical_url: "https://webaloha.co/tools/seo-migration-redirect-mapper/" markdown_url: "https://webaloha.co/tools/seo-migration-redirect-mapper.md" date_modified: "2026-07-20T00:00:00.000Z" --- # SEO Migration Redirect Mapper & Validator Last updated: Jul 20, 2026 Turn old and new URL inventories into an explainable redirect plan. Review alternatives, fix many-to-one conflicts, validate live chains, and export rules for your deployment platform—without uploading the files to an AI service. ## How to Build a Defensible Redirect Map 1. **Collect complete inventories.** Add every legacy URL that earned visits, links, rankings, or user bookmarks—not only URLs still present in the old sitemap. Supply new canonical URLs from staging or the launch site. 2. **Add identity signals.** URL-only matching works when structure survives the migration. Include titles or H1 values in pasted data or CSV when folders, slugs, domains, languages, or taxonomies changed. 3. **Generate explainable candidates.** The browser calculates every old-to-new pairing, shows the top candidates and their component signals, blocks weak automatic homepage fallbacks, and leaves matches below your threshold unmapped. 4. **Resolve ambiguity.** Review low confidence rows, click alternatives, type overrides, mark unchanged URLs as Keep, and inspect every many-to-one destination. A consolidation is valid only when one new page satisfies all mapped legacy intent. 5. **Validate after rules are deployed.** Work through every 40-row batch. Check that redirects reach the intended destination in one permanent hop and Keep URLs still return a successful page. Fix chains, temporary hops, loops, wrong targets, and redirected destinations. 6. **Export and retain the evidence.** Download the review CSV for sign-off, then generate the appropriate server format. Keep the approved mapping as a launch artifact and compare it with post-launch crawls. ## Why Redirect Mapping Is the Highest-Risk Migration Detail Google’s current [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) says complex moves need an old-to-new URL map before redirects are implemented. Its [redirect guidance](https://developers.google.com/search/docs/crawling-indexing/301-redirects) recommends server-side permanent redirects for permanent moves. A direct relevant mapping helps both visitors and crawlers understand where content went. - **Protect legacy discovery:** old organic results, bookmarks, backlinks, campaigns, and internal links should reach an equivalent destination. - **Avoid false consolidation:** sending every deleted page to the homepage hides missing content and creates poor user journeys. - **Remove chains:** old rules often survive several redesigns. Point each known legacy URL straight to the final canonical URL. - **Make sign-off auditable:** confidence, alternatives, overrides, validation evidence, and review notes belong in one shared artifact. ## Migration Inputs Most Teams Forget The old XML sitemap is a starting point, not a complete legacy inventory. Add these sources before approving the map: - **Analytics:** organic and referral landing pages across a representative period. - **Google Search Console:** pages with clicks or impressions, including URLs no longer linked internally. - **Backlink exports:** URLs with valuable external links, including historic HTTP and hostname variants. - **Server logs and 404 reports:** URLs bots and people still request. - **CMS/database exports:** published, archived, product, taxonomy, media, and localized records. - **Crawls:** current links, canonicals, hreflang targets, pagination, assets, and existing redirect rules. - **Marketing records:** email, advertising, QR, partner, affiliate, and offline campaign URLs. ## Launch-Day and Post-Launch QA Checklist 1. Deploy rules to staging when possible and crawl every old URL against that environment. 2. Confirm one permanent hop to a relevant 200 destination; do not redirect into another redirect. 3. Update internal links, canonicals, hreflang, structured data, navigation, and the new XML sitemap to final URLs. 4. Keep the old domain and redirect infrastructure active long enough for users and search systems to process the move. 5. Verify both old and new Search Console properties and use Change of Address when the documented conditions apply. 6. Monitor 404s, server logs, indexing, page-level clicks, and important rankings after launch. Repair missed URLs instead of layering new chains. 7. Retest mapped URLs after CDN, CMS, routing, or domain configuration changes. ## Export Format Notes The Apache and Nginx exports create exact path matches and use 301; install them only in the matching legacy-host server context because the rule itself contains no source hostname. Cloudflare Bulk Redirect CSV follows Cloudflare’s current [no-header CSV format](https://developers.cloudflare.com/rules/url-forwarding/bulk-redirects/reference/csv-file-format/). Vercel bulk CSV and JSON use source, destination, and permanence fields as documented for [`bulkRedirectsPath`](https://vercel.com/docs/project-configuration/vercel-json#bulkredirectspath). Vercel sources are project-wide paths without hostnames, so split mixed-host inventories and deploy each file only to its intended legacy-host project. Always review the generated file against the version and routing layer you deploy. Deployment formats intentionally exclude Keep/no-redirect decisions. They also skip source URLs with query strings, percent-encoded or non-ASCII paths, and non-literal paths because request-URI handling differs across servers and platforms. Every excluded decision remains in the review CSV for explicit implementation and testing. Wildcards and regex are not inferred: compressing individually approved mappings into a broad rule without testing can redirect unrelated URLs. Next steps ## SEO Migration Redirect Mapper related tools and articles Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow. [![Redirect Checker Tool Online](https://webaloha.co/_astro/tool-redirect-checker.Dk1kVM-b_1uexDu.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Redirect Checker ](https://webaloha.co/tools/redirect-checker/)[![Canonical URL Checker Tool Online](https://webaloha.co/_astro/tool-canonical-checker.Dd7XtjXS_2jUxdz.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Canonical URL Checker ](https://webaloha.co/tools/canonical-url-checker/)[![Sitewide Duplicate Content Finder Tool](https://webaloha.co/_astro/tool-sitewide-duplicate-content.CW6FlB4T_Z29ClMc.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Sitewide Duplicate Content Finder ](https://webaloha.co/tools/sitewide-duplicate-content-finder/)[![Technical SEO Audit: What to Check and How to Fix It](https://webaloha.co/_astro/blog-technical-seo-audit.BQGR9Gga_Z1kSpyl.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Technical SEO Audit: What to Check and How to Fix It ](https://webaloha.co/technical-seo-audit-guide/)[![Duplicate Content SEO: What It Is and How to Fix It](https://webaloha.co/_astro/blog-duplicate-content-seo-guide.DC0sfnDB_Z1jE3Dm.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Duplicate Content SEO: What It Is and How to Fix It ](https://webaloha.co/duplicate-content-seo-guide/)[![Google Search Console Guide for Business Owners](https://webaloha.co/_astro/blog-google-search-console-guide.BOIwH8JU_18vk2t.webp?dpl=dpl_AM1rGg4hZQMeX9Xux5JT1y5ZTCmw) Google Search Console Guide for Business Owners ](https://webaloha.co/google-search-console-guide/) ## SEO Migration Redirect Mapper: FAQ How does the redirect mapper match old and new URLs? It runs deterministic comparisons in your browser using normalized path tokens, final-slug character similarity, optional page-title token overlap, and path-depth similarity. Exact paths receive a perfect score, while an unchanged old/new URL is marked Keep with no redirect required. Weak candidates are capped, non-home pages are not automatically mapped to a homepage, and every suggestion includes its strongest signals and alternatives. Is a high confidence score safe to publish automatically? No. Confidence measures similarity between the supplied records, not semantic equivalence or business importance. Review valuable URLs with traffic, backlinks, conversions, revenue, and historic rankings. A direct match can still be wrong when product or service intent changed. What should I include in the old URL inventory? Combine the current XML sitemap with CMS exports, analytics landing pages, Google Search Console pages, backlink targets, server logs, and a full crawl. A sitemap normally excludes redirected, orphaned, deleted, or non-canonical URLs—the pages most likely to be lost during migration. Can the mapper read titles from XML sitemaps? Standard XML sitemaps contain locations and optional metadata such as last modification, but normally no HTML page titles. Sitemap imports therefore match on URL structure. Paste or upload CSV with URL and title columns to add a stronger content-identity signal without fetching every page. The bounded importer accepts uncompressed XML sitemaps and indexes; .xml.gz files are not supported. What do duplicate-target warnings mean? Two or more old URLs currently map to the same destination. That can be a valid consolidation, but it can also reveal an over-broad fallback. The tool flags every many-to-one mapping so you can confirm that the new page satisfies the intent of every source. How does live redirect validation work? The validator checks deterministic batches of up to 40 resolved rows per run; click again to continue until every row is checked. It follows at most eight HTTP redirects, confirms destinations return 2xx, detects loops and wrong targets, and verifies that Keep/no-redirect URLs remain live. It does not execute JavaScript redirects or carry visitor cookies. Should migrations use 301 or 308 redirects? Both are permanent server-side redirects. Google treats permanent server-side redirects as strong signals. Platform conventions differ: Apache and Nginx exports here use 301, Cloudflare uses 301, and Vercel bulk redirects express permanence and currently serve permanent redirects as 308. Test the behavior in your own stack. What happens to unmapped old URLs? They are never silently sent to the homepage or included in deployment exports. Decide whether each URL has a relevant replacement, should remain live, should intentionally return 404 or 410, or needs a new destination. Broad irrelevant redirects can confuse users and may be treated like soft 404s. Are uploaded inventories stored or sent to an AI service? Pasted lists, CSV files, matching, overrides, and export generation stay in your browser. Sitemap URLs are sent to Web Aloha only so the bounded endpoint can read their public XML. Live validation sends the selected public source and destination URLs to the endpoint. No paid AI API is used and the endpoint has no report-storage step. Free 48-Hour Website Audit Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory. [Get My Free Audit 💪](https://webaloha.co/free-website-audit/) ## Planning a Migration Where Rankings Matter? We inventory legacy value, map content, test staging, validate every redirect, and monitor the launch so valuable pages do not disappear between platforms. [Discuss Your Migration 🚀](https://webaloha.co/contact/)