How to build a Hebrew and English website, the right way
Yeheli Sampson · · 3 min read
The short answer
Give each language its own pages and addresses (for example / for Hebrew and /en for English), set lang and dir on every page, connect the versions with hreflang tags, make the language switch lead to the same page in the other language, and write each language for its own audience instead of translating word for word.
In Tel Aviv many businesses have Hebrew-speaking and English-speaking customers: locals, new immigrants, tourists and international companies. A site in both languages opens the business to both audiences, but only if it is built right.
This guide covers the technical decisions and the writing, so each audience gets a site that looks and sounds as if it was written for them.
Step 1: A separate address for each language
Each language gets its own pages and its own addresses. The simplest structure is a folder for the second language:
example.co.il/ Hebrew
example.co.il/en English
example.co.il/services Hebrew services
example.co.il/en/services English servicesAn automatic translate button that swaps text on the same address is not enough. Google does not see it as a real English page, and the translation usually sounds machine-made.
Step 2: Truly right to left
On Hebrew pages, set the language and direction for the whole page:
<html lang="he" dir="rtl">
...
<html lang="en" dir="ltr">- The menu, arrows and directional icons flip
- Styles use logical properties (start and end) instead of left and right, so one design works both ways
- English words and numbers inside Hebrew text are checked so punctuation does not jump to the wrong side
- Phone numbers, emails and domains display left to right
Step 3: Connect the languages with hreflang
hreflang tags tell Google that these are two versions of the same page, so Hebrew searchers get the Hebrew page and English searchers get the English one. Put them on both versions:
<link rel="alternate" hreflang="he" href="https://example.co.il/services">
<link rel="alternate" hreflang="en" href="https://example.co.il/en/services">
<link rel="alternate" hreflang="x-default" href="https://example.co.il/services">Each version points to itself and to the other version. Each page also has a canonical tag pointing to its own address.
Step 4: A language switch that keeps your place
The language button should lead to the same page in the other language, not to the home page. Someone reading about a specific service who switches to English expects to keep reading about that service.
Do not redirect visitors automatically by location or browser language. Offer the language and let them choose.
Step 5: Write, don't translate
Each language is written for its own audience. The same message, in the words people actually use. A phrase that sounds natural in Hebrew can sound odd in English, and the other way round.
- Titles and descriptions for Google are written separately in each language
- Search terms differ between languages, so check each one on its own
- Local details, such as how to get there or what Florentin is, get more explanation in English
Step 6: Sitemap and Google profile
The sitemap lists pages in both languages, with the links between them. On your Google Business Profile, add the main site and mention in the description that you serve customers in English too.
Checks before launch
- Every Hebrew page displays right to left and every English page left to right
- The language switch leads to the same page in the other language
- Every page has a title and description in its own language
- hreflang and canonical tags are correct on both versions
- Forms, the WhatsApp button and all links work in both languages
Questions on this topic
Can I just add a translation plugin?
You can, but automatic translation usually sounds machine-made and does not always create pages Google recognises in the second language. Separate pages work better.
Which language should be the default?
The language most of your customers speak. For a business whose customers mostly speak Hebrew, Hebrew at the main address and English under /en.
Do I need to translate the whole site?
Not necessarily. Start with the important pages in the second language and add more as needed.