Joomla Multilingual Setup: Step-by-Step Guide with Examples

Imagine: a Joomla site needs a second language. You install the language pack, create menus — but links lead nowhere, hreflang isn't generated, and the language switcher doesn't appear. Sound familiar? We've encountered this dozens of times. In this article, we'll break down how to set up Joomla multilingualism correctly: from installing language packs to SEO optimization with hreflang. You'll get ready-to-use configs and an error checklist.

Joomla is the only major CMS with full multilingual support out of the box, without paid plugins. Multi-language support is built into the core: articles, menus, categories, modules, and templates are translatable. However, configuration requires attention to detail. Over 5 years of experience, we've set up multilingualism on 15+ Joomla projects — from small blogs to e-commerce stores. We guarantee stable operation and correct indexing.

Why Language Filter Is the Key Plugin

Without the Language Filter plugin activated, the language switcher won't work and hreflang won't be added. Enabling it is a mandatory step. Automatic language change and removal of the prefix for the default language are typical settings. Check these parameters:

Automatic language change: Yes
Remove URL language code for default language: Yes
Show language code in URL: Yes

Even with the plugin enabled, the switcher may not work if menus for each language are not created or the module is not placed in a template position. More details in the Joomla documentation.

Installing Language Packs and Configuring Content Languages

Go to Extensions → Languages → Install Languages. Select the required languages (Russian, Ukrainian, English), click Install — Joomla will download the packs from the official server.

Or manually via CLI:

# For Joomla 4+
php cli/joomla.php extension:install --url https://download.joomla.org/language/ru-RU/ru-RU.tar.gz

Then configure Content Languages: Extensions → Languages → Content Languages → add languages with these settings:

• Language tag: ru-RU, en-GB, uk-UA
• URL code: ru, en, uk — used in the URL
• SEF prefix: same as above

How to Set Up Hreflang Without Errors

Joomla generates hreflang automatically when two conditions are met: the Language Filter is enabled and language associations are created. To verify:

curl -s https://yourdomain.com/ | grep hreflang
# <link rel="alternate" hreflang="ru" href="https://yourdomain.com/ru/" />
# <link rel="alternate" hreflang="en" href="https://yourdomain.com/en/" />

Errors occur when associations are not configured or the content language is not linked to the article. Use the Language Associations component for each record.

Multilingual Articles, Menus, and Switcher

For each language, create a separate version of the article. Joomla links them as language associations.

1. Create an article for Russian: language = ru-RU
2. Create an article for English: language = en-GB
3. Go to Components → Language Associations → select the Russian article → associate it with the English one

Menus: create a separate menu for each language. Menu items are tied to a specific language. This is mandatory for the switcher to work.

Add the Language Switcher module (mod_languages) to a template position:

<jdoc:include type="modules" name="language-switcher" style="none" />

Module parameters:

• Use image flags: optional
• Horizontal position
• Use a dropdown: for many languages

Content Model and Language Overrides

For complex sites, we recommend this structure:

Categories (by language):
├── News (ru-RU)
├── News (en-GB)
└── Новини (uk-UA)

Menus:
├── Main Menu (ru-RU)
├── Main Menu (en-GB)
└── Head Menu (uk-UA)

In our experience, the native Joomla approach outperforms paid solutions (e.g., Falang) in performance: no extra database queries, reducing load time by up to 30%.

Language string overrides:

; language/ru-RU/ru-RU.com_content.ini
COM_CONTENT_ARTICLE_MORE_DETAILS="Подробнее"
COM_CONTENT_ARTICLES_FILTER_SEARCH_DESC="Введите поисковый запрос"

Or via Extensions → Languages → Overrides.

Native Multilingualism vs Plugins

Work Process

What's Included in the Work

• Installation and configuration of language packs
• Creation of Content Languages (up to 5 languages)
• Configuration of Language Filter and SEF URLs
• Development of category and menu structure for each language
• Setup of language associations for existing content
• Integration of the Language Switcher module
• hreflang verification and SEO validation
• Documentation for managing multilingualism
• 30-day post-deployment support

Estimated Timelines

Setting up Joomla multilingualism for 2–3 languages, including translation of menus, categories, and basic content, typically takes 2 to 5 days depending on content volume. Larger projects with dozens of pages require additional scoping.

Contact us for an accurate estimate for your project. Order Joomla multilingual setup from experts — we guarantee correct indexing and stable operation.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.