---
title: "A multilingual real estate website that does not fall apart"
canonical: "https://en.prostor-agency.com/blog/multilingual-real-estate-website"
summary: "Three languages on one site sounds simple until Hebrew flips the layout and the Russian version misses half the forms. How we build multilingual property sites on one data core, shown on a residence in Israel."
publishedAt: "2026-07-28"
---

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 property sites in up to three languages, including
right-to-left ones, and the pattern that survives is always the same:
one data core, language views on top. Here is what that means in
practice, on a real project.

## One core, three faces

[Agada](/cases/agada) is a private residence in central Israel that
sells to three audiences at once: local Hebrew speakers, English
speaking buyers and the Russian speaking diaspora. Three separate
sites would mean three places where a price can be wrong. A single
"translated" site usually means Hebrew squeezed into a left-to-right
skeleton, and it shows.

So the site is built as one core of data (floor plans, prices,
statuses) with three language representations. When a unit is
reserved, it is reserved in every language at the same second. When a
price changes, nobody emails three webmasters.

The Hebrew version was designed right-to-left from the first sketch,
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 all of it exists in all three languages with the same depth. A
buyer who switched to Russian never hits a Hebrew error message halfway
through the money conversation.

The same logic applies in any market where buyers come from abroad.
We wrote earlier about [selling apartments to foreign buyers in Georgia](/blog/sell-apartments-foreign-buyers-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 not just words; the three Agada audiences ask different
questions in a different order. The local buyer knows the area and
goes straight to plans and terms. The relocating buyer needs the
context first: the town, the legal process, what happens remotely. So
the language versions share the core but can weight their accents
differently, and the structure allows it instead of forcing one
script on everyone.

This is worth deciding before design starts. It changes the brief
from "translate the site" to "serve three buyers", and the second
brief produces a different, better site for roughly the same money.

## The technical part, briefly

Every language is a full server-rendered 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 are 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](/services/real-estate). 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.