Language roadmap

English first, then controlled translations for priority countries.

Browser auto-translation is useful, but controlled translations are better for trust, payment wording, disclaimers, and search ranking.

Why not rely only on Chrome translation?

Chrome, Safari, and messaging apps may translate English pages automatically. That helps visitors understand the basics, but it does not give us control over legal disclaimers, payment copy, document upload instructions, or SEO.

The safer approach is to keep English as the source version, then translate reviewed page copy into separate language routes after the core flow is stable.

Initial language priority.

Russian

Strong bridge language for Central Asia, Caucasus, Ukraine, and Russian-speaking applicants.

Uzbek, Kyrgyz, Kazakh, Tajik

High-priority Central Asian languages based on applicant demand and likely customer fit.

Turkish

Useful for Turkey and parts of the broader regional audience where DV interest is active.

Arabic and French

Later expansion candidates for North Africa and African DV markets after the first translation set is stable.

First country SEO pages are live in English.

The first country-specific SEO batch focuses on Central Asian applicants. These pages are English source pages, not full translated language routes yet.

Each page should have its own title, description, FAQ block, internal links, and later hreflang tags when translations are ready. That is how we move beyond one generic homepage.