i18n roster

Languages we ship in

1 live, 1 staging, 15 planned. Status moves are operator-driven from /dashboard/seo/locales, no rigid quarter target; if editorial capacity in a market lands, the locale moves.

Tier 1, small-country leverage

  • Português (Brasil)pt-BR staging

    Brazilian Portuguese, Tier 1 · small-country leverage

    Large retail-FX population; thin English-content fit in Brazilian SERP; strong AI-search adoption.

  • Tiếng Việtvi planned

    Vietnamese, Tier 1 · small-country leverage

    Rising MT4/MT5 base; near-zero Tier-1 English saturation in the local SERP.

  • Bahasa Indonesiaid planned

    Indonesian, Tier 1 · small-country leverage

    Largest FX retail population in SEA; weak English content fit for rule queries.

  • Türkçetr planned

    Turkish, Tier 1 · small-country leverage

    Large scalping community; currency-volatility interest is a constant tailwind.

  • Español (México)es-MX planned

    Mexican Spanish (Latam base), Tier 1 · small-country leverage

    Largest Spanish-speaking prop population in the Americas; tone + USD-first differentiates from es-ES.

  • Español (Argentina)es-AR planned

    Argentine Spanish (RioPlate), Tier 1 · small-country leverage

    High-inflation environment drives prop interest; localised tone lands harder than generic Latam-Spanish.

  • Filipinofil planned

    Filipino, Tier 1 · small-country leverage

    OFW remittance + prop overlap; English-friendly so hybrid content can ship first.

Tier 2, mid-competition

  • Deutschde planned

    German (DACH), Tier 2 · mid-competition

    Strict trader population; high price tolerance; brand-language search dominant.

  • Françaisfr planned

    French (France + French-Canada), Tier 2 · mid-competition

    Mid-size population; French-language firm-rule content scarce.

  • Italianoit planned

    Italian, Tier 2 · mid-competition

    Smaller but high-conversion prop population.

  • Español (España)es-ES planned

    Castilian Spanish, Tier 2 · mid-competition

    Different from Latam in tone + commercial firm relevance.

  • Português (Portugal)pt-PT planned

    European Portuguese, Tier 2 · mid-competition

    Smaller market; converts well from pt-BR with light editorial pass.

Tier 3, premium markets

  • 日本語ja planned

    Japanese, Tier 3 · premium markets

    Premium content market; AI-search adoption strong; expensive to compete.

  • 한국어ko planned

    Korean, Tier 3 · premium markets

    High-conviction traders; strong domestic content needed.

  • हिन्दीhi planned

    Hindi, Tier 3 · premium markets

    Hybrid bilingual reality — Hindi pages support English ranking via backlinks.

  • العربيةar planned

    Arabic (MENA), Tier 3 · premium markets

    Large prop interest; RTL layout work required upfront.

Excluded, explicit and reasoned

  • 中文(中国大陆)zh-CN excluded

    Simplified Chinese (mainland), Canonical

    Regulatory + payment-rail risk for catalogue firms. Revisit when a supported firm formally accepts mainland customers.

  • Русскийru excluded

    Russian, Canonical

    Sanctions + ad-policy risk. Revisit when policy environment changes.

  • فارسیfa excluded

    Persian, Canonical

    Sanctions + ad-policy risk.

FAQ

How does a locale move from planned to live?
Five things happen, in order: (1) translator persona resolved + edit budget allocated, (2) status flips planned → staging, (3) per-cell + per-firm + per-tool pages translated and prerendered, (4) GSC service account delegated on the locale subpath + a binding row added to core.seo_property_bindings, (5) status flips staging → live, which un-suppresses the locale's meta robots, includes it in the sitemap index, and starts the hourly GSC/GA4 sync. The cockpit dashboard at /dashboard/seo/locales drives the flip with a confirmation dialog and a pre-flight delegation probe.
Why are some locales explicitly excluded?
Three categories: markets with restrictive financial-marketing regulation (we don't want to be flagged in jurisdictions where prop-trading promotion is heavily licensed), markets where the existing English coverage is already the leading source (translation would dilute, not multiply), and markets where the editor pool we trust is thin enough that quality risks outweigh reach. The rationale per row spells out which condition applies.
When do you expect Tier 1 to all be live?
pt-BR is staging today; expect live by mid-2026 pending editorial pass. Vietnamese, Indonesian, Turkish, Spanish-LatAm, and Filipino target Q3-Q4 2026 in roster order. Status flips are operator-driven from /dashboard/seo/locales, no rigid quarter target if editorial capacity moves.
Can I help translate a planned locale?
Yes. We work with bylined editorial personas, ex-prop-desk operators in each market, not anonymous freelance pools. If you fit the profile (verifiable trading-desk experience + native fluency + willing to sign per-page reviewedAt), email [email protected] with two paragraphs on a firm-rule topic of your choice.
How is the translation kept accurate to the firm rules?
Editorial law: firm names, calculator labels, and quantitative rule values (3% daily cap, 5% trailing DD, 15% consistency, etc.) are never translated, they're literal references to the firms' own published rule values. Loanwords (trader, scalper, EA, ICT, SMC, broker, slippage, stop-loss) stay English by convention because that's how the retail-FX community in each market writes them. Only the analytical prose is translated.

Last reviewed .