New researchTechnical SEO & AI Search · 2027Explore the framework

International URL mapping for SEO migrations

Map old and new localized URLs by language and region, prevent cross-locale redirects, and update hreflang, canonicals and sitemaps together.

Part of the Technical International SEO series. For the full picture, start with Technical international SEO: the complete implementation guide.

International URL mapping is the old-to-new redirect plan for pages that have language or regional variants. A simple domain replace may send /de/schuhe/ to a missing path or an English category, even while most redirects look successful. This guide concentrates on mapping and QA across locales. The site migration checklist covers the whole launch, while the ccTLD migration guide focuses on country-domain consolidation.

How do you build an international URL map?

Inventory the canonical old URLs for each locale, not just one master-language sitemap. Google’s site-move guidance recommends mapping old URLs to new destinations and updating annotations, internal links and sitemaps. Add data from sitemaps, CMS exports and logs so important legacy URLs are not missed.

Old URL Locale and intent New URL Mapping decision
/en/shoes/trail/ English trail category /en/running/trail/ Equivalent category
/de/schuhe/trail/ German trail category /de/laufschuhe/trail/ Translated equivalent
/fr/guide/ancien/ French retired guide None yet Review content lifecycle

Include content type, canonical target, expected status and owner in the working map. A 301 to a live but irrelevant language page is not a successful mapping. The redirect mapping guide covers the general one-to-one redirect method.

What do you do with missing or changed translations?

Classify exceptions before writing wildcard rules. A translated slug may not follow the English path. A product may exist in one market but not another. Two regional pages may have been merged, or one translation may be retired. Choose a relevant equivalent where one exists; otherwise document whether the old page should remain, return a suitable error or lead users through a helpful local navigation path. Do not force all unmatched localized URLs to a global homepage.

Google’s multi-regional guidance recommends separate URLs for locale variants and warns that automatic content changes based on IP or language headers can hide variants from Googlebot. Keep every intended locale URL directly reachable and linked.

Which signals must change with the URLs?

The redirect is only one part of the move. Google’s site-move documentation says to update self-canonicals, hreflang annotations, internal links and sitemaps to new URLs. Its localized-pages guide requires each hreflang set to identify its members, including the page itself, with reciprocal references.

For each migrated locale set, verify:

  1. Every old URL reaches its intended same-locale new page directly.
  2. The final page returns 200, is indexable and has the expected content.
  3. Canonical points to the intended new canonical URL.
  4. Hreflang names the new URLs for every available locale and has reciprocal entries.
  5. Navigation, language switcher and sitemaps no longer use the retired URLs.

Use the hreflang errors guide for syntax and return-link problems. This article is about keeping the URL inventory and all its relationships consistent through a move.

How do you test and monitor the mapping?

Before launch, test the entire redirect map mechanically and review a sample of final pages from every language and region. Check the exceptions manually. After launch, crawl old and new sets, inspect a few canonical selections in Search Console, and report clicks and indexing by locale rather than only global totals. A stable sitewide line can hide one market that was redirected to the wrong language.

Expect search signals to take time to move as Google recrawls; do not treat day-one position changes as proof that the mapping failed. Treat wrong targets, errors and missing alternate links as concrete defects to fix immediately.

International URL mapping checklist

  • Inventory canonical old URLs separately for every locale.
  • Pair pages by language, region and intent, not just path shape.
  • Review missing translations and merged content as exceptions.
  • Test direct redirects and the final page’s status and language.
  • Update canonicals, reciprocal hreflang, links and sitemaps to new URLs.
  • Keep each locale accessible without forced IP or header routing.
  • Monitor indexing and performance by market after launch.

Frequently asked questions

Where should a missing translation redirect during a migration?

Do not automatically send it to an unrelated homepage or different-language page. Decide whether a genuinely equivalent replacement exists; otherwise handle the old URL according to the page's lifecycle and provide useful navigation.

Should hreflang use old or new URLs after launch?

Use the new canonical localized URLs in the complete hreflang set. Update self-references and reciprocal alternate references together so no page still points to a retired location.

Can a URL pattern replace a page-by-page map?

A pattern can cover truly regular paths, but inspect exceptions such as translated slugs, missing products and merged content. Test the resulting target and language for a representative sample from every locale.

Should users be forced to a locale based on IP?

Avoid making a locale reachable only through an IP or language redirect. Google warns that its crawler may not discover all variants when content changes by location or Accept-Language, so keep explicit crawlable locale URLs and links.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows