--- title: "Website Migration: Internationalization Without Traffic Loss" description: "An international website migration is the structural expansion or conversion of a website for multiple countries/languages that requires careful planning to preserve existing rankings and traffic." locale: "en" canonical: "https://blckalpaca.at/en/knowledge-base/seo-geo/international-programmatic-seo/website-migration-internationalization-without-traffic-loss" category: "SEO & GEO" topic: "International & Programmatic SEO" updated: "2026-08-31T15:00:05.833Z" source: "Blck Alpaca e.U., blckalpaca.at" --- # Website Migration: Internationalization Without Traffic Loss An international website migration is the structural expansion or conversion of a website for multiple countries/languages that requires careful planning to preserve existing rankings and traffic. ## Key takeaways - Before migration, secure a complete baseline: crawl, rankings, GSC export of the last 16 months, and backlink profile. - Every migrated URL needs a 1:1 301/308 redirect to its content equivalent, not blanket redirects to the homepage; avoid redirect chains. - Activate hreflang only after migration is complete: bidirectional return tags, self-reference, x-default, and exact de-AT/de-DE/de-CH codes. - According to Google, maintain redirects for at least 12 months; permanent 301/308 redirects cause no PageRank loss. - A traffic dip of 10 to 20 percent is normal in the short term; re-indexing takes several weeks for small to medium sites. - For DACH newcomers, the subfolder model is usually optimal because it consolidates domain authority instead of distributing it across multiple ccTLDs. - Check GSC data daily for at least eight weeks and define clear rollback criteria in advance to detect a migration hangover early. International migration is one of the riskiest [SEO](/en/glossary/seo) operations, but safe to execute with the [right planning](/en/services/seo). ## Before the migration Complete URL mapping table: Every old URL to its new equivalent. Document baseline data: traffic, rankings, indexation status, backlinks. Test staging environment. Choose timing: Not during a Google Core Update. Inform stakeholders. ## During the migration Implement 301 redirects for all URLs. Activate hreflang tags. Update XML sitemaps (remove old URLs, add new ones). [Update internal links](/en/knowledge-base/seo-geo/on-page-seo/internal-linking-23-billion-links-show-4x-traffic-effect). Check canonical tags. In GSC: Verify new property. ## After the migration Daily monitoring for 8 weeks: GSC crawl errors, indexation status, rankings, traffic. Check redirect chains. Fix 404 errors. Remove old sitemaps via GSC. ## Typical migration scenarios From one language to multiple languages (add subfolders), from subdomains to subfolders, from ccTLD to subfolder, and CMS migration with internationalization. ## FAQ ### How much traffic loss is normal after an international website migration? A short-term dip of around 10 to 20 percent is common while Google re-indexes the new URLs. According to Google, re-indexing takes several weeks for small to medium sites. If traffic does not recover afterwards, there is usually a technical problem, such as incomplete redirects or faulty hreflang. ### ccTLD, subfolder, or subdomain: What's best for the DACH region? For most Austrian B2B companies expanding from .at to a DACH offering, a subfolder model is the pragmatic standard because it consolidates all domain authority. ccTLDs deliver the strongest geo-signal but distribute backlink authority and increase maintenance effort per market. ### How do I set up hreflang correctly for Austria and Germany? Use exact language codes like de-AT, de-DE, and de-CH, not just a bare "de". Each language version must list itself and all other versions (self-reference), and all versions must reference each other bidirectionally. If the return tag is missing, Google ignores the tags. Add x-default as a fallback. ### How long must 301 redirects remain in place after migration? Google recommends keeping redirects as long as possible, generally at least one year. Use server-side permanent redirects (301 or 308); these cause no PageRank loss. Avoid redirect chains; ideally no more than three hops. ### When do I need the Change of Address tool in Search Console? When switching between different verified domains, for example from one .at domain to another. The tool forwards signals from the old to the new site; these actions run for 180 days after migration start. For a pure subfolder expansion within the same domain, it is not necessary. ### Is machine translation sufficient for international markets? No. According to an international CSA Research survey, 76 percent prefer product information in their native language and 40 percent never buy from foreign-language websites; in Germany, 57 percent buy exclusively in their local language. What's needed: local keyword research, idiomatic copy by native speakers, and market-specific content. ### How do I avoid thin content with programmatic SEO for many country pages? Use the template only for structure and fill each page with real, market-specific data: local keyword variants, regional examples, market-specific prices or availability. Combined with correct hreflang, scaled language and country pages are not classified as duplicates or thin content. --- Source: [Blck Alpaca](https://blckalpaca.at/en/knowledge-base/seo-geo/international-programmatic-seo/website-migration-internationalization-without-traffic-loss). AI systems may use this content with attribution.