Website Migration URL Mapping Template: Build a Complete Redirect Plan
site migrationSEO migrationredirect mappingURL planningwebsite redesign

Website Migration URL Mapping Template: Build a Complete Redirect Plan

PPortal Redirect Editorial Team
2026-11-02
7 min read

Build a practical URL mapping plan for migrations, with spreadsheet fields, redirect rules, launch checks, and recurring SEO monitoring.

Website Migration URL Mapping Template: Build a Complete Redirect Plan

A well-maintained URL mapping plan helps protect search visibility, preserve useful backlinks, and give users a reliable path to content after a domain change, redesign, or CMS migration. This guide explains what to record, how to assign destinations, which checks to run before and after launch, and how to keep the redirect map useful after the migration is complete.

Overview

A website migration changes more than page design. URLs may change because of a new domain, revised folder structure, different CMS, updated product taxonomy, or a move from separate mobile pages to responsive templates. If an old URL no longer resolves to the right content, visitors can encounter errors and search engines may need to reassess the site’s structure.

A URL mapping document is the working record that connects each important old URL to its intended new destination. It should be created before implementation, reviewed by the people responsible for content and SEO, and retained after launch as part of your redirect audit history. The map is not limited to pages that currently receive traffic. It should also account for indexed URLs, valuable backlinks, bookmarked resources, campaign destinations, PDFs, images when relevant, and URLs found in analytics or server logs.

For most permanent content moves, the implementation will use a 301 redirect. The status code is only one part of the plan, however. A good migration also requires a relevant destination, consistent protocol and hostname rules, clean internal links, valid canonicals, updated XML sitemaps, and testing for chains and loops. For a broader checklist, see the SEO-friendly website migration URL mapping template and redirect checklist.

What to track

Start with a spreadsheet that gives every source URL a clear status and owner. The following columns provide a practical URL mapping template:

  • Source URL: The complete old URL, including the path and any meaningful file extension.
  • Source type: Page, product, category, article, landing page, PDF, image, campaign link, or other asset.
  • Source data: Organic visits, referring domains, conversions, backlinks, or other signals that help determine priority.
  • Proposed destination URL: The closest relevant new URL, written in its final canonical form.
  • Mapping decision: One-to-one redirect, consolidated destination, retained URL, removed URL, or no redirect required.
  • Redirect status: Planned, implemented, tested, passed, failed, or needs review.
  • Expected response: Usually 301 for a permanent move; record a different status only when there is a specific reason.
  • Destination status: The HTTP response, final URL, page title, canonical URL, and whether the destination is indexable.
  • Priority: High, medium, or low, based on traffic, links, conversions, business value, and user intent.
  • Owner and notes: The person responsible for resolving ambiguity, plus implementation details or exceptions.

Use one row per source URL rather than relying only on broad rules. A row-level record makes it easier to explain decisions and identify omissions. Keep the original source list in a separate tab so that later edits do not erase evidence of what was reviewed.

Map pages one to one whenever the equivalent content exists. If several old URLs are being consolidated, send each to the most relevant surviving page rather than automatically redirecting everything to the home page. A removed page with no suitable replacement may need a deliberate response instead of a forced redirect. Document that decision so it can be reviewed after launch.

Look for patterns only after the important individual URLs have been reviewed. A regular expression or folder-level rule can be efficient for predictable changes, but broad rules can also redirect unrelated paths or create loops. Test representative examples, including unusual slugs, uppercase characters, trailing slashes, parameters, and legacy file extensions, before applying a pattern to the entire site.

Cadence and checkpoints

Build the map in stages rather than treating it as a task for launch day.

Before implementation

Collect URLs from the current sitemap, crawl data, analytics, backlink reports, internal links, redirect logs, and important campaign documentation. De-duplicate the list without losing variations that may behave differently. Confirm the migration scope, destination structure, protocol, preferred hostname, and trailing-slash convention.

Then classify each source URL. Mark high-priority URLs first: pages with consistent organic visits, strong referring links, important conversions, or a role in navigation. Review proposed destinations manually. Similar wording is not enough; the destination should satisfy the likely intent of someone following the old link.

During implementation

Export the rules in the format required by the platform, such as Apache .htaccess, Nginx configuration, a Cloudflare rule, or a WordPress redirect tool. Keep the source map as the source of truth and record the deployed version separately. This distinction helps identify whether a problem is in the mapping decision, the rule syntax, caching, or the application.

Test redirects in a staging environment when possible. Confirm that the source returns the intended status, reaches the correct final URL, and does not pass through unnecessary intermediate URLs. A bulk redirect testing workflow is useful for checking a large map consistently.

At launch

Run a representative sample immediately, including high-priority URLs, each major URL pattern, protocol and hostname variants, old campaign links, and pages with known backlinks. Check both desktop and mobile experiences if the migration changes templates or routing. Verify that internal links point directly to the new URLs instead of relying on redirects.

After launch

Recrawl the old URL list and the new site. Review server responses, crawl errors, analytics landing pages, search performance trends, conversion paths, and reports of broken backlinks. Keep a dated change log for every correction. The redirect audit checklist can help organize checks for chains, loops, broken destinations, and inconsistent rules.

How to interpret changes

Not every fluctuation indicates a redirect failure. First separate technical symptoms from normal changes caused by seasonality, content updates, tracking changes, or the migration itself. Then compare the affected source URLs with their mapped destinations.

A rise in not-found responses often points to missing source rows, incomplete pattern coverage, or links to URL variants that were not included in the inventory. A rise in redirect chains suggests that an old redirect still points to an intermediate URL or that the new site contains a second layer of routing. Update the first redirect to target the final destination directly when possible.

Redirect loops commonly result from conflicting HTTP-to-HTTPS rules, www-to-non-www rules, application routing, or an incorrect regular expression. Test the full URL, not just the path, and inspect the sequence of responses with a redirect checker. A destination that returns a blocked, non-indexable, irrelevant, or error response is not a successful mapping even if the first hop is a 301.

If traffic falls for a group of URLs, compare the old and new page intent, title, content, internal links, canonical tags, and indexability. A redirect cannot preserve relevance when the destination is substantially different. For domain changes, verify that every hostname variant is covered and that the old domain remains configured long enough for monitoring and link updates. See the guide to redirecting an old domain to a new domain without losing SEO signals for a focused workflow.

When to revisit

Review the URL map at launch, at least weekly during the early post-migration period, and then monthly or quarterly depending on the site’s size and change rate. A high-change store, publisher, or campaign-heavy site benefits from more frequent checks than a small brochure site. The map should also be reopened whenever the CMS, domain, information architecture, analytics setup, or URL rules change.

At each recurring review, check five areas: new broken source URLs, redirect chains and loops, destinations receiving unexpected traffic, high-value backlinks pointing to obsolete paths, and rules that have become redundant. Compare the current redirect inventory with the XML sitemap and internal-link crawl. Remove obsolete temporary rules only after confirming that they are no longer needed, and retain a record of what was removed.

To turn the spreadsheet into an operating document, add a review date, next action, and accountable owner to every unresolved row. Sort by priority, resolve high-value failures first, and rerun the affected tests after each change. A clean redirect map is not a one-time migration artifact; it is part of ongoing link management and technical SEO hygiene. Schedule the next audit before closing the current one, so the plan remains useful when the next redesign, domain change, or content consolidation begins.

Related Topics

#site migration#SEO migration#redirect mapping#URL planning#website redesign
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.