What is the difference between internationalization (i18n) and localization (l10n)?

Internationalization (i18n) is the process of designing your website's architecture so it can support multiple languages and regions without requiring engineering changes for each one. Localization (l10n) is the actual adaptation of content — translations, date formats, currencies, and cultural references — for a specific locale. You internationalize once, then localize for each market.

Do I need hreflang tags if I only have two languages?

Yes. Even with just two languages, hreflang tags tell search engines which version of a page to serve to which audience. Without them, Google may treat your translated pages as duplicate content, which can hurt rankings for both versions. Proper hreflang implementation is essential regardless of how many languages you support.

Multilingual Website: Technical Guide to Web Internationalization

Why Internationalization Matters More Than Ever

Over 60% of internet users prefer browsing in their native language, and 72.4% of consumers say they are more likely to buy a product with information in their own language (CSA Research). If your website only speaks one language, you are leaving money — and market share — on the table.

But going multilingual is not just about translating text. It requires a solid technical foundation known as internationalization (i18n). Get it wrong, and you risk duplicate content penalties, broken user experiences, and tanked SEO rankings.

Here is what you need to know.

Choosing the Right URL Structure

Your URL architecture is the first critical decision. There are three main approaches:

Strategy	Example	SEO Strength	Complexity
Subdirectories	example.com/fr/	High (shares domain authority)	Low
Subdomains	fr.example.com	Medium (treated as separate site)	Medium
ccTLDs	example.fr	High (strong geo-targeting)	High (separate domains)

The recommended approach

For most businesses, subdirectories offer the best balance of SEO value and simplicity. All language versions benefit from the main domain’s authority. Google itself recommends this approach for most use cases.

ccTLDs make sense only if you have dedicated teams and budgets per country. Subdomains sit awkwardly in between — more overhead than subdirectories without the geo-targeting power of ccTLDs.

Implementing Hreflang Tags Correctly

Hreflang is the HTML attribute that tells search engines which language and regional version of a page to display. It looks like this:

<link rel="alternate" hreflang="en" href="https://example.com/en/about" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/about" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/about" />

Common hreflang mistakes to avoid

Missing return tags: Every hreflang reference must be reciprocal. If page A points to page B, page B must point back to page A.
Wrong language codes: Use ISO 639-1 for language (fr, en) and ISO 3166-1 for region (fr-FR, en-US). Mixing these up is surprisingly common.
Forgetting x-default: Always include an x-default tag as the fallback for users whose language or region does not match any version.
Inconsistent URLs: Ensure the URLs in hreflang tags exactly match your canonical tags. A single trailing slash mismatch can break everything.

According to a study by Ahrefs, over 75% of websites with hreflang tags have implementation errors. It is one of the most frequently botched technical SEO elements.

CMS Configuration and Translation Workflows

WordPress

Plugins like WPML or Polylang handle multilingual content effectively. WPML supports over 40 languages, manages string translations, and auto-generates hreflang tags. For headless setups, you can use the REST API or GraphQL to serve localized content by locale parameter.

PrestaShop

PrestaShop has built-in multilingual support at the core level — product descriptions, categories, CMS pages, and URLs can all be translated per language. For stores targeting multiple countries, combining language settings with multi-currency and tax rules is essential.

At Lueur Externe, we have been configuring multilingual PrestaShop and WordPress environments since 2003, ensuring every technical detail — from hreflang to localized sitemaps — is handled properly.

Beyond Translation: True Localization

Technical internationalization is only half the work. True localization means adapting:

Date and number formats (MM/DD/YYYY vs DD/MM/YYYY)
Currency display and payment methods per region
Right-to-left (RTL) layouts for Arabic or Hebrew
Images and cultural references that resonate locally
Legal compliance (GDPR for Europe, LGPD for Brazil, etc.)

A technically perfect multilingual site that ignores these details will still feel foreign to its target audience.

Conclusion: Build It Right From the Start

Internationalization is not an afterthought — it is an architectural decision that shapes your URL structure, your SEO performance, and your users’ experience across every market you enter. Subdirectories, clean hreflang implementation, proper CMS configuration, and genuine localization are the pillars of a successful multilingual website.

If you are planning to expand internationally, Lueur Externe can guide you through every technical layer — from initial architecture to deployment on AWS. Get in touch with our team and let’s build a website that speaks your customers’ language.