Multilingual Websites — The Complete Guide for Kurdish, Persian and English Markets

If your business operates in the Kurdistan region, your customers probably think in three languages: Kurdish, Persian and maybe English. A single-language site loses a big share of potential customers. But a properly built multilingual site strengthens SEO — it doesn't dilute it.

Three approaches — and why one wins

Approach 1: Translation widget (like Google Translate)

• ❌ Machine content with costly errors (especially Kurdish)
• ❌ Search engines don't index translated versions
• ❌ Users feel "translated," not respected
• ✅ One legitimate use: as a temporary aid

Approach 2: Parameter or cookie (?lang=fa)

• ❌ Unstable, duplicate URLs
• ❌ Complex canonical and hreflang
• ❓ A weak SEO option

Approach 3: Separate directory per language ✅ (industry standard)

example.com/        → Kurdish (primary language)
example.com/fa/     → Persian
example.com/en/     → English

• ✅ Each language has a stable, indexable URL
• ✅ Simple, correct hreflang
• ✅ Users can bookmark and share their language's link
• ✅ Analytics sees each language separately

Separate domains (fa.example.com) also work, but for most regional businesses a directory is simpler and sufficient.

hreflang — the connecting bolts between languages

Every page must tell Google where its "siblings" are:

<link rel="alternate" hreflang="ckb" href="https://kurdnet.co/">
<link rel="alternate" hreflang="fa" href="https://kurdnet.co/fa/">
<link rel="alternate" hreflang="en" href="https://kurdnet.co/en/">
<link rel="alternate" hreflang="x-default" href="https://kurdnet.co/">

Vital rules:

• All three must link to each other (reciprocal) — one-way is forbidden
• Each page's canonical points to itself
• x-default for users without a defined language

RTL — beyond mirroring

Persian and Kurdish are right-to-left. Real RTL design means:

• Starting the design in RTL — not converting a finished LTR layout
• Proper fonts: Vazirmatn for Persian/Kurdish, Inter for English
• Numbers and dates: decide Persian or Latin digits and stay consistent
• Forms: text fields, email and phone are usually LTR inside an RTL page (with dir="ltr")

Translation — three quality levels

Level 1: Raw machine ❌

Especially Sorani Kurdish — translation models still make serious errors. Don't burn customer trust.

Level 2: Machine + human editing ✅

Fast and affordable for English.

Level 3: Native writing ✅✅

A writer who thinks in that language. For Sorani Kurdish, this is the only acceptable option — and for key sales pages too.

Rule: high-selling pages = native; low-traffic pages = edited machine translation.

Multilingual content strategy

• Don't translate everything: 20 good native articles beat 60 machine ones
• Page priority: home → services → contact → 10 key articles → the rest
• Each language has its own keywords: Persian and Kurdish search behavior differs — do separate research

Multilingual SEO — checklist

• [ ] Each language in Search Console with separate geo targeting (if needed)
• [ ] Sitemap covering all languages
• [ ] Correct, reciprocal hreflang tags
• [ ] Title and meta description in the page's own language
• [ ] Language switcher in each language's own name ("فارسی" not "Persian" in the Persian version)
• [ ] Conversion tracking: each language has its own rate — analyze separately

Practical challenges we've seen

• Contact forms: names may contain any script — don't validate names against English patterns
• Dates: multiple calendars — clearly state which one
• Phone numbers: accept regional formats (don't over-validate)
• Web fonts: each language adds file weight — only the needed weights

Wrap-up

A multilingual site = separate directories + correct hreflang + native content + real RTL. For the Kurdistan market, this isn't just technique — it's respect for the customer.

The Kurdnet site is built with exactly this architecture (Kurdish at the root, Persian and English in directories) — test it right now.