Tri-lingual site & cross-border market expansion
Agence Sofi places candidates with employers in North America and MENA. Their site made one pitch in one language to buyers who weigh different things in each market.
- Role
- Positioning, copy, build
- Client
- Agence Sofi (recruitment)
- Languages
- English, French, Arabic (RTL)
- Scope
- Positioning rewritten for each market
One site, two continents, one argument
A recruitment agency placing candidates across North America and the MENA region. They had real business on both sides and one website, in French.
The instinct in that situation is to add a language switcher and run the copy through a translator. It is cheap and fast, and it produces three sites that each work about as badly as the original, because the problem was never the vocabulary.
- A Montreal employer is buying speed and compliance: bilingual candidates, Quebec labour rules, someone who can start this month.
- A Gulf employer is buying mobility and logistics: visa handling, relocation, credential recognition across borders.
- A US employer is buying volume and reliability, and mostly wants to know why they should work with an agency headquartered somewhere else.
Those are three different objections. Rendering the same paragraph in three languages answers one of them at most.
What I built
Three parallel sites sharing one codebase and one design system, with the positioning written separately for each market and the structure allowed to differ where the argument differs.
Positioning per market
Each locale got its own headline, its own lead paragraph, its own set of proof points and its own call to action, written in that language from the start. The Arabic site leads with cross-border placement because that is what employers in the region are buying. The French site leads with Quebec compliance. A bilingual visitor comparing them would see three different pages, and that is intended.
Right-to-left layout
Arabic runs RTL, and doing that properly means the layout mirrors: the navigation, the reading order, the direction arrows point, which side a form label sits on. It is handled with CSS logical properties instead of a mirrored stylesheet, so one set of components serves both directions and there is no reversed copy of the design to maintain.
Search, separately, three times
Keyword research was done separately for each market, because the phrase a Montreal HR manager types and the phrase a Dubai HR manager types are not translations of each other. Each locale has its own metadata, its own internal linking and its own hreflang wiring so the three don’t compete with one another in search.
The part you’d be right to argue with
This is three times the content maintenance forever. Every new service page, every price change, every piece of proof now has to be written three times by people who can write it. An agency that can’t sustain that is better off with one good site and a clear note about which markets it serves.
- The shared build keeps the cost in the copy. Structure, components and styling are maintained once. What multiplies is the writing, which is the part that had to be bespoke anyway.
- Three languages in-house made it viable. I write all three, so this engagement didn’t carry a translation vendor, a review cycle or the round trip where a translator asks what a sentence means and the answer arrives a week later.
What I haven’t solved
Keeping three arguments in sync as the business changes. A year on, a positioning shift means three rewrites and somebody has to notice that the Arabic page is still making last year’s promise. I don’t have a process that catches that automatically, only a calendar reminder, which isn’t a real solution.