#SEO (Search Engine Optimization)

How to Build a URL Mapping Table for a Site Migration

Match old addresses to their new destinations. Use a worked table to handle retained, merged and removed pages and check redirects before and after launch.

Published: Reading time: 4 minute.
How to Build a URL Mapping Table for a Site Migration


Quick Answer

A URL mapping table records the destination and expected response for each old address. Permanently moved pages point to relevant replacements; unchanged addresses remain, and removed content is not sent to the homepage merely to reduce error counts.

The new website looks finished, yet an old product link opens the home page. The design works; the product the visitor wanted has disappeared. A URL mapping table records what should happen to each old address before the migration goes live.

Decide Which Addresses Will Change

A URL is a page's web address. A change to the domain, folder or page name may require an old link to lead somewhere new. If you are changing hosts while keeping the same URLs, do not create redirects for every page. If the rebuild itself is still undecided, first compare repairing and redesigning the website.

Collect addresses from the CMS, sitemaps, a site crawl, visit logs and Search Console. None of those sources should be assumed complete. An old PDF may still receive external links even though it no longer appears in the navigation.

What Belongs in the Mapping Table?

Record the old full URL, language, existing content, decision, new full URL, expected status, owner and test result. Instead of marking a row “done”, record the destination actually reached and the check date. The person choosing the content destination may not be the developer implementing the redirect.

Illustrative address map for a maintenance company
Old PathDecision and DestinationExpected Result
/service/boiler-careThe same service moves to /services/boiler-maintenance301 or 308 → relevant page returning 200
/contactThe address and contact page stay200 directly
/care-plan-a and /care-plan-bBoth plans are genuinely combined at /maintenance-plansEach old address → combined page
/past-event-registrationRegistration is removed with no suitable replacement404 or 410, without an unrelated redirect
/tr/hizmet/kombi-bakimTurkish equivalent at /tr/hizmetler/kombi-bakimiEnds on Turkish content

The paths are illustrative. Use complete addresses, including scheme and hostname, in the working document. Matching similar words is insufficient: the destination must answer the question the old page answered.

Let the Content Determine the Redirect

Use a server-side 301 or 308 for a permanent move. Google's redirect documentation distinguishes permanent changes from temporary ones. A mapping table is not executable configuration; a developer still needs to implement the server or CMS rules.

Sending every retired address to the home page rarely answers the visitor's question. The maintenance plans in the example share a destination because their content has been consolidated. An expired registration page without an equivalent may instead need a proper 404 or 410 response. A quiet week of traffic is not enough evidence to decide that useful content should disappear.

Test the Same Row Before and After Launch

  1. Check that the destination presents the right content and language. A 200 status alone does not prove either.
  2. Send the old address directly to the final destination where possible. Resolve redirect loops and unnecessary chains.
  3. Match the new page's canonical, language alternates and internal links to the new addresses. Check for access restrictions or noindex left from staging.
  4. Check the new sitemap and important page links. Use the technical SEO guide for the broader crawling and indexing review.

An English service URL could reach a Turkish category page without producing an HTTP error. It would still fail the mapping check. Recording “correct service, correct language” alongside the final status gives the reviewer a usable acceptance condition.

Keep the Table After Launch

Monitor redirect failures, requests to old addresses and crawling of the new pages. In its site move guidance, Google recommends keeping redirects as long as possible, generally for at least a year. They are not a temporary measure to remove immediately after release.

Search visibility can fluctuate during a move; a mapping table cannot guarantee unchanged traffic. When implementation, content decisions and monitoring belong to different teams, include their owners and completion evidence in the SEO project scope. The final document should still explain why each old address changed.

FREQUENTLY ASKED QUESTIONS (FAQs)

No. The map records the decision about where each existing page belongs. A redirect implements that decision. Check that the destination answers the original visitor need before asking a developer to configure the rule.

No. A 301 indicates a permanent move and may be the expected result. Test the final destination, its content and language rather than treating every redirect as a failed page.

301 and 308 indicate permanent redirects; 302 and 307 indicate temporary ones. Select the response according to the actual move. A temporary maintenance arrangement should not be mistaken for a permanent replacement.

Yes, when addresses change. A CMS feature or plugin can implement rules, but it does not settle which new page is the right content replacement. If addresses remain the same, avoid adding redirects without a reason.

A pattern-based rule can cover a consistent address change. It still needs exceptions checked: merged pages, removed content and different language structures may require individual decisions. Test those cases separately before launch.

Aim to send it directly to the final destination. If A points to B and B points to C, update A to point to C where practical. A loop that sends C back to A must be fixed rather than accepted as a longer chain.