Part of the Technical International SEO series. For the full picture, start with Technical international SEO: the complete implementation guide.
Moving example.de/produkt/ to example.com/de/produkt/ may simplify infrastructure, but it also removes a clear country-code domain signal from the URL. A ccTLD SEO migration needs the normal URL-move work and a locale-by-locale review. The technical international SEO guide compares the URL structures; if the domains also carry different content, the guide to merging two websites covers that side.
How do you plan a ccTLD SEO migration?
Inventory each regional site’s canonical URLs, then map each one to an equivalent page in the new structure. Google’s international site guidance describes ccTLDs as a strong country signal and documents subdirectories and subdomains as alternatives. A new /de/ path can be valid, but the site must make its German pages and relationships clear.
| Before | After | Specific check |
|---|---|---|
example.de/produkt/ |
example.com/de/produkt/ |
Same German product and availability |
example.fr/produit/ |
example.com/fr/produit/ |
French content and currency still correct |
example.de/hilfe/ |
Relevant German help page | Do not send it to English homepage |
Build separate inventories for each locale. Include articles, products, category pages, images, PDFs and hreflang annotations. Benchmark Search Console by country and page group, not only total traffic. The broader migration checklist covers general launch QA.
What happens to hreflang and canonicals?
Replace old URLs in every hreflang set with new fully qualified URLs. Google’s localized versions documentation says alternates can live on different domains, must list themselves and their counterparts, and need reciprocal references. Test a complete set, not one tag on one page. Keep each indexable locale page self-canonical unless you have a deliberate duplicate strategy; a canonical to the English page can erase the regional version you meant to preserve.
Update sitemaps, navigation, internal links, structured-data URLs and any language selector. A German page should be reachable directly at its URL without an IP or browser-language gate. Google warns that automatic locale adaptation can prevent it from finding all variants. The hreflang errors guide covers syntax and reciprocity checks.
How do you redirect the old country domains?
Use direct permanent redirects from each old URL to its equivalent new locale URL. Do not redirect every .de page to /de/ or, worse, to the global homepage. Google’s site-move guide warns against irrelevant redirects and recommends keeping them long term. Verify that the final page returns 200, is indexable, and has the right language, currency and content.
If whole country domains move, review Search Console Change of Address requirements for each source and destination. The tool does not replace redirects or correct a broken hreflang set. Stage locales where practical so a country-specific issue is easier to isolate.
How do you monitor each locale?
Inspect Google-selected canonicals, index counts, search clicks and impressions by country and language URL group. Compare old and new URLs together. A country may decline while the global total looks steady, so separate reporting matters. Crawl both old and new URL sets after launch and check a representative product, article and category in each locale.
ccTLD migration checklist
- Map every old regional URL to a relevant new locale URL
- Preserve translated content, pricing and availability where relevant
- Replace all hreflang, canonical, internal-link and sitemap URLs
- Test reciprocal hreflang sets and direct page-level redirects
- Keep locale pages accessible without IP-based redirection
- Verify old domains and new property in Search Console
- Monitor each country and URL group, not only total traffic
The redirect moves the visitor; consistent locale signals help the right replacement appear in the right market.
Frequently asked questions
Is moving from a ccTLD to a subfolder just a domain change?
No. It is a URL migration plus an international-site change. Review regional content, hreflang, canonicals and user navigation as well as redirects.
Does Google require ccTLDs for international SEO?
No. Google documents country domains, subdomains and subdirectories as possible locale-specific URL structures. Choose one you can maintain with clear content and annotations.
Should hreflang point to old or new URLs after launch?
It should point to the current canonical locale URLs. Update every member of each hreflang set and check reciprocal references after the move.
Should I redirect visitors based on IP address?
Avoid making locale content reachable only through IP-based redirects. Google says IP location is not reliable for detecting all variants and recommends explicit locale URLs and links.