Website Migration: Internationalization Without Traffic Loss

Why international migration is the riskiest SEO project

Internationalization touches almost every variable Google evaluates for ranking and indexing: URL structure, domain signals, canonical logic, internal linking, and language assignment. When several of these factors change at the same time, the sources of error add up. The risk is not theoretical. An international analysis of 18,786 websites with hreflang code shows that 31.02 percent contain conflicting hreflang directives. Such errors are typical during migrations, when old and new structures exist in parallel.

The DACH region adds a linguistic peculiarity: German is the shared language of Austria, Germany, and Switzerland, but the markets differ in law, currency, shipping, and search behavior. If you turn a purely German website into a DACH offering, you are, strictly speaking, internationalizing within the same language. That is more demanding than a classic language switch, because the language code alone does not differentiate the markets. The differentiation comes from de-AT, de-DE, and de-CH.

The economic leverage is high in the Austrian B2B environment. In January 2025, Austria had 8.69 million internet users, a penetration rate of 95.3 percent, so the market is almost completely reachable online. In May 2026, Google held a search engine market share of 81.87 percent in Austria, followed by Bing at 9.01 percent. In the DACH region, you therefore optimize a migration primarily for Google, without ignoring Bing entirely.

Pre-migration audit: measure the baseline before anything moves

Without a baseline measurement, you cannot prove success or damage after the migration. The audit before the move is the most important insurance against uncontrollable traffic loss.

• Full crawl: Capture all indexable URLs, status codes, canonicals, and the internal link structure. This crawl is the basis for the later URL mapping.
• Ranking snapshot: Document the positions of your most important keywords per target market, ideally separated by de-AT and de-DE, since SERPs differ between Austria and Germany.
• Traffic baseline from GSC: Export the Search Console data of the last 16 months at URL and query level. GSC retains data only for a limited time, so an export secures your basis for comparison.
• Backlink profile: Record which pages have external links. These are the URLs that must redirect cleanly after the migration; otherwise their link authority is lost.

Only once these four data sets are in place does the actual planning begin. A common mistake is to go looking for the baseline only after the first traffic drop, when the old data can no longer be retrieved.

Domain strategy: ccTLD, subfolder, or subdomain

The domain architecture is the single most consequential decision. Correcting it later means going through another migration.

• ccTLD (example.at, example.de): The strongest geo signal and the highest trust in each market. Drawback: each domain builds authority separately, backlinks are spread out, and the maintenance effort grows with every market.
• Subfolder (example.com/at/, example.com/de/): Consolidates all domain authority on one domain. Usually the most efficient choice for entering DACH, because a single strong backlink profile carries several markets. The geo signal comes from hreflang with a region code (such as de-AT) and local signals like address, phone number, and currency.
• Subdomain (at.example.com): Technical separation with a moderate split of authority. Practical when markets run on separate systems, but rarely the first choice from a pure SEO perspective.

For most Austrian B2B companies expanding from .at to a DACH offering, a subfolder model is the pragmatic standard: the hard-won authority of the existing domain stays consolidated. A hybrid model, such as a strong .at ccTLD plus subfolders for additional languages, is possible, but it makes the hreflang architecture considerably more complex.

Setting up the hreflang architecture correctly

hreflang does not boost rankings. It is an assignment signal: it tells Google which language version to serve to which user. Errors here do not lead to ranking losses through penalties. They lead to the wrong version appearing in the wrong market.

Three rules are technically mandatory. First, bidirectionality: if two pages do not both point to each other, Google ignores the tags. The return tag is therefore mandatory, not optional. Second, self-reference: each language version must list itself and all other versions. Third, x-default as a fallback for users whose language or region is not covered.

The international analysis shows how common these errors are in practice: 16.04 percent of hreflang clusters lack the self-reference tag, up to 47.95 percent of multilingual sites use no x-default, and 8.91 percent use invalid language codes. For the DACH region, the language code is critical: de-AT, de-DE, and de-CH must be written exactly. A bare "de" gives away the market differentiation, and invalid codes such as "de-österreich" are ignored.

The order matters: hreflang tags should go live only after the migration is complete and the redirects have been verified. hreflang that points to URLs that still redirect or do not exist yet produces exactly the conflicting directives that dominate the error statistics.

Redirect management: the backbone of every migration

Every migrated URL needs a 1:1 redirect to its content equivalent, not a blanket redirect to the homepage. Google recommends server-side permanent redirects such as 301 and 308, and permanent redirects do not cause a loss in PageRank. The widespread concern that redirects always cost link equity is unfounded with clean 301/308 mapping.

• Create a 1:1 mapping: Every old URL gets exactly one new target. The mapping table is built from the pre-migration crawl and fully checked before go-live.
• Avoid redirect chains: Googlebot follows up to 10 hops in a redirect chain; ideally, keep it to no more than 3 and fewer than 5. Every chain costs crawl budget and delays re-indexing.
• Keep redirects in place long term: Keep redirects for as long as possible, generally at least 1 year. Twelve months is the minimum, not the target.

Change of Address and monitoring in Search Console

For a domain change, the Change of Address tool signals the move. It forwards signals from the old site to the new one and tells Google to prefer the new site when choosing canonicals; these actions run for 180 days after the migration starts. The tool applies to moves between verified properties, for example from .at to another domain. For a pure subfolder expansion within the same domain, it is not relevant.

Re-indexing takes time. A small to medium-sized website needs a few weeks until most pages have moved; larger sites take longer. During this phase, check index coverage and crawl stats daily: if 404 errors or unexpected soft 404s rise, that points to gaps in the mapping.

Content localization instead of plain translation

A machine translation meets the language requirement on paper, but it does not match how people search. Keyword research has to be done again for each market, because Austrians search for different terms than Germans, even for an identical product.

Willingness to pay depends on language. According to an international CSA Research survey of 8,709 consumers in 29 countries, 76 percent prefer product information in their native language, and 40 percent never buy from websites in other languages. The effect is particularly strong in the German-speaking region: in Germany, 57 percent buy only from websites in their own language. Localization is therefore a condition for conversion, not a convenience feature.

In practice, this means local keyword research per target market, idiomatic copy by native speakers, market-specific examples, currency, legal information, and shipping information. In a B2B context, the correct technical terminology of the respective industry in the target country also counts.

Geo-targeting and technical infrastructure

Load time and server availability affect crawling and user experience across markets. A CDN distributes content to edge locations close to the user and smooths out latency differences between countries. Today, the physical server location is a weak geo signal. The actual market assignment comes from hreflang and local signals such as address, phone number, and currency; Google has discontinued the former country targeting setting in Search Console. Location still matters for load time: the infrastructure should be designed so that all target markets get comparable response times.

International link-building strategy

The domain strategy determines the link logic. With ccTLD setups, each country domain builds its authority separately, so you need local backlinks per market: Austrian sources for .at, German sources for .de. That takes more effort, but it signals strong local relevance.

With subfolder setups, authority consolidates on one domain. A backlink from a strong Austrian source strengthens the entire setup, including the subfolders for other markets. This consolidation is the central SEO advantage of the subfolder strategy and the reason it is often the most rational choice for resource-constrained B2B companies in the DACH region.

Programmatic SEO without the risk of thin content

Programmatic SEO generates large numbers of pages from templates, such as country or city variants of an offering. For internationalization, that is attractive because it lets you scale localization. The danger is thin content: pages that differ only by a swapped place name offer no value of their own and risk weak indexing.

The solution is to fill every generated page with real, market-specific data: local keyword variants, regional examples, market-specific prices or availability. The template provides the structure; the substance comes from the data. Combined with correct hreflang, this approach prevents scaled language and country pages from being treated as duplicates or thin pages.

Post-migration recovery and risk management

A short-term traffic dip after the migration is normal and no reason for knee-jerk action. As long as Google has not fully re-indexed the new URLs, rankings fluctuate. Re-indexing takes a few weeks for small to medium-sized sites, and for a domain change, the signal transfers run for 180 days.

Still, every project needs clear escalation criteria:

• Daily GSC monitoring: Check index coverage, crawl stats, and performance daily for at least eight weeks.
• Detect a migration hangover: If traffic stays well below the baseline after several weeks instead of recovering, there is usually a technical problem rather than a normal dip. Typical causes are incomplete redirect mapping, redirect chains, or faulty hreflang tags.
• Define rollback criteria: Before go-live, decide at what threshold and over what period a rollback happens. A rollback is the last option, not the first reaction, because it resets re-indexing once again.

The most effective risk management is still preparation: a complete baseline, a verified 1:1 mapping, a clean hreflang architecture, and patience during the transfer window.

Further reading

An international migration stands or falls on disciplined preparation. If you export baseline data, check the URL mapping completely, keep redirects for at least twelve months, and activate hreflang only after the migration is complete, you avoid most of the documented sources of error. In the DACH region, clean differentiation between de-AT, de-DE, and de-CH also determines market success. For more depth, read about the fundamentals of international SEO and country-specific optimization. If you don't want to handle the migration on your own, you can have us support you through it.