Build a Multilingual Website Without Plugins in Ravix: 10 Languages, RTL and SEO Built In
A step-by-step guide to building a bilingual or multilingual website with Ravix CMS and no plugins: 10 ready languages, automatic right-to-left and calendars, a separate URL per l…

On this page
In WordPress, a multilingual site means buying or installing a separate plugin, extra configuration and one more layer to keep updated and secure. In Ravix, multilingual support is part of the system itself: from day one, with no plugin at all.
The very site you're reading this on is built with Ravix in 10 languages.
What does multilingual mean in Ravix?
- The interface ships in 10 languages: English, Persian, Arabic, Turkish, Spanish, French, German, Russian, Portuguese (Brazil) and Chinese. The admin panel, default theme, emails and error messages are all translated.
- You write content for each language yourself. Every post and page has a "language" field. Ravix deliberately doesn't replace your text with machine translation, because automatic translation usually hurts both quality and SEO.
- Every language gets its own address: for example
/en/blog/for English and/fa/blog/for Persian.
Step by step: building a multilingual site
- Choose the default language. In "Site settings", set the default language. Visitors who open an address without a language prefix are sent to this language.
- Keep "Show each post and page only in its own language" switched on. It's on by default for new sites. With it, each language's home page, blog, categories, tags, search, RSS feed and sitemap show only content in that language.
- Create a separate post for each language. In the post form, pick the "language" and give each language its own slug, for example
about-usfor English anddarbare-mafor Persian. Slugs are unique across the whole site. - The language switcher is ready. The default theme includes a language menu. The visitor's choice is saved in a cookie, so they see the same language next time.
- Build your menu. If a menu links to a page in another language, Ravix opens it with that language's correct prefix automatically.
Multilingual SEO, automatically
- Home, blog, category and tag pages get hreflang and x-default tags automatically, so Google knows which version is for which language.
- A sitemap (sitemap.xml) is built for each language, and one index connects them all. You only need to submit that one address in Search Console.
- If a post is opened with the wrong language prefix, it's redirected (301) to the right address, so no duplicate content is created.
- For every post you write a separate SEO title and description in its own language.
Right-to-left, calendars and fonts, with no setup
- Text direction is automatic: Persian and Arabic run right to left, every other language left to right.
- The Persian (Jalali) calendar and Persian digits are used only for Persian; other languages get Gregorian dates and Latin digits.
- The right font for each script: Vazirmatn for Persian and Arabic, Inter for Latin and Cyrillic, and a suitable system font for Chinese.
- Emails are sent in the recipient's language, not the site admin's.
For theme and plugin developers
- A theme needs only a simple JSON file per language for translations (
locale/de.json); no compiling or extra tools. - With "logical" CSS properties such as
margin-inline-start, the same styles work in both directions. - Plugins use Django's standard gettext, and their name and description can be multilingual too.
- An automated test blocks any untranslated string in the core.
Ravix next to WordPress
- Multilingual interface: 10 languages built into Ravix. WordPress translates its interface, but multilingual content needs a plugin.
- A separate URL per language: built into Ravix. In WordPress, via a plugin.
- hreflang and a sitemap per language: automatic in Ravix. In WordPress, via a plugin.
- Right-to-left and the Persian calendar: built into Ravix. In WordPress, the Persian calendar usually needs a plugin.
New: translations linked together
- Link any post or page to its translations in other languages from the "Translations" card.
- The site's language switcher jumps straight to that post's translation, not to the home page.
- hreflang tags are generated on the posts themselves, so Google shows each version to readers of that language.
- This very article is linked across 10 languages; try the language switcher at the top of the page.
Automatic translation doesn't exist, on purpose: you or your translator write the text for each language, so quality and SEO stay high.
Try it now: install Ravix on a VPS or get the latest version from the download page.
Comments
No comment has been posted yet.