## The Multilingual Website Problem Adding multiple languages to a website has traditionally been painful. With WordPress, you need WPML ($79/year) or Polylang, a compatible theme, careful configuration, and constant maintenance to keep translations in sync. With separate sites per language, you're managing multiple instances of everything. With subdirectories and manual translation, you're one missed page update away from inconsistent content. For businesses operating across language boundaries — which is most of Europe — multilingual support shouldn't be a premium feature or a technical project. It should be as easy as writing content in one language and translating it. That's what Lucky Desk's multilingual system does. Here's how to set it up. ## Minute 1-2: Enable Languages Go to Settings → Languages. Your default language is already active (the one you've been writing content in). Click "Add Language" and select the languages you want to support. Lucky Desk supports 30+ languages out of the box, including right-to-left languages like Arabic and Hebrew. Each language gets: - A language code (en, nl, de, fr, es, etc.) - A display name - An optional regional variant (en-US vs. en-GB) For a typical European business, you might enable: Dutch (nl), English (en), German (de), and French (fr). That covers the Benelux, DACH, and Francophone markets. **Pro tip:** Start with two languages. Get the workflow down, then add more. Going from one to two is the hard part; going from two to five is just more of the same. ## Minute 3-4: Configure URL Structure Choose how multilingual URLs work on your site. Three options: **Subdirectories (recommended):** yoursite.com/en/about, yoursite.com/nl/over-ons, yoursite.com/de/uber-uns. This is the approach Google recommends for SEO. All languages share the same domain authority. **Subdomains:** en.yoursite.com, nl.yoursite.com. Useful if you want completely separate site identities per language. Slightly more complex to set up (DNS records per language). **Path with default language at root:** yoursite.com/about (English as default), yoursite.com/nl/over-ons (Dutch as secondary). The default language doesn't have a prefix, which keeps URLs cleaner for your primary market. Select your preference in Settings → Languages → URL Strategy. The system applies it immediately to all existing content. ## Minute 5-7: Translate Your First Page Open any page in the editor. You'll see a language switcher in the toolbar showing your active languages. Your content is currently in your default language. **Click the target language** (e.g., switch from English to Dutch). The editor shows the page structure with empty content fields for the new language. The layout, block structure, and design carry over — you're only translating the text. **Three ways to translate:** 1. **Manual translation.** Type the translation directly into each block. Best for important pages where you want to control every word. 2. **AI-assisted translation.** Click "Auto-translate" on any block. The system generates a translation using AI, which you review and edit. This is fast and surprisingly good for most content, but always review — AI translations can be awkward with industry-specific terminology. 3. **Translation export/import.** Export translatable content as a file (XLIFF or CSV), send it to a professional translator or translation agency, and import the completed translations. Best for large volumes or when accuracy is critical. For your first page, try AI-assisted translation. It takes seconds per block. Read through the result, adjust anything that sounds unnatural, and save. You now have a bilingual page. ## Minute 8-9: Set Up Language Navigation Your visitors need a way to switch between languages. Add a language switcher to your site navigation: **In the navigation editor**, add the "Language Switcher" component. Choose its style: - **Dropdown:** A compact selector showing the current language with a dropdown for alternatives. Works well in headers with limited space. - **Flags:** Language flags side by side. Visually clear but can be problematic (flags represent countries, not languages — do you use a British or American flag for English?). - **Text links:** Language codes or names as text links (EN | NL | DE). Clean and unambiguous. The language switcher automatically detects which languages have translated content for the current page. If a page isn't translated to German yet, the German option either hides or shows with a note — configurable in settings. ## Minute 10: SEO for Multilingual Lucky Desk automatically handles the technical SEO requirements for multilingual sites: **hreflang tags.** Every page includes hreflang tags pointing to its translations. This tells Google which version to show in which market. The tag <link rel="alternate" hreflang="nl" href="yoursite.com/nl/over-ons" /> is generated automatically. **Localized meta data.** Each language version has its own meta title and meta description. When you translate a page, the meta fields are included in the translation workflow. **Localized sitemaps.** Your XML sitemap includes all language versions with proper hreflang annotations. Submit it to Google Search Console once; updates happen automatically. **Canonical URLs.** Each language version has its own canonical URL, preventing duplicate content issues across languages. **Localized slugs.** URLs can be translated too. /about in English becomes /over-ons in Dutch, not /nl/about. This is better for SEO and user experience. ## Beyond the First 10 Minutes With the basics in place, here's what to tackle next: ### Translation Workflow for Teams If multiple people create content, set up a translation workflow: 1. Content is created in the default language 2. Status is set to "Needs Translation" for each additional language 3. Translators receive a notification with a link to the translation interface 4. Translated content goes to "Review" status 5. Reviewer approves and publishes This prevents untranslated content from appearing on the live site and gives translators a clear queue of work. ### Content That Shouldn't Be Translated Not everything needs translation. Images with text baked in, videos, embedded widgets, code snippets — some content is language-independent. Mark these blocks as "shared across languages" so they appear the same in every language version without duplicating effort. ### Handling Partial Translations What happens when a page exists in English and Dutch but not German? Options: - **Hide the page** from the German site (safest for public-facing content) - **Show the English version** as a fallback (practical for internal tools) - **Show a "not yet translated" message** with a link to the default language version Configure this globally in settings and override per page if needed. ### Translation Memory As you translate more content, Lucky Desk builds a translation memory — a database of previously translated phrases and sentences. When the same phrase appears in new content, the system suggests the existing translation for consistency. This speeds up translation and ensures terminology stays consistent across your site. ## Ongoing Management The biggest challenge with multilingual websites isn't the initial setup — it's keeping translations in sync as content changes. Lucky Desk tracks this automatically. When you update a page in the default language, the other language versions are flagged as "potentially outdated." Translators see a diff of what changed, so they can update just the modified sections rather than re-translating the entire page. This "incremental translation" approach is what makes multilingual content manageable long-term. Without it, every content update becomes a full translation project, and eventually translations fall behind or get skipped entirely. Set up a weekly review of the "needs update" queue, and your multilingual site stays current without becoming a burden.