2026-04-22 · Baduno Editorial Team · 8 blog.readMin · Blog & Knowledge
ccTLD, Subdomain or Directory? The International Domain Strategy
baduno.fr, fr.baduno.com or baduno.com/fr – the choice shapes SEO, costs and maintenance for years. A decision aid without dogma.
The Three Models
Country code top-level domains (ccTLDs) send the strongest geo-signal, but require registration, maintenance and separate SEO authority per country. Subdomains separate cleanly but also distribute authority. Subdirectories consolidate all strength on one domain – and are the most economical path for most companies.
When ccTLDs Make Sense
Independent country subsidiaries with their own marketing, legally separate offerings or markets with strong domain preference (e.g. .de in Germany) justify the extra effort. Those who only translate but manage centrally gain little from ccTLDs and have more to manage.
Why We Usually Recommend Subdirectories
A single backlink strengthens all language versions, one technical update affects all, and hreflang cleanly connects the versions. This website itself uses /de/, /fr/, /fa/ – out of conviction and experience.
The Most Common Mistake
Mixing without a plan: .de for Germany, /en/ for England, subdomain for France. Such organically grown structures confuse both search engines and users alike. Choose one structure, implement it consistently, link via hreflang – that's the whole art.
Implementing hreflang correctly – no guesswork, but craftsmanship
The hreflang annotation is the most important technical signal for multilingual websites. It tells Google: 'This page also exists in language X for region Y.' In practice, this means: Every URL that is translated receives a self-referencing hreflang link in the <head> plus a link for each language/region variant. A common mistake is forgetting the x-default variant, which is shown to users without a matching language. Use ISO-639-1 for languages (e.g., 'de') and ISO-3166-1 alpha‑2 for regions (e.g., 'DE'), but only if the content is region-specific. Do not confuse hreflang with canonical – they have different purposes. Check your implementation with tools like Merkle's hreflang tag checker or directly in Google Search Console. Faulty hreflang links lead to missed impressions – and that's pure waste of money.
Canonical tags and avoiding multilingual duplicates
If the same content is offered in multiple languages, there is no duplicate content issue – provided hreflang is set correctly. Nevertheless, it is crucial to set a separate canonical tag for each language version that points to itself. This is the only way to avoid confusion when, for example, the CMS generates multiple URLs for the same page. For instance, if a product page is served under /de/produkt and /de/produkt.html, the canonical tag must point to the preferred URL. In practice, it helps to define consistently uniform URL structures and set up redirects from non-canonical to canonical URLs. This also includes parameter handling in Search Console: specify that language or tracking parameters should be ignored. This ensures that Google only sees your desired indexing targets.
Country selection and navigation – engaging the user
In addition to technology and SEO, user guidance determines the success of an international website. A country/language selector should be prominently placed – ideally at the top right, as a drop-down menu with flags and language codes. Should you offer automatic redirection based on browser language? Caution: This can lead to unwanted redirects if the user is browsing in a different country. Better: a one-time query or a cookie that stores the preference. The navigation should also respect the language version: clicking on a product in the German version should land on the German product detail page – not the English one. Also check whether your site is culturally appropriate in each country: date formats, currencies, payment methods. These are small details, but they build trust – and thus indirectly improve dwell time and conversion.
baduno.fr, fr.baduno.com or baduno.com/fr – the choice shapes SEO, costs and maintenance for years. A decision aid without dogma.
Organizing content management and translation workflow
An international website thrives on current content. Without a well-thought-out workflow, you quickly lose track. Recommendation: Use a CMS that natively supports multilingualism – such as TYPO3, Drupal, or WordPress with Polylang/WPML. Define a fixed process: source language, translation, review, approval, publication. Each language version should have its own editor who is also responsible for regional adaptations. Ensure that technical updates (new categories, snippets) are synchronized in all languages. A good tool maintains a translation memory and remembers recurring phrases. This avoids costs for repeated translations and speeds up the workflow. Keep in mind: A daily updated page in one language but outdated versions in others harms the user experience and can lead to bounce.
Server location and CDN – latency and geo signal
The physical proximity of your server to the target region can affect load time and is considered a weak geo-signal by search engines. For purely linguistic localization without country-specific targeting, a central server with a Content Delivery Network (CDN) is often sufficient. A CDN caches static resources such as images, CSS, and JavaScript on global edge nodes – measurably speeding up delivery. Dynamic content can be routed to the nearest data center node via DNS-based geo-routing or Anycast. However, note that Google does not directly use the web server's IP address as a ranking factor for country assignment; more important are hreflang, country settings in Search Console, and local directory listings. For ccTLDs (.de, .fr), a server in the respective country or a CDN with local PoPs is recommended to keep latency minimal. For subdirectory structures, a well-configured CDN is entirely sufficient. Ensure that your CDN correctly passes through hreflang headers and does not apply its own compressions that could disrupt the display of language identifiers. A performance audit using tools like PageSpeed Insights or WebPageTest will show whether your pages load quickly in all target markets. Also keep in mind that a slow page in a country – e.g., due to high latency from a central server – degrades user experience and indirectly negatively affects SEO signals such as bounce rate. Therefore, test your load times regularly from different regions.
Legal compliance and localization of T&C/Privacy Policy
International websites must comply with the legal system of each target market – this particularly concerns data protection, Impressum requirement, cookies, and T&C. A German online shop that also delivers to France needs a French version of its privacy policy and T&C that meet local requirements (e.g., the CNIL in France). Mere translation is not sufficient: legal concepts such as the data processor (Article 28 GDPR) must be transferred meaningfully, and country-specific regulations such as cookie consent under the ePrivacy directive vary. For each country, a separate legal text should be created tailored to the local legal situation. Technically, you implement this by creating separate pages for Impressum, privacy policy, and T&C per language version – linked via hreflang. Ensure that the cookie consent solution allows different settings depending on the region (e.g., tracking cookies in DE only after opt-in). It may also be necessary to specify a local representative (e.g., according to §5 TMG for Germany). Consult a lawyer specialized in international online law. And document your translation processes for legal texts: use certified translators or legal specialist translators to minimize liability risks. Because an incorrect legal text can lead to expensive cease-and-desist letters – this is not an SEO issue but a fundamental requirement for a credible international presence.
Localization Beyond Pure Translation – Considering Cultural Nuances
A successful international website is not limited to translating texts. It requires thoughtful localization that takes into account cultural conventions, legal frameworks, and local expectations. Date formats (MM/DD in the US, DD.MM in Germany), currencies ($, €, ¥), and measurement systems (metric vs. imperial) should be automatically adapted to the region. Visual elements such as colors (red symbolizes luck in China, often danger in Western countries), symbols, or images must also be checked for cultural acceptance. In Islamic countries, for example, depictions of limbs or alcohol are problematic. Furthermore, legal requirements may vary: imprint and privacy policy are subject to stricter rules in the EU than in other regions. Incomplete localization not only appears unprofessional but can also lead to legal consequences. Therefore, allocate sufficient budget for a thorough cultural review—ideally conducted by native speakers with market knowledge. This effort pays off through higher user acceptance and better conversion rates.
Technical Performance of Multilingual Websites – Focus on Loading Time
Loading speed is a critical ranking factor – and multilingual websites face additional challenges. If you use a ccTLD per country, you benefit from geographically distributed servers but must optimize each domain separately. With a central domain using subdirectories like /de/, /fr/, the technical responsibility lies with you. A Content Delivery Network (CDN) is therefore essential for international websites. It stores static assets (images, CSS, JavaScript) on servers close to users, reducing latency. Additionally, ensure that fonts and icons are not unnecessarily reloaded – a language may require different character sets (e.g., Cyrillic or Chinese) than the base version. Enable HTTP/2 or HTTP/3 for parallel downloads and use server-side caching via Redis or Varnish. Regularly test performance with tools like PageSpeed Insights or WebPageTest, separately for each language version. A loading time just 0.5 seconds slower can already lead to measurable revenue losses. Also consider mobile optimization: in many markets, users primarily browse on smartphones with slower connections. Speed up your multilingual website by compressing images, inlining critical CSS, and removing unnecessary scripts.
blog.faqT
Is there a maximum number of hreflang links per page?
Technically, there is no hard limit, but Google recommends not linking more than a few dozen variants per page. In practice, 5–10 language variants are often sufficient. For very many languages, consider a sitemap- or prefix-based structure to reduce the flood of links.
Do I need to provide a separate legal notice (Impressum) for each language?
Yes – provided you are doing business in a country subject to specific legal regulations. In Germany, you need an Impressum according to §5 TMG; in Austria, a similar one. Link the Impressum separately in each language version. A global page with only one Impressum can be subject to a cease-and-desist letter – this is not an SEO risk, but a legal one.
