# How do I migrate an international website without losing SEO? > You migrate an international website without losing SEO by preserving the structure that separates your markets and the signals that connect them. An international site serves different countries or languages through some structure, country domains like a separate site per country, subdirectories like a country or language folder, or subdomains, and search treats each version as serving a specific audience. The migration must keep that intact in three ways. First, preserve or 301 redirect every localized URL, so each market's pages keep their rankings rather than collapsing or 404ing. Second, keep your hreflang reciprocal and pointed at the new addresses, so search still knows which version serves which audience and does not treat your translations as duplicates. Third, hold any country targeting you have set, so a version aimed at one country stays aimed there. The deeper risk than a single market dropping is breaking the links between versions, which can scramble which audience sees which pages. If you are also reconsidering the structure itself, treat that as a deliberate change with full redirects, not a side effect. WPBuildAI scans your site and returns the URL list across all your country and language versions, so you can preserve and reconnect each market through the move. Source: https://wpbuildai.com/how-to-migrate-an-international-website-without-losing-seo/ By lawrence-arya ยท 2026-06-08 --- You migrate an international website without losing SEO by preserving the structure that separates your markets and the signals that connect them. An international site serves different countries or languages through some structure, country domains like a separate site per country, subdirectories like a country or language folder, or subdomains, and search treats each version as serving a specific audience, as the guidance on [managing multi-regional and multilingual sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites) describes. The migration must keep that intact in three ways. First, preserve or 301 redirect every localized URL, so each market's pages keep their rankings rather than collapsing or returning 404. Second, keep your hreflang reciprocal and pointed at the new addresses, so search still knows which version serves which audience and does not treat your translations as duplicates. Third, hold any country targeting you have set, so a version aimed at one country stays aimed there. The deeper risk than a single market dropping is breaking the links between versions. WPBuildAI scans your site and returns the URL list across all your country and language versions, so you can preserve and reconnect each market through the move. Language subdomains need declaring individually, which Google spelled out in June 2026 by naming [en.example.com among the variants requiring their own Change of Address request](https://ppc.land/googles-site-move-guide-now-covers-www-and-non-www-domain-variants/), so an international move is several migrations declared together rather than one. ## An international site is a network of versions The starting point is to see your site not as one site but as a connected set of versions, each aimed at a market. You might have a French version, a German version, and a United States version, each with its own URLs and content, and search engines understand them as serving those audiences. What holds the network together is the signals that say which version is for whom and that they are equivalents of one another, not duplicates. A migration touches both the individual versions and the connections between them. So the goal is twofold: keep each version's pages and rankings intact, and keep the network of relationships, the hreflang and the targeting, intact. Thinking in terms of a network rather than a single site is what makes the international specifics visible. ## Preserve or redirect every localized URL Each version is made of URLs, and those URLs carry the rankings for their market, so the first job is the standard one applied to every localized address. List every URL across every country and language version, and either keep each at the same address on the new site or 301 it to its new equivalent in the same version. The danger is treating only the main market carefully and letting the others slip, so a smaller language version quietly loses its redirects. Every market matters to the audience it serves, so every version gets the full treatment. Web Almanac 2024 ([HTTP Archive](https://almanac.httparchive.org/en/2024/)) is a reminder of how many URLs a site has, and an international site multiplies that by the number of versions, so a complete URL map is essential. ## Keep hreflang reciprocal and current The connections between versions live largely in hreflang, the signals that tell search which version serves which language or region and that they are equivalents. A migration changes the URLs those signals point at, so hreflang must be regenerated to reference the new addresses, and it must stay reciprocal, with each version pointing at all the others and itself. If hreflang breaks, search may show the wrong language version to a user or treat your translations as duplicates, which is the network level failure that is worse than one market dipping. The mechanics of this are covered in detail in [what happens to hreflang tags after a migration](/what-happens-to-hreflang-tags-after-migration), and the principle from [telling Google about localized versions](https://developers.google.com/search/docs/specialty/international/localized-versions) is that the version relationships must be declared accurately at the new URLs. Rebuild hreflang as a first class part of the move. ## Hold your country and structure targeting Beyond hreflang, international sites often have targeting tied to their structure, and a migration must not lose it. If you use country code domains, the country association comes largely from the domain itself, so keeping the domains preserves it. If you use subdirectories or subdomains for countries, any targeting you have configured for those should be preserved or reconfigured on the new setup. The structural choice itself, country domains versus subdirectories versus subdomains, is a strategic decision with trade offs similar to the [subdomain versus subdirectory question](/subdomain-vs-subdirectory-for-blog-seo), and a migration is a tempting moment to change it. If you do change the structure, treat it as a deliberate, full migration of every localized URL with redirects, not a casual side effect, because changing how markets are separated touches every version at once. ## Do not collapse versions into duplicates A specific international failure to guard against is accidentally merging your versions into duplicates. If the migration makes two language versions resolve at overlapping URLs, or strips the signals that distinguish them, search may see near duplicate content across markets and consolidate them, hiding versions you want shown to their audiences. The protection is the combination above working together: distinct URLs per version, correct hreflang declaring them as equivalents for different audiences, and canonicals that reference each version as its own, not pointing across versions, following the [consolidate duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) guidance. Keep each market on its own distinct, canonical URLs, connected by hreflang, so search keeps them separate and serves the right one to each audience. ## Steps to migrate an international site 1. **Inventory every URL** across all country and language versions. 2. **Preserve or 301** each localized URL within its own version. 3. **Rebuild hreflang** reciprocal and pointed at the new addresses. 4. **Preserve country targeting** tied to your domains or structure. 5. **Keep versions distinct**, with self referencing canonicals, not merged. 6. **If changing the structure**, treat it as a full, deliberate migration. ## Worked example: moving a three-market site Imagine a company with United States, German, and French versions in subdirectories under one domain, moving to a new platform. The team inventories every URL in all three versions, then maps each to its new address and sets 301s within each version, giving the smaller French version the same care as the larger United States one. They regenerate hreflang so each page references its three counterparts plus itself at the new URLs, and confirm the references are reciprocal. They keep the subdirectory structure rather than changing it during the move, so targeting is undisturbed, and they set self referencing canonicals so the versions are not read as duplicates. After launch they check that a German user still sees German pages and that no two versions collapsed together. Each market kept its rankings and its audience, because both the versions and the connections between them were preserved, the same care as a careful [multilingual migration](/how-to-migrate-multilingual-wordpress-site-wpml-safe). ## Limitation: structure preservation is not a ranking gain It is fair to bound this. Preserving your international structure protects the rankings and audience routing you already have; it does not improve your standing in any market on its own. Keeping hreflang and targeting intact stops you from losing visibility or showing the wrong version, but growing in a market still depends on the content and reputation for that market, not on the migration. Likewise, a migration cannot fix an international setup that was already misconfigured before the move; it can only carry across what existed. So treat international migration care as protection of a working multi market presence, and address the strength of each market separately, recognizing that the move is about not breaking the network rather than strengthening any node in it. ## Common mistakes - Treating only the main market carefully and letting smaller versions lose redirects. - Letting hreflang break or point at old URLs, scrambling which audience sees what. - Losing country targeting tied to the domains or structure. - Collapsing distinct versions into near duplicates with overlapping URLs or cross canonicals. - Changing the structure casually during the move instead of as a deliberate migration. ## Key points You migrate an international website without losing SEO by preserving each market's version and the connections between them. Inventory and 301 every localized URL across all country and language versions, giving smaller markets the same care as the largest. Rebuild hreflang so it is reciprocal and points at the new addresses, and preserve any country targeting tied to your domains or structure, because the network level failure of broken connections is worse than one market dipping. Keep versions distinct with self referencing canonicals so they are not merged into duplicates, and if you deliberately change the structure, treat it as a full migration with redirects. Structure preservation protects the presence you have rather than improving any market on its own. WPBuildAI scans your site and returns the URL list across all your country and language versions, so you can preserve and reconnect each market through the move. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.