14.1 Multilingual Website Architecture

AIUNIFY Leads supports multiple Website Languages for a single website.

The website's language configuration is connected to its public pages, Website Settings, page translations, Website Builder content, navigation, and public rendering behavior.

14.2 How the Public Website Chooses a Language

The confirmed public routing logic evaluates available language information in a defined order.

Depending on the public route being used, AIUNIFY Leads can determine the website language from:

1. A valid language supplied through the supported lang query parameter on applicable page routes.
2. The visitor's language cookie for the website.
3. The website's configured Default language.
4. English, when an English Website Language exists.
5. The first available Website Language.
6. An English language key fallback when no language record resolves.

14.3 Website-Specific Language Cookie

The public website uses a website-specific cookie naming pattern:

lang_{website-slug}

This design allows language selection to be associated with the particular website rather than requiring one universal language choice for every website.

14.4 Language Selection Persistence

Public language controls can update the website-specific language cookie and reload the public website so the visitor sees content in the selected language.

Because the language choice is associated with the website slug, different websites can maintain their own visitor language selections.

14.5 Website Settings by Language

After the public language is determined, AIUNIFY Leads retrieves the Website Settings associated with that Website Language.

This allows settings such as website identity and SEO information to differ from one language to another.

14.6 English Settings Fallback

If the selected non-English language does not have a corresponding Website Settings record, the confirmed public routing logic attempts to use the English Website Settings for that website.

Best practice: Complete Website Settings for every published language rather than relying on fallback behavior.

14.7 Multilingual Website Pages

A Website Page uses one underlying Page Key while storing language-specific page names through Website Page Translations.

For example, the same underlying page can keep a Page Key such as:

about-us

while displaying a language-appropriate page name in each configured Website Language.

14.8 Adding a New Language to Existing Pages

The confirmed website update workflow can create missing page translations when a new Website Language is added.

For an existing page, the generated translation initially uses:

1. Home for the Home page.
2. A readable version of the Page Key for other pages.

The newly created page translation is initially configured to show in the header.

You can then edit the translated page name to the correct language-specific wording.

14.9 Right-to-Left Presentation

Languages such as Arabic and other RTL languages require a different reading direction from left-to-right languages.

The Website Language record includes an RTL setting, and the AIUNIFY Leads front-end theme contains RTL-specific layout rules for supported components.

Examples of RTL adaptation in the source include direction changes, reversed row alignment, adjusted left/right positioning, and mirrored layout behavior.

14.10 Configuring an RTL Language

1. Open Website Languages for the correct website.
2. Add or edit the intended language.
3. Confirm the correct country/flag and language identity.
4. Enable the RTL setting.
5. Save the language.
6. Translate the Website Page names and Website Settings.
7. Preview the public site in that language.

14.11 Review Every Public Page

RTL support at the theme level does not eliminate the need to review actual website content.

Check each page for:

1. Text alignment.
2. Navigation order.
3. Icons and directional graphics.
4. Section spacing.
5. Buttons and calls to action.
6. Forms and contact information.

14.12 Multilingual Content Best Practice

Do not treat the language Name alone as the translation. Configure the language, then review the page names, Website Settings, Website Builder section content, navigation, and public presentation for that language.