Base manual
How OLOlang really translates a WordPress site, from the database to SEO, and how you work in the dashboard translator.
What is OLOlang
OLOlang is the suite's native multilingual system: it takes a WordPress site to 28 languages with no third-party plugins and no fragile frontend patches. It's included free the first year with OLObuild Free, and for life with OLObuild Pro.
“Native” means the translation isn't a layer glued on top: it runs through the database, covers content, menus and strings, and produces first-class URLs and metadata for every language.
How it translates
- Content: pages, posts, OLObuild tiles: every language has its own version, saved in the DB.
- Menus: navigation items follow the active language, no manual menu duplication.
- Strings: theme and plugin text (buttons, labels, messages) translated via the database.
Why via DB — Solutions that rewrite the HTML on the fly break with every theme change. Translations in the database survive: they're content, not a trick.
The engines
- DeepL: quality machine translation for the languages it covers.
- AI translator: to refine, adapt the tone, cover the remaining languages.
- Glossary: your terms (brand, products, jargon) stay yours in every language: “OLObuild” never becomes something else.
- Translation memory: a sentence already translated gets reused: guaranteed consistency and costs that drop over time.
The workflow
The dashboard translator is the view for whoever is translating: progress by language, missing strings, review queue. The typical flow:
- 1 · Automatic batch: DeepL/AI translate the content in bulk for the chosen language.
- 2 · Human review: the translator goes through the entries, corrects, approves.
- 3 · Publishing: the language goes live with URLs, menus and SEO already in place.
Multilingual SEO
- hreflang: every page declares its variants: Google sends the user to the right language.
- Localized URLs:
/it/camere-vista-lago,/en/lake-view-rooms,/de/zimmer-mit-seeblick. - Sitemap: every variant in the sitemap, meta and title per language.
No version is a second-class citizen: for search engines, every language is a first-class page.
Spec sheet
- Type
- Native multilingual system for WordPress
- Requirements
- WordPress 5.9+ · PHP 7.4+ · OLObuild
- Languages
- 28
- Engines
- DeepL + AI translator
- Quality
- Protected terms glossary · translation memory
- Scope
- Content, menus, theme and plugin strings, via database
- Workflow
- Dashboard translator: automatic batch → review → publishing
- SEO
- hreflang, localized URLs, sitemap and meta per language
- Suite
- Also translates OLObooking flows and OLObuild tiles
- Cost
- Free the 1st year (Free) · for life with OLObuild Pro