Israeli WordPress hosting where Hebrew search finds the word.
Hebrew is written without vowels most of the time, and optionally with them. The same word therefore has two spellings that share no matching characters in the middle.
Letters without vowels.
Hebrew orthography makes matching a harder problem than direction, which is the part everyone notices first.
Vowel points folded for matching
Text may carry niqqud or omit it entirely, and the two forms do not match as strings. Points are stripped for comparison while kept for display where they belong.
Final letter forms treated as the same letter
Five Hebrew letters change shape at the end of a word and are separate characters. Unfolded, a search matches only the occurrences where the word was not final.
A working week ending Thursday
Sunday is a working day and Friday afternoon is not, so business-day calculations and support expectations both shift.
Right-to-left with Latin mixed in
Hebrew text routinely contains Latin product names and numerals, which changes direction mid-sentence and needs resolving rather than guessing.
An origin in the region
Signed-in and checkout requests always reach the origin, and Israel is well served from within Asia.
Two spellings of one word.
A visitor searches a Hebrew word plainly visible on the page and gets nothing, because the page carries vowel points and their query does not, or the word fell at the end of a phrase.
- Vowel points folded for matching
- Final letter forms folded to their base letters
- Business-day logic using a Sunday-to-Thursday week
- Mixed-direction text resolved
Found without the vowels.
An Israeli site can answer a query in milliseconds and return nothing, because the query and the content are the same word written two legitimate ways.
What we change for Israeli sites
Hebrew matching is the distinguishing work; direction and the calendar follow behind it.
| Setting | What we do | Why |
|---|---|---|
| Vowel point folding | Niqqud stripped for comparison, retained for display | Hebrew is usually written without vowel points and sometimes with them, and the two forms of one word share no matching sequence in the middle. |
| Final letter folding | Word-final forms folded to their base letters | Five Hebrew letters take a different shape at the end of a word as separate codepoints, so unfolded search finds only non-final occurrences. |
| Business-day logic | Computed against a Sunday-to-Thursday week | Sunday is a working day here and Friday afternoon is not, so delivery estimates and service windows both land wrongly by default. |
| Bidirectional text | Mixed Hebrew and Latin runs resolved explicitly | Hebrew content routinely contains Latin names and numerals, and left to guess the browser places punctuation on the wrong side. |
| Origin region | Asia, close to the domestic audience | Cached pages are served locally regardless, but signed-in and checkout requests reach the origin. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why does Hebrew search miss words on the page?
Should I store Hebrew with or without niqqud?
Does the working week affect my site?
Is right-to-left the main Hebrew problem?
Match the word either way.
Move the site to an Asia origin - migration is free, search folding configured.