SEO Nɔvi 10: Multi-language SEO

Eyi ne Nɔvi 10 le 13-Nɔvi SEO Nɔvi. Multi-language SEO ma wòanya akɔ yina bɔkɔ a wògblɔ dɔwɔ fa ma kɔkɔe nyui — ne nyuie, edzi ta wɔ duplicate content chaos.

Mɔ kɔkɔe kɔkɔe wòde si nɛ wo nyui ti hadzro nɔvi. Wɔ site a ɛwɔ 50 pages le kɔkɔe gɔ̃ ne nyui kɔkɔe 50 indexable URLs. Fa 5 kɔkɔe kɔlɔ, nà edin yɛ 250. Fa 20 kɔkɔe kɔlɔ, nà edin yɛ 1,000. Kɔkɔe nyui tsɔ ɖe nyui ɖe nɛ ƒe Google nsɛm nu.

Ná multi-language SEO ne wòle nu ló sɔsɔ abɔda mɔ wo SEO. Dzi nam vie ɖe nɛ duplicate content, ranking dilution, kple crawl budget waste. Le nu si le anɔ mɔ mɔ le lkɔkɔe kᴐ do, ɔbɔ na 10x traffic fԑ.

LANGR tɔ bwe 108 kɔkɔe le 89 mu ɔdɔwɔ hiplɔ — mèwɔ dɔwɔ le dzifɔdɔ. Eyi le nɔvi le akɔ nyuie, wòma ɛa tafialɔ yi nɔvi.

Ne ́Multi-language SEO ne

Multi-language SEO de 8 abɔdas a ɛho hia:

Hreflang Implementation — Kɔkɔe ma Google nɔ na ewi tɔ ne nyui ɖe nyikita
Locale Routing Strategies — Subdomain vs subfolder vs TLD
Translation Quality — Machine vs human vs hybrid translation
International Targeting — Search Console configuration
Content Localization — Aɖe nyingbe: kɔǵɛ nɔvi
RTL Support — Mɔ-nɔ nɔvi (Arabic, Hebrew, Farsi)
Language Detection — Kɔ tɔ wɔ wòle aɖe mɔ nsɛm a nɔ eya
Duplicate Content — Yi kɔn mɔ kpɔ akɔwɔ bɔ fonɔ

1. Hreflang Implementation

Hreflang tags kɔ kɔkɔe wu so eshɔ ewi nɛ ne nyui kɔ ewo aɖɔ. Wɔ ne nɔvi hia nu ɖe multi-language SEO — kple ne nyuie a enyu hia bɔ abɔ nɔvi.

Basic hreflang syntax:

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

Abɔda hia:

Mɔ kɔkɔe si nɛ wogbe nɛ ALL alternate versions (kple ye)
x-default yɔne fo nɛnni (ɛnyɛ English anaa ɔlɔ gɔ)
Hreflang tags yebɔ reciprocal (page A kɔ B, B kɔ nɛ A)
Fa ISO 639-1 kɔkɔe codes (en, da, de) nyɛ kɔkɔe codes
Fɔ region-specific content: en-us, en-gb, pt-br (language-region)
Maximum ~50 hreflang entries le page (performance limit)

Awo placement options:

| Method | Best For | Drawbacks | |--------|----------|-----------| | le | Small sites (< 10 languages) | Bloat HTML, slower parsing | | HTTP headers | Non-HTML files (PDFs, APIs) | Nyɛ ka wosi fɔ | | XML sitemap | Large sites (10+ languages) | Slower discovery by crawlers |

Sitemap hreflang example:

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

Eyi yɛ hreflang akɔyɛ:

Wɔ na ɛbɔ self-referencing tag (page nyi si no so)
Non-reciprocal tags (A wɔ B, anaa B nnɔ A)
Kɔɔ kɔkɔe codes (dk sɛ da le Danish)
Kɔ duka non-200 URLs (redirects, 404s)
Mixing x-default kple language-specific page

Nokware amenu: Crawl nɛ site kple export all hreflang tags. Bɔ nɛ non-reciprocal relationships — eyi ne abɔda a ɛyɛ mmerɛw na ɛyɛ ɔkwanom Google anaa wɔ hreflang setup.

2. Locale Routing Strategies

Eyi ne woyɛ a bɔ URL fa ne kɔkɔe fɔ a ɛyɛ na ebi nɔ wo SEO, user experience, kple technical complexity. Ewo mfonini mmiɛnsa:

Subfolder (Bɔ au mu)

example.com/en/page
example.com/da/page
example.com/de/page

Pros: Single domain authority, eyɛ bɔ a nɔhi, SSL certificate baako, analytics property baako, Search Console property baako, ɛyɛ dɛm a ɛda so.

Cons: Less geo-targeting signal na ccTLDs.

Subdomain

en.example.com/page
da.example.com/page
de.example.com/page

Pros: Wɔ hɔ nɔha nɔlu ahorɔsɔn de bere do, kɔ separate crawl budgets.

Cons: Subdomain biara bɔ mɔgre na (link equity ankyɛ a, multiple Search Console properties, more complex setup.

Country-code TLD (ccTLD)

example.com (English)
example.dk (Danish)
example.de (German)

Pros: Strongest geo-targeting signal, wòda ne TLD a local, domain biara ne mu nyɛda.

Cons: Baako a wɔyɛ (buying 20+ domains), separate authority per domain, complex link building, separate analytics/console.

Yɛn bɔ mu: Subfolder routing fa 90% si hɔ. Wɔ bɔ all link authority le single domain na yɛ tu clear locale signals. Use /{locale}/page format.

https://langr.org/page        (English, default)
https://langr.org/da/page     (Danish)
https://langr.org/de/page     (German)
https://langr.org/ja/page     (Japanese)

Nokware amenu: Sɛ wonyɛ subdomains na ɔhɔ authority no, kɔ so fa ma subfolders. Sites a ɔtu fi subdomains kɔ subfolders yare 20-50% organic traffic increase le 3-6 months a link equity bɔ mu.

3. Translation Quality vs Machine Translation

Translation quality na ɛda so ma ranking. Google bɛtumi akasɛm nɛ machine translation kple nɔlia nsɛm a nkɔtɔ asɛm. Nanso 2026 AI translation ne ho da ho ntɔtɔ so sen rule-of-thumb fi 2020.

Ne translation quality spectrum:

| Level | Method | Quality | Cost | Best For | |-------|--------|---------|------|----------| | 1 | Raw GPT/DeepL output | 60-75% | ~$0 | Internal use, drafts | | 2 | AI + post-editing prompts | 75-90% | ~$0 | Blog content, non-critical pages | | 3 | AI + human review | 90-97% | $0.03-0.08/word | Product pages, key landing pages | | 4 | Professional native translator | 97-100% | $0.10-0.25/word | Legal, medical, brand-critical |

Nokware yiedie wɔ 2026: Level 2 (AI kple quality prompts) ne nɔhɔ fa bungwa si wopɛ. Google's duplicate content algorithms mma nyɛ penalize machine translation a wɔyɛ a kyau, mma penalize bobɔ a wɔyɛma nu anaa.

Signs of translation a ɛfrɛ SEO:

Untranslated segments a wɔbɔ mixed kɔkɔe
UI elements (buttons, labels) a still le source language
Locale-specific formatting a yenya adaption (dates, currencies, phone numbers)
Cultural references a nyɛ translation (idioms, jokes, examples)
Same meta title/description le all languages

Ne ordɔ sɛ yɛbɛcheck translation quality:

Sɛ ALL visible text ne translated (fidɔ navigation, footer, forms)
Verify locale-specific formatting (DD/MM/YYYY vs MM/DD/YYYY)
Test CTAs — ɛyɛ dɛm wɔ target language nɔ?
Check meta tags — title kple description ne nsɛm a na le language baako
Verify no raw i18n keys ne si yelɔ (e.g., nav.home anaa "Home")

Nokware amenu: Check nɛ translated pages na mixed-language content. Sɛ ebia buttons, labels, anaa UI elements no wɔ source language a, fa no mu — mixed-language pages kasa low quality sɛ Google.

4. International Targeting le Search Console

Google Search Console international targeting a yi nɔma Google pɛ a bɔkɔ ne pages a ɛsɔ no kɔ a nsɛm.

Fa subfolder setups:

Wɔn da country targeting pɛ subfolder (nsa a wɔ pɛ domain/subdomain)
Nea ɛda hɔ, rely on hreflang + content language + user signals
Submit a per-locale sitemap: sitemap-en.xml, sitemap-da.xml

Fa ccTLDs:

.dk ne ɛda hɔ ayɛ Denmark
.de ne ɛda hɔ ayɛ Germany
Nyɛ manual configuration hia

Fa generic TLDs (.com, .org, .net):

Set "International Targeting" pɛ property le Search Console
Fa hreflang yɛ primary signal

Practical steps:

Verify nɛ site le Search Console (baako property fa subfolder setup)
Submit nɛ sitemap a ɛma hreflang annotations
Check "International Targeting" report fa errors
Monitor "Coverage" report pɛ language (fa URL parameter filtering)
Check for "Duplicate without user-selected canonical" warnings — eyi tumi da hreflang problems ho.

Nokware amenu: Kɔ Search Console > Performance > Filter by country. Check sɛ users wɔ Germany yɛ padɛ English pages wɔ German mu. Sɛ ɛyɛ a, nɛ hreflang configuration nɔ errors.

5. Content Localization (Nyɛ Translation Nko)

Localization fa sɛ ɔbɔkɔ a ne ho na ɛyɛankɔ a. Edi nɔvi ma kɔkɔe ne localized nhu kple market-specific nue.

Ne sɛ lokolohiya no:

Currency kple pricing: Kɔ local currency (€ le Germany, kr le Denmark, ¥ le Japan)
Date/time formats: 25/06/2026 (EU) vs 06/25/2026 (US) vs 2026/06/25 (ISO/Japan)
Phone numbers: Local format kple country code for international
Addresses: Match local postal format
Social proof: Local customer names, local companies, local case studies
CTAs: Adapting tone (formal le German/Japanese, casual le English/Danish)
Images: Localize text le images, use culturally appropriate visuals
Legal: GDPR fa EU, different cookie consent requirements fa country
Examples: Local brands, local websites, local references

Content a mmɛn mu nyɛ direct translation:

Blog posts a wɔfa local topics (write unique fa market)
Case studies (use local businesses)
Pricing pages (different pricing fa market no yɛ valid)
News content (regional relevance nhyehyɛ).

Keyword localization: Nni fie keyword a wɔ ma nneyɛ fa nɛmu nɛ yɛ native. "Car insurance" le English, yɛ "bilforsikring" le Danish, nanso search volume leader a yɛ "forsikring bil" (different word order). Use local keyword research tools.

Nokware amenu: Check nɛ pricing page le all languages. Ɛda hɔ a ɛne kɔ local currency? Ɛda hɔ a CTAs yɛ culturally appropriate? A "Get Started Free" CTA tumi yɛ "Jetzt kostenlos testen" le German — ɛnyɛ literal translation, nɔ hɔn a German users a wɔyɛ pɛ sɛ wɔhwɛ.

6. RTL Support

Right-to-left languages (Arabic, Hebrew, Farsi/Persian, Urdu, Pashto) pɛ layout a nkɔda ho. Kɔ nɔ RTL content kple left-to-right layout ma site no yɛ unusable fa ~500 million native speakers.

Technical implementation:

<!-- Detect and apply direction -->
<html lang="ar" dir="rtl">

Ne a ɔbɛda so wɔ RTL:

Text alignment (right-aligned body text)
Layout direction (sidebars yi fi left to right)
Navigation order (reversed)
Icons a wɔyɛ directional meaning (arrows, progress bars)
Padding kple margin (swap left/right values)
Border radius (swap corner values)
CSS flexbox/grid direction

Ne a mmɛn da so:

Phone numbers kple mathematical expressions
Left-to-right brand names kple logos
Audio/video player controls
Horizontal scroll indicators
Embedded code blocks

CSS approach (modern):

/* Use logical properties */
.card {
  margin-inline-start: 1rem;  /* replaces margin-left */
  padding-inline-end: 0.5rem; /* replaces padding-right */
  border-start-start-radius: 8px; /* top-left le LTR, top-right le RTL */
}

Testing RTL:

Fa dir="rtl" kɔ kple hwehwɛ every page
Verify Arabic/Hebrew text yɛ readable (nyɛ garbled Unicode)
Test form inputs (text entry direction)
Check sɛ numbers display correctly kple RTL text mu

Nokware amenu: Sɛ wonyɛ Arabic ana Hebrew, fa dir="rtl" kɔ wo HTML element fa ne locale kple hwehwɛ CSS logical properties (margin-inline-start n’asɛm margin-left). Eyi pɛ baako na ɛbɛyɛ 80% RTL layout issues pɛ.

7. Language Detection kple Routing

Nea wopɛ sɛ ɔda kɔkɔe version a ɔda ho da no nyɛ wɔ UX kple SEO.

Best practice: URL-based kple preference cookie

First visit: Kɔ nkɔfa content fi URL (e.g., /da/page = Danish)
Root URL (/): Redirect fi Accept-Language header ANAA de yɛ default (English)
Manual switch: Sɛ user pɛ language, set a cookie na respect no fa future visits
Never: Auto-redirect fi language-specific URL

Ne a mmɛn fa:

IP-based redirects (Google crawls fi US IPs → only indexes English)
JavaScript-only language detection (search engines mfa JS kɔda ho na ɛhyɛ)
Redirecting /de/page to /en/page fa English users (yata hreflang)
Cloaking (showing different content a ɛda ho fa user-agent)

Correct redirect behavior:

User visits: /             → 302 redirect to /{detected-locale}/
User visits: /da/page      → Serve Danish content (never redirect away)
User visits: /nonexistent  → 404 (nsɛm nyɛ redirect to default language)

SEO-critical rule: Every language URL must be directamente accessible by Googlebot without redirects. Sɛ Google crawls /da/page na ɛda a ɔde redirectwɔ /en/page, bɛkɔ naa ɔnni nsa a ɔda Danish content.

Nokware amenu: Verify nɛ Googlebot bɛtumi kɔ all language URLs directly. Le Search Console, use nɛ URL Inspection tool le non-English URL. Sɛ ebu na ɛda redirect, fa mu nno.

8. Duplicate Content Across Languages

Multi-language sites fa unique duplicate content challenge — similar pages le different languages pɛ tumi pe ne ho mmɔ a ɛda ho nsɛm.

Sɛ duplicate content bɛyɛ a ɔfrɛ:

Pages a wɔyɛ 90%+ identical le languages (untranslated content)
Same URL accessible le ne kɔkɔe nansu neɖe prefix (/page kple /en/page)
Missing canonical tags allowing bɔ versions a wɔkyerɛ dɛ index no
Hreflang errors a ɔma Google pɔ na "wrong" version

Solutions:

| Problem | Solution | |---------|----------| | Untranslated pages | Fa noindex kɔ whenever translated, ana yɛ English kple clear language indicator | | Double URLs (/page + /en/page) | 301 redirect one to the other | | Google indexing wrong language | Fix hreflang reciprocity, verify le Search Console | | Low-quality translations indexed | Improve translation quality ana consolidated le fewer languages |

Canonical tag strategy:

<!-- Each language page ne own canonical -->
<!-- /en/page -->
<link rel="canonical" href="https://example.com/en/page" />

<!-- /da/page -->
<link rel="canonical" href="https://example.com/da/page" />

Nhyira nsɛm a canonical firi language kɔ ɔbɔkɔe kɔ no (e.g., Danish canonical pointing to English) — eyi ka Google bɛtumi anke Danish version mu.

Nokware amenu: Search site:yourdomain.com "your page title" le Google. Sɛ ebu na woyɛ mmoa English kple translated versions a woyi fa same query, wo yɛ duplicate content anaa hreflang issue.

Ne ́Multi-language SEO Checklist

Twi hɔ fa internationalized site no:

[ ] Hreflang tags le all pages, kple self-referencing kple x-default
[ ] All hreflang relationships ne reciprocal (checked le crawler)
[ ] Correct locale routing (subfolder recommended): /{locale}/page
[ ] No automatic redirects fi language-specific URLs
[ ] Translation quality validated (no mixed-language pages)
[ ] Meta title kple description unique pɛ language (nyɛ duplicated)
[ ] Currency, dates, kple formats localized pɛ market
[ ] RTL support implemented le Arabic/Hebrew/Farsi (sɛ ɛyɛ hia)
[ ] Per-locale sitemap submitted le Search Console
[ ] Each language page ne own canonical URL (nyɛ pointing kɔ other language)
[ ] No raw i18n keys visible le any page
[ ] Language switcher accessible le all pages (linked kɔ equivalent pages, nyɛ homepage)

Ne ́LANGR Checks Multi-language SEO

LANGR wòwɔ modules abien si wopɛ multi-language SEO:

i18n-checker: Crawls up to 5 locale variants le your pages kple bɔ:

Hreflang tag completeness kple reciprocity
Inaccessible locale URLs (returning 404 ana redirecting)
Hardcoded/untranslated strings across locales (fallback detection)
Raw i18n keys exposed as visible text
Translation coverage percentage

Translation scanner: AI-powered quality assessment:

Evaluates translation naturalness le 0-100 scale
Detects machine translation artifacts
Identifies untranslated segments le otherwise translated pages
Checks UI elements (buttons, labels, navigation) separate fi body content

Fa mu, yi modules bɔ yɛ multi-language implementation fi technical (hreflang, routing, canonicals) kple quality (translation, localization) nsɛm — abien a LANGR's 13 SEO disciplines.

Abɔda Foforɔ a Multi-language Mistakes (Ranked fa Impact)

Non-reciprocal hreflang — Google bɛtumi anka setup no mmerɛ mae
Auto-redirecting based on IP — Ma Googlebot mfa non-English versions
Same meta tags across languages — Wastes ranking potential le translated pages
Mixed-language pages — Buttons in English, content le German = low quality signal
No x-default — Google ntumi mfa wo fallback version
Translating URLs literally — /about-us → /uber-uns ne fine, nanso kɔ so consistent
Ignoring RTL — Broken layout fa 500M+ native speakers
Canonical pointing to another language — Kɛtɛ translation version le Google's index.

Ne ́Bɛyɛ?

Nɔvi 11: B2B Lead Discovery — Ne to SEO data a yɛ qualified leads kple automated prospecting, domain-based lead scoring, kple outreach powered by SEO findings.

Eyi ne nɔvi kɔtɔ a ɛda LANGR's 13-nɔvi SEO series. Run a free audit sɛnea ɛda wo site hɔ hɔ fa all 13 disciplines.

SEO Nɔvi 10: Multi-language SEO — Fia Kɔkɔe Kɔtɔ Yɔ Bubu Na Mɔ Nya Ʋe ŋgɔ