A developer selling internationally always asks for languages, and the request sounds trivial: add English, add Russian, maybe Hebrew or Arabic. Then the estimate arrives and it turns out "add" was the wrong verb. A language is not a coat of paint. It is a parallel version of every screen where money is discussed.
We have built a property site in three languages, including right-to-left Hebrew. What holds such a site together is one shared structure with a complete version for each language. Here is what that means in practice, on a real project.
One structure, three versions
Agada is a premium residential project in Tiberias, on the Sea of Galilee, that sells to three audiences at once: local Hebrew speakers, English-speaking buyers and the Russian-speaking diaspora. A single "translated" site usually means Hebrew squeezed into a left-to-right skeleton, and it shows.
So we built three versions on one structure and one visual language. The buyer's path, the composition and the presentation are the same; the language and the address change. The site runs on Tilda at three addresses: agadahome.com, agadaisrael.com and theagada.com. All three are equally complete. Separate addresses usually mean a change is made in each version. With live prices and statuses that stops working, and we would recommend one data core with language views on top, so an update lands everywhere at once.
The Hebrew version was built right-to-left rather than mirrored, with typography, composition and navigation thought through for a reader whose eye starts on the right. Mirroring an existing layout at the end of a project is the single most common RTL mistake, and it is visible to every native reader within seconds.
Translate the funnel, not just the brochure
Marketing pages get translated because they are visible. What decides whether the deal happens is the layer underneath: enquiry forms, validation errors, reservation statuses, the emails the site sends. On Agada we translated the forms and their states along with the copy, so a buyer reading in Russian does not hit a Hebrew message halfway through an enquiry.
The same logic applies in any market where buyers come from abroad. We wrote separately about selling apartments to foreign buyers in Georgia: most developer sites there have an English homepage and a local-language everything else, so the foreign buyer falls out exactly at the step where they wanted to act.
What each audience actually needs
Languages are more than words; audiences ask different questions in a different order. As a rule, a local buyer knows the area and goes straight to plans and terms, while a relocating buyer needs the context first: the town, the legal process, what happens remotely. On Agada all three audiences get the same path, so one site answers both kinds of question: the historic map and the location for those who need context first, plan cards and finishes for those who go straight to terms.
Decide who you are serving before design starts. It changes the brief from "translate the site" to "serve three buyers".
The technical part, briefly
Each language should be a full version with its own addresses and correct hreflang links, so Google and the AI crawlers see three complete sites, not one page with a JavaScript switcher. Fonts should be chosen once for all scripts, which sounds minor until a Hebrew headline renders in a fallback font next to a polished Latin one.
If you are planning a project that sells across languages, tell us about it. We will say honestly which languages need the full treatment, which can wait, and what that does to the budget. Reply within one business day.

