Native Multilingual Engine. Zero Translation Bloat.

Build global websites without fragile plugins or database duplication. Pragma CMS features a native multi-language engine at the database and routing levels. Serve translated content, automate hreflang, and manage global SEO in a unified monolithic pipeline.

Launch a Multilingual Site Read I18n docs

True Localization, Built Into the Core.

Legacy CMSs require multiple database instances or unstable plugins to translate a page. Pragma handles localization natively via normalized translation tables. One base entry, unlimited language mappings, zero query overhead.

language

Define (Locales)

Activate global languages inside the admin dashboard. The system automatically initializes the database mapping layers.

translate

Translate (Forms)

Editors translate fields side-by-side. Unchanged values can fallback or alert editors of missing translations.

route

Route (Language Map)

The router automatically detects the language code, loads localized dictionaries, and injects alternate hreflang tags.

Structured for global search engines.

table_view

Normalized Translation Tables

Strict separation of structural data (IDs, dates, configurations) and localized text elements (titles, slugs, content).

language

Automated Hreflang alternate

Our routing layer generates clean, alternate hreflang tags natively during compilation to guarantee crawl compliance.

swap_horiz

Smart Translation Fallback

Control fallback behaviors when a translation doesn't exist yet. Fallback to default language or serve a clean notification.

dictionary

Localized UI Dictionaries

Load static translations seamlessly from core, site, theme, and extension .php files with zero runtime overhead.

Localized routing resolved in one boot phase.

Multi-language is not a plugin; it is a core system design. We do not duplicate your database tables to translate your pages.

verified

Strict Hreflang Validation

Alternate tags are only emitted for published, active translations, protecting your SEO score.

swap_horiz

Optimized Language Switcher

Detects missing translations and applies rel="nofollow" to preserve search engine crawl budget.

public

Isolated Site Locales

Run different languages or localized settings on different site mappings under the same Platform.

bolt

Unified Query Footprint

Translations are resolved in a single indexed query alongside the base entry, keeping render times fast.

Frequently Asked Questions

How are translations stored in the database?

It uses a base table for structural IDs, dates, and settings, and a normalized _translation table for localized text fields. There is no duplicate rows or overhead.

Does it automate SEO hreflang tags?

Yes. Alternate hreflang tags and x-default fallbacks are handled natively by the routing layer during page compilation.

Can we translate static theme elements?

Yes. Using the global helper getTranslation(), the CMS matches static keys to local .php dictionary files.