Built in your language. Not translated into it.
Set your brand’s language once — Hebrew, Arabic, French, or English — and everything follows: articles generate natively, the public blog flips to true RTL, and every date, label, and meta tag speaks your market’s language.
Your entire site,
Not an English site with translated posts — a publication that generates, renders, and describes itself in the language your market actually reads.
- Native generation, everywhere — Set your primary language once and every generator receives it automatically — articles, ideas, outlines, newsletters, social posts, voice guidelines, categories, and authors.
- True RTL, not a mirrored hack — Hebrew and Arabic flip the whole layout — direction, blockquotes, arrows — with dedicated fonts loaded automatically. RTL is treated as a property of the language, not a display toggle.
- A localized public blog — Navigation, labels, and section headings render in your language, and dates format to match — including an optional dual Gregorian + Hebrew calendar display.
- SEO metadata in your language — Every page carries the correct lang and dir attributes and Open Graph locale, and you choose between native-script URL slugs or concise AI-generated English ones.
- Newsletters that read right — When your site is Hebrew or Arabic, outgoing emails carry inline RTL direction and the matching font — applied in a way that survives Gmail, Apple Mail, and Outlook.
- Your theme, corrected for RTL — Built-in themes flip automatically. For custom CSS, a dedicated RTL overrides field injects your fixes scoped to RTL mode only — they never leak into LTR rendering.
What it looks at
- Content generation — Articles, outlines, newsletters, social posts, categories, and author voices are generated in your primary language from the start.
- Public blog — Layout direction, fonts, navigation strings, and date formats all follow the language setting automatically.
- Email — Newsletters inherit the site language, including RTL direction and fonts that hold up across major email clients.
- SEO metadata — lang and dir attributes, Open Graph locale, and your chosen slug format — native script or AI-generated English.
Translation is not localization.
English-first tools
- Content is written in English, then translated — and it reads that way
- RTL is a hack: mirrored layouts break, arrows point the wrong way, fonts don’t fit
- Blog navigation, dates, and labels stay in English around your “localized” articles
- Meta tags and page attributes still declare the site as English to search engines
- Your team fights the tool in every language but one
With Content Agents
- Articles, ideas, outlines, newsletters, social posts, categories, and author voices all generate natively in your primary language
- True RTL for Hebrew and Arabic — layout, blockquotes, arrows, and dedicated fonts, automatically
- All public blog strings and dates localized, with an optional Hebrew calendar display
- Correct lang and dir attributes and Open Graph locale on every page
- Your choice of native-script or AI-generated English URL slugs
How it works
- Pick your language — One setting: Hebrew, Arabic, French, or English. For RTL languages, choose your slug format and date format at the same time.
- Your public site follows — Layout direction, fonts, navigation strings, dates, and SEO metadata all switch together — no code, no translation files.
- Generate natively — Every generator on the platform reads the language setting and writes in it from the first word — no translate-after step.
Included in every plan.
Language support is a setting, not an upsell. RTL layout, localized strings, native generation, and per-language metadata come with every workspace.
Publish in your market’s language.
One setting, one release — and your whole site reads the way your audience does.
Frequently asked questions
How is this different from writing in English and translating?
Translated content reads translated — the idioms, sentence rhythm, and examples carry an English accent your readers notice immediately. Here the language setting reaches the generators themselves: the AI writes the article in Hebrew, Arabic, or French from the first word, and the site around it — navigation, dates, metadata, layout direction — matches. There is no English original and no translation step to manage.
What does setup look like?
One settings screen. Pick your language; for Hebrew or Arabic, also choose your URL slug format and date format. Save, publish a release, and your public blog renders in the chosen language — RTL layout, fonts, and translated strings included. No code, no translation files, no plugin.
Can one site publish in several languages at once?
No — and we say so plainly. The setting applies to the whole site: one brand, one language, done properly. That means full RTL, localized strings, and correct metadata rather than a half-working multi-locale setup. If you serve several markets, run a workspace per language. Per-locale URL variants on a single site are planned for a future release.
How does this affect SEO in our language?
Search engines see a site that is honestly declared: the correct lang and dir attributes, an Open Graph locale that matches the content, and — if you choose native-script slugs — URLs that carry your language’s keywords directly. Native Hebrew and Arabic URLs are indexed correctly by Google; if you prefer maximum compatibility, the AI generates a concise English slug from each title instead. The choice is yours, per site.
Does our team have to work in Hebrew or Arabic too?
No. The editor interface — writing tools, settings, analytics — stays in English regardless of the site language. Your team keeps a familiar working environment while everything the public sees, from the article body to the footer label, renders in your market’s language.