Keep your Hebrew and English offers in sync.

1. One record of the offer, with an owner.

Before anyone edits a page, write a short record per offer: name, what is included, what is excluded, the price in each currency, what recurs monthly, and the date it was last approved. One named person approves changes to it. Translators and designers should never have to guess whether an old number still stands.

A shekel price is a decision, not a conversion. Kinetiq's own prices show it: the audit is $2,500 in English and ₪7,500 in Hebrew, a landing page starts at $2,750 or ₪8,500, a launch site at $9,500 or ₪29,000. The ratio is not the same from one line to the next, because each figure was set as a round number for its market.

The test: ask two people on the team what the entry offer costs in each language, and where that number is written down. Two answers to the second question means you have two prices.

2. Every place the price is repeated.

The price card is the place everyone checks. The copies are where drift happens: FAQ answers, form options, page titles, search descriptions, share previews, the structured data search engines read, confirmation emails.

We found one on our own site. Until 1 October 2026 the Hebrew enquiry form offered the audit at $2,500, the English price, while the Hebrew page around it said ₪7,500. The page had been translated and the form option had not followed. The form now reads its label from the same source as the published prices.

The test: search each language version for every currency symbol and every price figure, including the page source. Any number that appears in only one of the two lists needs an explanation.

3. The whole enquiry journey, in one language.

Walk through each version as a customer would: open a service, read the offer, send an enquiry. Look at the parts a translator never sees: the required-field message, the error state, the success screen, the automatic reply, and the language of the first human answer.

If something exists in only one language, say so before the click. On the Hebrew version of ki-iq.com, the links to case studies carry the Hebrew for "in English", because the case studies are.

The test: send your own site an enquiry in Hebrew, leaving one required field empty the first time. Write down the language of every message you get back, up to the reply from a person.

4. A language switch that keeps the visitor's place.

Google's guidance for multilingual sites is to use "different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language", and to "avoid automatically redirecting users from one language version of a site to a different language version". Its reason: such redirects "could prevent users (and search engines) from viewing all the versions of your site."

A switch that drops a visitor from a service page onto the other language's homepage makes them start again. Where an equivalent page exists, link to it. Where none exists, say where the link goes.

The test: open a service page, switch language, and see whether you are still on that service. Then open the site in a private window with the browser set to the other language. If you are redirected without asking, fix that first.

5. Right-to-left, checked with real content.

Hebrew is more than right-aligned headings. W3C's guidance is to add dir="rtl" to the html tag when the whole document runs right to left, and to set dir="auto" on form fields so a field follows whatever the visitor types. Placeholder text hides the problems: they show up when Hebrew meets a Latin brand name, an email address, a phone number or a price.

The test: on a phone, type a Hebrew sentence that contains an English name and a price into your enquiry form. Check where the punctuation lands and whether the digits stay in order. Then tab through the page with a keyboard and see whether the order still makes sense.

6. Proof that means the same thing.

A result claim has to survive translation with its unit, its period and its source. Our SHER case study says the page brings Pinkas Group 3 to 5 leads a day, and the Hebrew version says leads a day as well. A shortened translation that said customers instead of leads would claim something nobody measured.

The test: put each claim from both versions side by side. For each, the number, the unit, the period and the source should match. If you cannot name the source in one language, remove the claim from both.

After every price change.

A launch review is out of date the first time an offer changes. Keep the list from check 2, the places each price is repeated, next to the offer record, and walk it in both languages each time a number moves. Have a second reader check the language the editor does not write in.

Where Kinetiq fits.

We run a site in English and Hebrew and keep its prices in one place: every page like this one reads its prices from the homepage copy, and the site will not build if a price it quotes is no longer stated there. Our one-week audit costs $2,500 (₪7,500 in Hebrew), ends with a prioritised fix list, and is credited in full if you go on to build. See every price in plain text, or a lead generation website from $2,750.