Nov
17

How to Map Old URLs to New Ones During a Migration: A Step-By-Step Guide

11/17/2026 11:00 AM 작성자 Seovaro Team 의


How to Map Old URLs to New Ones During a Migration: A Step-By-Step Guide

When a website moves to a new domain, platform, or structure, every old address needs a deliberate destination, and that decision is recorded in a URL mapping document. Who owns this work? Usually a project lead coordinating developers, content owners, and SEO input, because a missed page means lost visitors and broken bookmarks. What is at stake is continuity: readers, search engines, and partner sites all arrive through old links and expect to land somewhere sensible.

Where does mapping fit in the wider project? It sits between the content inventory and the technical build, and why it matters is simple: redirects can only be implemented accurately if someone has already decided, page by page, where each old URL should go. How you run the process, with clear stages, owners, and sign-offs, determines whether launch day is calm verification or frantic patching.

This guide sets out the full procedural blueprint, treating mapping as a managed deliverable, not a spreadsheet filled in the night before launch.

Build the Complete Inventory of Old URLs First

No mapping can be better than the list it starts from. Begin by assembling every old URL that exists or has existed recently enough to still receive visits, then reconcile the sources against each other so gaps are visible before any decisions are made.

Gather addresses from several places, because no single source is complete on its own.

  • Crawl data: a full crawl of the current site, capturing live pages, status codes, and internal link counts.
  • Sitemap and CMS exports: published pages, attachments, and taxonomy archives that a crawl may miss.
  • Analytics and search data: pages that received visits or impressions, including older URLs no longer linked internally.
  • Server logs and backlink reports: addresses that outside sites still request, even if they currently return errors.

Clean the combined list first. Remove duplicates, normalise trailing slashes, and record the current status of each address.

How to Map Old URLs to New Ones in a Working Spreadsheet

The mapping spreadsheet is the central project document, so set it up for review, not just data entry. Each row is one old URL, and the columns should let any reviewer understand the decision and its status without asking the author.

Columns every mapping sheet needs

  1. Old URL, exactly as it exists today, with its current status code.
  2. Proposed new URL, or an explicit decision to retire the page.
  3. Match rationale, such as same content, merged content, or nearest relevant section.
  4. Owner and reviewer, with a status field for drafted, reviewed, and approved.
  5. Implementation and test status, completed after the redirects are built.

Work through the sheet in priority order: highest-traffic and most-linked pages first, then the long tail in batches by section. Apply the core rule strictly, which is one-to-one mapping wherever the content survives. Only merge pages when the new destination genuinely covers the old topic, and only retire a page when nothing relevant remains, recording that choice rather than leaving a blank.

Review passes matter as much as the first draft. Have section owners confirm that destinations make sense for readers, and use Google guidance on site moves and address changes as a reference point when the team debates edge cases such as changed paths on the same domain versus a full domain change. For related planning checklists, see the Seovaro blog.

Turn the Approved Map Into Redirect Rules

Once the map is approved and frozen, hand it to the developers as the single source of truth. Late edits should go through the same document with a change note, never through side conversations, so implementation and testing always reference the same version.

Implementation usually groups rules by pattern where the structure is regular, with individual rules for exceptions and high-value pages. Each approved row should produce either a permanent redirect to the stated destination, or a deliberate retirement response for pages with no successor. Chains must be avoided at build time: if an old URL already redirected somewhere, the new rule should point directly to the final destination in the map.

Before launch, freeze content changes where possible, with a cut-off point and a mop-up pass for anything published after the inventory.

QA, Launch-Day Checks, and Post-Launch Monitoring

Quality assurance happens on staging first. Test every mapped URL, not just a sample, by requesting each old address and confirming it returns a single permanent redirect to the exact approved destination. Automated checking is essential at this scale, because manual spot checks reliably miss the rows with typos and swapped destinations.

On launch day, repeat the full check against the live site as soon as the new version is public, then work through a short operational list.

  • Confirm the homepage, top landing pages, and checkout or enquiry flows resolve correctly.
  • Check that the new sitemap is live and that internal links point to new URLs directly.
  • Verify analytics tracking fires on the new site and note the launch time for later comparisons.
  • Monitor server logs and error reports for old URLs returning not-found responses.

Keep monitoring for several weeks. Log files will surface old addresses the inventory missed, often from printed materials, partner sites, or old bookmarks, and each one deserves a late addition to the map rather than a shrug. Close the project only when error volumes settle and every late discovery has been resolved.

Make your QA pass faster and more thorough: try the Open All URLs tool to work through your mapped addresses in batches and confirm each old URL lands exactly where the spreadsheet says it should.

Frequently Asked Questions

What if an old page has no equivalent on the new site?

Choose deliberately between the closest relevant section page and retiring the URL. Record the decision and its rationale in the mapping sheet. Avoid sending unrelated retired pages to the homepage, which confuses visitors and weakens the redirect signal.

How long should redirects from a migration stay in place?

Keep them indefinitely if possible, and for at least a year at minimum. Old links, bookmarks, and printed references can surface long after launch, and permanent redirects cost little to maintain once they are correctly implemented.

Should every old URL be tested before launch?

Yes. Sample testing misses the individual typos and swapped rows that cause real losses. Automated batch testing of the full map on staging, then again on the live site, is a standard part of a well-run migration project.

Who should sign off the final mapping document?

The project lead should collect sign-off from content owners for destination choices and from developers for feasibility. That dual approval makes the frozen spreadsheet a reliable single source of truth for implementation and launch-day testing.