SEO-Friendly Website Migration URL Mapping Template and Redirect Checklist
site migrationURL mappingSEO recovery301 redirect planwebsite launch checklist

SEO-Friendly Website Migration URL Mapping Template and Redirect Checklist

PPortal Redirect Editorial Team
2026-11-01
8 min read

Use this URL mapping template and recurring checklist to plan 301 redirects, test migrations, fix broken backlinks, and monitor SEO recovery.

A successful website migration begins with a clear URL mapping plan, not a last-minute list of redirect rules. This guide provides a reusable URL mapping template, a 301 redirect checklist, and a monitoring routine for preserving useful backlinks, reducing crawl problems, and identifying SEO recovery issues after launch.

Overview

A migration can change domains, URL paths, page templates, protocols, subdomains, or all of them at once. Each change creates a possibility that an old URL will lead to the wrong destination, return an error, create a redirect chain, or remain indexed when it should be consolidated.

The core task is to connect every important old URL with the most relevant live destination. In most permanent migrations, that connection is implemented with a server-side 301 redirect. A redirect should not simply send every old page to the new homepage. It should preserve user intent and, where appropriate, help search engines understand that a page has moved permanently.

Before writing rules, create a mapping document that records the old URL, its proposed destination, redirect status, implementation location, test result, and follow-up status. Treat this document as a working control sheet before launch and as an audit record afterward.

For a broader review of chains, loops, status codes, and broken destinations, see The Complete URL Redirect Audit. If the migration involves an entire domain, also review How to Redirect an Old Domain to a New Domain Without Losing SEO Signals.

What to track

1. Build the URL mapping template

Use one row for every meaningful old URL. A practical spreadsheet can include these columns:

  • Old URL: The complete legacy URL, including its path and any important variant.
  • URL type: Product, service, article, category, landing page, image, PDF, or another content type.
  • Traffic and link priority: A simple high, medium, or low rating based on known traffic, conversions, backlinks, or business importance.
  • New URL: The closest relevant destination on the new site.
  • Mapping decision: Redirect, retain, consolidate, remove, or investigate.
  • Status code: Usually 301 for a permanent move; document any intentional 302 or 307.
  • Reason: For example, “path changed,” “content consolidated,” or “no suitable replacement.”
  • Rule location: Apache, Nginx, Cloudflare, a WordPress plugin, application routing, or another system.
  • Pre-launch test: Not tested, passed, failed, or blocked.
  • Post-launch result: Final response code, destination, indexing status, and notes.

Export URLs from the old site wherever possible. Useful inputs include the XML sitemap, server logs, analytics landing pages, search performance data, internal links, and known backlink reports. Do not rely on the current sitemap alone: it may omit old URLs that still receive visits or links.

2. Decide whether each URL needs a redirect

Map an old page to a new page when the new destination serves substantially the same purpose or is the closest useful successor. If several old pages are being combined, map them to the consolidated page rather than creating a long sequence of intermediate redirects.

Do not redirect unrelated pages merely to avoid a 404 response. A misleading destination can frustrate visitors and make the migration harder to diagnose. If an old URL has no appropriate replacement, document the decision and use the response that best reflects the site’s intended behavior. The important point is that the outcome is deliberate, tested, and consistent.

3. Track canonical and redirect relationships separately

A redirect tells the browser and crawler to go somewhere else. A canonical link usually tells crawlers which version to treat as the preferred one while the page remains accessible. They are not interchangeable. Use a redirect when the old URL should no longer be used; use canonicalization when multiple accessible versions need consolidation but the page may still be served.

After launch, check that the new pages have self-consistent canonical URLs, that redirected pages are not included in the new XML sitemap, and that internal links point directly to final destinations.

4. Track technical variants

Include every relevant combination of protocol, hostname, and path in the test set. Common examples include HTTP to HTTPS, www to non-www, trailing-slash variations, uppercase paths, legacy query parameters, and old subdomains. Choose one canonical host and protocol, then verify that alternate versions resolve consistently without creating loops or unnecessary hops.

For implementation differences between DNS forwarding, server redirects, and browser behavior, see Domain Forwarding vs URL Redirects. DNS alone does not replace an HTTP redirect when the browser must be sent from an old URL to a new one.

Cadence and checkpoints

Before launch

  1. Freeze the mapping file and record who approved exceptions.
  2. Confirm that every high-priority old URL has a destination or a documented reason not to redirect.
  3. Load redirect rules in a staging environment or isolated test configuration where possible.
  4. Test representative URLs from every pattern, directory, hostname, and protocol variant.
  5. Check that one old URL reaches one final destination without a chain.
  6. Verify that destination pages return the expected successful response and do not redirect again unnecessarily.
  7. Update internal links, navigation, structured references, canonical tags, and the XML sitemap to use final URLs.
  8. Prepare a rollback copy of the previous configuration and preserve the pre-migration URL inventory.

A bulk redirect test is especially useful when rules are generated from patterns rather than entered individually. The Bulk Redirect Testing guide covers the checks to perform before and after a release.

Launch day

Test a small, representative sample immediately after the switch, then expand to the high-priority list. Confirm that the chosen canonical hostname and protocol resolve correctly, key templates load, forms and tracking still work, and no redirect rule is catching assets or unrelated paths.

Review access logs for spikes in server errors, unexpected status codes, repeated requests for old URLs, and possible redirect loops. Keep a timestamped record of configuration changes so later traffic or indexing changes can be compared with what actually happened.

First week and continuing checks

During the first several days, review the highest-value URLs and any failures reported by monitoring tools. Then perform a broader crawl to find broken internal links, redirect chains, orphaned pages, incorrect canonical tags, and sitemap entries that still reference old locations.

After the initial period, a monthly check is suitable for an active site, while a quarterly review may be sufficient for a stable site with few structural changes. Campaign links, short links, and QR code destinations deserve their own ownership and expiration review because they may continue receiving visits long after a migration. See QR Code Redirect Management and Short Link Governance for Teams for related controls.

How to interpret changes

A migration rarely produces a single clean signal. Interpret several measurements together rather than treating a temporary traffic change as proof that every redirect succeeded or failed.

  • Redirect response: A mapped old URL should return the intended status and final destination. Unexpected 404, 410, 5xx, or repeated 3xx responses require investigation.
  • Redirect chains: If an old URL points to URL B and URL B points to URL C, change the old rule to point directly to URL C where practical.
  • Redirect loops: A URL that repeatedly alternates between hosts, protocols, or paths often indicates conflicting application, server, CDN, or canonicalization rules. Disable overlapping rules, then test each layer separately.
  • Organic landing pages: Compare the pages receiving search visits before and after the migration. A decline limited to a directory may indicate incomplete mappings or content changes in that section.
  • Indexed URL patterns: Watch for old URLs remaining visible alongside new URLs, parameter variants multiplying, or important new pages failing to appear in crawl and indexing reports.
  • Backlink destinations: Prioritize external links that still point to old, broken, or low-relevance locations. Where appropriate, repair the source link and maintain a relevant redirect. The Broken Backlink Recovery guide provides a practical prioritization approach.
  • Analytics attribution: Check that campaign parameters, referral data, and conversions survive the redirect path. A technically correct redirect can still create measurement gaps if tracking parameters are stripped or rewritten.

When a problem appears, isolate the variable. Test the old URL directly, follow each hop, inspect the final page, and compare the result with the mapping sheet. Avoid adding another redirect as a quick fix before identifying which existing rule caused the issue.

When to revisit

Revisit the mapping and redirect audit on a monthly or quarterly cadence, depending on how often the site changes. A stable corporate site may need only a quarterly review, while a publishing, ecommerce, or campaign-heavy site benefits from monthly checks.

Perform an additional review whenever the site changes hosting, CDN, CMS, domain, URL structure, navigation, international setup, mobile handling, or analytics configuration. Also revisit the plan after a major content consolidation, a redesign, a security incident, or a noticeable change in organic landing-page performance.

Use this action list for each review:

  1. Export new crawl, analytics, log, sitemap, and backlink data.
  2. Compare newly discovered URLs with the existing mapping file.
  3. Run a redirect checker against priority old URLs and representative URL patterns.
  4. Remove obsolete rules only after confirming that the URLs no longer receive useful traffic, links, or operational requests.
  5. Fix chains, loops, broken destinations, and internal links pointing through redirects.
  6. Record status changes, owners, test dates, and unresolved exceptions.

Keep the mapping sheet with the site’s release documentation. It becomes more valuable over time because it explains why each redirect exists and gives the next migration or redesign a reliable starting point.

Related Topics

#site migration#URL mapping#SEO recovery#301 redirect plan#website launch checklist
P

Portal Redirect Editorial Team

Technical SEO Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.