An Israeli developer selling only to local buyers can get away with a site that leans on a sales office: come in, we will walk you through the plans. A developer selling to buyers in New York, London or the diaspora more broadly does not have that option. The buyer will not drive to the office. Everything the office would normally explain in person has to live on the site instead.
We build sites for Israeli developers, including for buyers abroad, and the same gap shows up on most sites we review: the Hebrew market is served properly, and the English version is an afterthought bolted on top of it.
Hebrew is not a template that gets mirrored
The starting mistake is treating Hebrew as a settings toggle on an English site: flip the direction, keep the layout. Right-to-left is a design decision, not a CSS property. Navigation, forms, tables, unit numbers, floor plans and any line that mixes Hebrew and Latin characters (a project name, a phone number, a price in dollars) all need deliberate handling. A layout that only works left to right and gets algorithmically flipped breaks in exactly these places, and it breaks first for the audience the developer cares most about locally.
The same logic runs the other way. An English version that is a machine translation of Hebrew marketing copy reads like one: the idioms are wrong, the tone is off, and a buyer doing due diligence from abroad notices immediately. Both versions need their own copy, written for their own reader, on top of shared unit data.
What a remote buyer actually needs
A buyer who will not walk the model apartment needs the model apartment on the screen instead: a specific unit with its floor, plan, orientation, price and status, not a PDF brochure of the whole project. They need the numbers that a local buyer would ask the sales agent directly, published rather than gated behind a form. And they need a way to talk to someone that does not depend on being awake during Tel Aviv office hours: a booking link for a video call, a WhatsApp line, a reservation form that reaches the CRM with the unit attached rather than a generic "someone will call you."
None of this replaces the sales team. It removes the friction that stops a buyer eight time zones away from ever reaching them.
Trust signals for someone who cannot check the site in person
A local buyer can drive past the construction site. A buyer in London cannot, so the site has to carry proof that would otherwise come from being there: progress photos with real dates, permits and legal status explained in plain language rather than legal Hebrew, the developer's completed projects, a team with names and faces rather than a stock photo of a handshake. Every one of these that is missing reads as a reason not to trust the deal, and a buyer weighing a purchase from another country weighs that risk more heavily than a local one would.
What this looks like in practice
We have built sites for Israeli developers on exactly this brief: one project selling to buyers in the United States needed presentation materials and a website that worked for an audience that would never see the building before signing. Another, a private residence, needed Hebrew, English and Russian served from the same data so that a unit's price and status could not drift between languages. The pattern in both cases was the same: decide what the English-speaking buyer needs to see without ever visiting, then build the site around that, rather than translating a Hebrew site after the fact.
Where to start
If you are selling to buyers who will not walk into the sales office, audit your current site as one of them would: from a search result or an ad to a specific unit and a reservation, in English, without calling anyone. Note where that path breaks.
We build sites for this exact situation, from a project landing page to a full multilingual sales site. See how we approach real estate sites generally, or how we work with developers in Israel specifically.
