메인 콘텐츠로 이동

[KO] Multilingual Domains & International SEO: Domain Strategy for Global Sites

[KO] Domain architecture choices for multilingual sites, hreflang configuration, and international SEO best practices for optimal rankings across global search results

When your website serves multiple languages and regions, domain architecture directly affects how search engines understand and rank each language version. ccTLD, subdomain, or subdirectory? How to configure hreflang correctly? This guide answers these core international SEO questions.

Domain Architecture for International SEO

Three Main Approaches

Option 1: Country-Code TLDs (ccTLD)

example.de    → German version
example.fr    → French version
example.jp    → Japanese version

Option 2: Subdomains

de.example.com    → German version
fr.example.com    → French version
jp.example.com    → Japanese version

Option 3: Subdirectories

example.com/de/    → German version
example.com/fr/    → French version
example.com/jp/    → Japanese version

Detailed Comparison

DimensionccTLDSubdomainSubdirectory
Geo-targeting signalStrongestNeeds GSC setupNeeds GSC setup
SEO authorityIndependent per domainPartially independentShares main domain authority
Implementation costHighest (multiple domains)MediumLowest
Operational complexityHighMediumLow
Brand consistencyWeakerMediumStrongest
Best forLarge enterprises, multi-marketTechnical isolation needsMost situations (default choice)

Google’s Recommendation

Google officially states none of these approaches has an absolute SEO advantage. But the practical consensus:

  • For most sites: Subdirectories are optimal — shared authority, simple management
  • For large enterprises: ccTLDs provide stronger local trust signals in target markets
  • Subdomains: Unless technical isolation is required, typically not the best choice

hreflang Tag Configuration

What Is hreflang

hreflang is an HTML tag that tells search engines which language/region versions of a page exist and the URL for each.

Implementation Methods

HTML head tags (for smaller sites):

<link rel="alternate" hreflang="en" href="https://example.com/page" />
<link rel="alternate" hreflang="zh" href="https://example.com/zh/page" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />

XML Sitemap (for large sites):

<url>
  <loc>https://example.com/page</loc>
  <xhtml:link rel="alternate" hreflang="en" href="https://example.com/page"/>
  <xhtml:link rel="alternate" hreflang="zh" href="https://example.com/zh/page"/>
</url>

Common Configuration Errors

  1. Missing self-reference: Each page must include an hreflang tag pointing to itself
  2. Missing x-default: Always specify the default language version
  3. Asymmetric references: Page A references B, but B doesn’t reference A
  4. Wrong language codes: Using zh-CN vs zh-cn (case-sensitive in some contexts)
  5. Pointing to 404 pages: All hreflang URLs must be valid

Domain Impact on Local Search Rankings

ccTLD Local Ranking Advantage

ccTLDs have inherent advantages in target country search rankings:

  • Google treats ccTLDs as geo-targeting signals
  • Local users prefer clicking national domain results
  • Local backlinks are easier to acquire (local sites link more readily to local domains)

Setting Geo-Targeting in Google Search Console

If using gTLD (.com) + subdirectories/subdomains:

  1. Add each subdirectory/subdomain in GSC
  2. Set the target country for each version
  3. Submit separate sitemaps for each version

Multilingual Content Strategy

Translation vs. Localization

Translation: Converting content from one language to another Localization: Adapting content for the target market’s culture, habits, and needs

SEO best practice favors localization over simple translation:

  • Keywords have different search patterns across languages
  • The same topic has different popularity and focus points across markets
  • Localized content earns local backlinks more easily

URL Structure Best Practices

  • Use local-language URL slugs (e.g., /de/datenschutz not /de/privacy)
  • Keep URL structure consistent across language versions
  • Avoid mixing languages within URLs

Common Pitfalls

Auto-Redirect Trap

Automatically redirecting users based on IP or browser language:

Problems:

  • Search engine crawlers may be redirected to wrong versions
  • Traveling users get forced into non-native language versions
  • May affect indexing of multilingual versions

Recommendations:

  • Show a language selection banner instead of auto-redirecting
  • Ensure crawlers can access all language versions
  • Use x-default hreflang for the default version

Duplicate Content Issues

Multilingual sites easily create duplication:

  • Similar content across versions (e.g., UK vs US English) needs hreflang differentiation
  • Each language version should have its own canonical tag
  • Don’t create multilingual URLs without actual translation

Summary

Multilingual domain strategy is the foundation of international SEO. For most sites, the subdirectory approach (example.com/zh/) is optimal for authority sharing and management simplicity. Large enterprises can consider ccTLDs for stronger local signals. Regardless of approach, correct hreflang configuration is essential for search engines to understand multilingual relationships. Remember: localization beats simple translation, and user experience beats technical perfection.