Hebrew Content Writer
Instructions
Step 1: Identify Content Type and Register
| Content Type | Register | Audience | Key Characteristics |
|---|---|---|---|
| Legal / Government | Formal (gvoha) | Officials, lawyers | Passive voice, complex sentences, traditional gendering |
| Business / Corporate | Business | Professionals | Clear, professional, moderate formality |
| Marketing / Ads | Business-Casual | General public | Persuasive, benefit-focused, concise |
| UX / Interface | Direct | End users | Imperative mood, ultra-short, action-oriented |
| Social Media | Informal | Young adults | Casual, slang-friendly, emoji-compatible |
| Blog / Article | Business | Readers | Informative, SEO-aware, structured |
Step 2: Apply Hebrew Grammar Rules
Spelling Standard -- Use Ktiv Maleh (Full Spelling): Modern Hebrew content uses ktiv maleh (plene spelling) with vav and yod for vowels:
- Correct: תוכנה (tochnah) not תכנה
- Correct: שירות (sherut) not שרות
- Follow Academy of Hebrew Language guidelines
Smichut (Construct State) Rules:
- First noun loses definite article: "beit ha-sefer" (the school) not "ha-beit ha-sefer"
- First noun may change form: bayit -> beit, yom -> yom (unchanged)
- Adjectives agree with the LAST noun in the chain
Direct Object Marker (et):
- Required before definite direct objects: "ra'iti ET ha-sefer" (I saw the book)
- NOT used with indefinite objects: "ra'iti sefer" (I saw a book)
- Common mistake: omitting "et" or using it with indefinite objects
Subject-Verb Agreement:
- Verbs agree in gender and number with their subject
- Past tense: also agrees in person
- Present tense: only gender and number (no person distinction)
- Future tense: gender, number, and person
Step 3: Handle Gendered Language
Option A -- Traditional (default for formal/legal): Use masculine plural for mixed groups. Standard in government, legal, academic writing.
Option B -- Slash Notation (for business/marketing):
משתמשים/ות יקרים/ות (dear users, m/f)Option C -- Gender-Neutral Rewording (recommended for UX/tech):
| Instead of | Use |
|---|---|
| המשתמש צריך ללחוץ (the user needs to click, m.) | יש ללחוץ על (click on) |
| אתה יכול לבחור (you can choose, m.) | ניתן לבחור (it is possible to choose) |
| הלקוחות שלנו מרוצים (our customers are satisfied, m.) | שביעות רצון הלקוחות שלנו (the satisfaction of our customers) |
Ask the user which approach they prefer if not specified.
Step 4: Common Hebrew Writing Mistakes to Avoid
| Mistake | Wrong | Correct | Rule |
|---|---|---|---|
| Smichut with ha- on first noun | הבית הספר | בית הספר | Only second noun gets ha- |
| Missing et | ראיתי הכלב | ראיתי את הכלב | Definite direct object needs et |
| Wrong gender agreement | הילדה הלך | הילדה הלכה | Verb must match subject gender |
| Mixed ktiv | תוכנה/תכנה in same text | Pick one consistently | Use ktiv maleh throughout |
| Incorrect vav ha-hipukh | ואז הוא הולך | ואז הוא הלך | Vav ha-hipukh is biblical, not modern |
| Colloquial in formal text | נגיד ש... | לדוגמה... | Match register to context |
Step 5: Hebrew SEO Optimization
Keyword Strategy:
- Research keywords in Hebrew using Google Keyword Planner (region: Israel)
- Account for morphological variations -- target root words and common forms
- Example: "ביטוח" (insurance) also search "ביטוחים", "לבטח", "מבוטח"
- Consider bilingual searches -- Israelis search English for tech terms
On-Page SEO for Hebrew:
- Title tag: 50-60 Hebrew characters, primary keyword near beginning
- Meta description: 120-150 characters, compelling call-to-action
- H1: One per page, contains primary keyword
- URL slug: Transliterated Hebrew ("bituach-briut") or English equivalent
- Alt text: Descriptive Hebrew text for images
- Internal linking: Use Hebrew anchor text
Content Structure:
- Use short paragraphs (2-3 sentences) -- Hebrew text appears denser than English
- Use headers (H2, H3) every 200-300 words
- Bulleted lists improve readability in Hebrew
- Bold key terms for scanning
Examples
Example 1: Marketing Email
User says: "Write a Hebrew marketing email for a SaaS product launch" Result: Write business-register Hebrew email with compelling subject line, benefit-focused body, clear CTA. Apply SEO principles if it will be a web version. Use gender-inclusive language.
Example 2: UX Error Message
User says: "Write Hebrew error messages for a login form" Result: Write short, clear, action-oriented Hebrew text in imperative mood. Use neutral/inclusive phrasing. Examples: "הסיסמה שגויה. יש לנסות שנית" (The password is incorrect. Please try again).
Example 3: SEO Blog Post
User says: "Write a Hebrew blog post about cloud security for Israeli businesses" Result: Research Hebrew keywords, write structured article with proper H2/H3 hierarchy, include meta description, use ktiv maleh throughout, business register.
Example 4: Gender-Inclusive Rewrite
User says: "Make this Hebrew text gender-inclusive" Result: Identify gendered forms, apply Option C rewording where possible, use slash notation where rewording is awkward, maintain readability and register.
Bundled Resources
References
references/hebrew-grammar-quick-ref.md— Concise Hebrew grammar reference covering all 7 binyanim (verb patterns) with usage guidance by register, ktiv maleh vs. ktiv chaser spelling examples, common smichut (construct state) forms, and four gender-inclusive writing patterns with before/after examples. Consult when writing or editing Hebrew content and need to verify grammar rules, choose the correct register, or apply gender-neutral phrasing.
Gotchas
- Agents default to formal/literary Hebrew (safa gvoha) when writing marketing or UI text. Israeli users expect casual, conversational Hebrew. Use colloquial phrasing, not textbook Hebrew.
- Hebrew punctuation differs from English: the geresh (') and gershayim (") are used for abbreviations (e.g., tsahal) and acronyms, not for quotation. Agents may strip these or replace them with standard ASCII quotes.
- Agents tend to transliterate English idioms literally into Hebrew, producing unnatural text. "Think outside the box" does not translate directly; use native Hebrew expressions instead.
- Hebrew has grammatical gender that must agree between nouns, verbs, and adjectives. Agents often use masculine defaults even when addressing a female user or a feminine noun.
Reference Links
| Source | URL | What to Check |
|---|---|---|
| Academy of the Hebrew Language | https://hebrew-academy.org.il | Official spelling rules, loanword decisions, new terms |
| Milog online dictionary | https://milog.co.il | Modern Hebrew usage, register, common phrasing |
| Ravmilim online dictionary | https://www.ravmilim.co.il | Synonyms, collocations, grammatical info |
| Kotar HaKeshet | https://hebrew-academy.org.il/topic/hahlatot/ | Academy decisions on grammar and terminology |
| Hebrew style guide (Wikipedia) | https://he.wikipedia.org/wiki/ויקיפדיה:מדריך_הסגנון | Community-maintained modern Hebrew style conventions |
Troubleshooting
Error: "Text mixes formal and informal registers"
Cause: Inconsistent tone throughout the content Solution: Identify the target register at the start and apply it consistently. Common issue when multiple writers contribute or when translating from English.
Error: "SEO keywords don't match Hebrew search patterns"
Cause: Direct translation of English keywords to Hebrew Solution: Use Google Keyword Planner with Israel region. Hebrew search patterns differ from English -- Israelis may search differently than direct translations suggest.