OPERATING IN ISRAEL
Three things do not cross the border with you: the privacy law, the search results, and the message. Companies usually buy them from three separate vendors and discover, late, that the three answers do not fit together. I hold all three.
THE THREE
Each of these is normally a different vendor. Each one constrains the other two.
Israel's Privacy Protection Law Amendment 13 has been in force since August 2025, the regulator's grace period on appointments closed that October, and the final guidance landed in July 2026. The part that catches foreign groups is narrow and specific: the officer must be a natural person, available in Israel, and the Authority's guidance is explicit that fluency in foreign privacy frameworks does not substitute for working knowledge of Israeli law. An existing EU appointment does not transfer.
The full Amendment 13 service →Whatever authority your brand carries in English, it carries none in Hebrew. The queries are different, the competitors are local, and the answer is not a translation layer on the existing site. It is a separate body of content with its own entity graph, built for how people actually search here, which is the one thing a global team cannot produce from headquarters.
A topical map built before the first article →Positioning does not translate. The claim that lands in New York often reads as vague or evasive in Hebrew, and the proof points that carry weight elsewhere are not the ones that carry weight here. This is deciding what you are in this market, then writing it in a language you can build from, rather than handing a translator a deck.
How I named a category and won it →WHY ONE PERSON
The privacy answer decides what your product is allowed to collect. What it collects decides what you can honestly claim. What you claim is what search has to find. Split across a law firm, an agency and a consultancy, each one optimizes its own answer and nobody is responsible for whether they agree.
That is the failure this practice exists to prevent, and it is sharper here than anywhere, because a foreign company has no local instinct telling it something is off.
EVIDENCE
Every number below comes from the live property's own Search Console, not from an estimation tool.
Bar-Ilan
certified DPO, taking the role personally
#1 globally
for “narrative engineering”, a term I coined
3,462
organic impressions in a new property's first full month
41
silently de-indexed pages found and recovered for a client
The full case studies, including what was broken and what it took to fix, are here.
QUESTIONS
Generally not. Israel keeps its own database regime, its own definition of sensitive data and its own regulator, and the Authority's guidance addresses multinational groups directly: knowledge of foreign frameworks does not stand in for in-depth knowledge of Israeli privacy law, and the officer is expected to be available in Israel. Mapping a GDPR programme onto Israel gets you most of the way on principles and leaves the specifics exposed, which is where an inspection looks.
A local office is not what triggers the privacy obligation. If you run a product, a store, an app or an ad platform with Israeli users, the sensible assumption is that you are in scope until an assessment says otherwise. The search and message questions are commercial rather than legal, and they apply from the moment you want customers here.
For translation, often yes. For search, rarely, and the reason is structural rather than linguistic: ranking in Hebrew means competing against local publishers on local intent, in a right-to-left market with its own query habits, and it needs someone who reads the results the way a customer here reads them. A translated version of your English site is a different asset from a Hebrew presence.
Because these three are the same problem seen from three angles. The privacy answer constrains what your product may collect, what it collects shapes what you can honestly claim, and what you claim is what search has to find. Bought separately you get three correct answers that contradict each other, and nobody whose job it is to notice.
It starts with a paid assessment: where you actually stand on the legal obligation, what your Hebrew visibility is today, and whether your current message survives the crossing. That produces a written picture you keep, whether or not we work together afterwards. Anything ongoing is scoped and priced from there.
Hebrew and English, both natively enough to write in. That matters more than it sounds: the work here consists of decisions made in English with a client and executed in Hebrew for a market, and every handover between two people at that seam is where accuracy is lost.
Thirty minutes is usually enough to tell whether the privacy obligation applies to you, whether there is a Hebrew search position worth competing for, and whether your current message survives the crossing. It can also end with me saying there is no work here for me.