slugme.ioclean-url-slug-generator

Multilingual URL Structure: Slugs, Subfolders & hreflang

How to structure multilingual URLs: ccTLDs vs subdomains vs subfolders, translated and native-script slugs, hreflang, and removing a language safely.

By 5 min read
Multilingual URL Structure: Slugs, Subfolders & hreflang

Going multilingual multiplies every URL decision by the number of languages you support. Get the structure right and each language version ranks in its own market; get it wrong and versions compete with each other, Google shows French users the English page, or a migration leaves hundreds of dead URLs behind.

This guide covers the decisions in the order you'll face them.

Decision 1: where each language lives

There are three structures, and Google documents the trade-offs in its guide to managing multi-regional and multilingual sites:

Structure Example Pros Cons
Country-code domains (ccTLDs) example.fr, example.de Strongest country signal; local trust Expensive; separate authority per domain; heavy to maintain
Subdomains fr.example.com Easy to host separately Authority less clearly shared; still multiple properties
Subfolders example.com/fr/ One domain, shared authority, cheap, simple Weaker country signal than ccTLDs

For most sites, subfolders are the right default. They are what frameworks like Next.js and Nuxt generate out of the box, keep all your links pointing at one domain, and make hreflang straightforward. Choose ccTLDs only when you are genuinely running separate country businesses (different prices, laws, inventory).

Avoid URL parameters (?lang=fr) for language — they are easy to lose, hard to target, and awkward to report on.

Language vs. region in the prefix

Use a language code (/fr/) when content differs by language. Add a region (/fr-ca/, /fr-fr/) only when content actually differs by country: prices, spelling, legal text. Don't create /en-us/, /en-gb/ and /en-au/ copies of identical pages — that's three duplicates to maintain.

Decision 2: translate the slug or not

Once you have /fr/, what comes after it? Compare:

/fr/seo-friendly-url-guide          ← English slug in a French section
/fr/guide-url-optimisee-seo         ← translated slug

Translate it. Google's URL structure guidelines recommend using words in your audience's language. A translated slug matches local searches, reads naturally in local search results and link previews, and signals that the page was properly localized rather than machine-wrapped.

Apply each language's own slug rules when you do — they differ more than people expect:

Language Rule Example
French Flatten accents, split elisions Étude sur la sécurité → etude-sur-securite
Spanish ñ → n, drop ¿ ¡ Diseño web en España → diseno-web-espana
German ä → ae, ö → oe, ü → ue, ß → ss Straße in München → strasse-muenchen
Arabic Keep script, strip Harakat/Tatweel دليل التسويق الرقمي → دليل-التسويق-الرقمي

The per-language generators — French, Spanish, German and Arabic — apply these rules, including each language's stop words. For a whole translated catalog, the bulk slug generator does the same for a list of titles.

Decision 3: native script or transliteration

For languages that don't use the Latin alphabet, you have a real choice:

/ar/دليل-التسويق-الرقمي        ← native Arabic script
/ar/dalil-altaswiq-alraqmi      ← transliterated

Google indexes Unicode URLs and displays them readably in results, so native script works. It matches what users type and recognize. The trade-off is that when a native-script URL is copied as plain text in some apps, it appears percent-encoded (/ar/%D8%AF%D9%84%D9%8A%D9%84-…) — long and opaque.

Transliteration produces short, universally safe URLs, but there is often no single standard romanization, so the result may match nobody's spelling.

Our recommendation: native script for Arabic, Persian, Hebrew, Cyrillic, Greek and CJK content aimed at native speakers, transliteration when the audience is mixed or your platform handles Unicode URLs poorly. Whatever you choose, apply it consistently across the language. More detail in URL slugs for non-Latin languages.

Decision 4: connect versions with hreflang

Translated pages with different slugs need to be explicitly linked, or Google may not realize /guide-url-optimisee-seo is the French version of /seo-friendly-url-guide. That is what hreflang is for:

<link rel="alternate" hreflang="en" href="https://example.com/seo-friendly-url-guide" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/guide-url-optimisee-seo" />
<link rel="alternate" hreflang="de" href="https://example.com/de/seo-freundliche-url-anleitung" />
<link rel="alternate" hreflang="x-default" href="https://example.com/seo-friendly-url-guide" />

The rules that trip people up:

  • Reciprocal: every version lists every other version and itself. If the French page doesn't link back to the English one, Google may ignore the annotation.
  • Absolute, canonical URLs only: no relative paths, no URLs that redirect, no URLs with tracking parameters.
  • Valid codes: ISO 639-1 language (fr), optionally plus ISO 3166-1 region (fr-CA). en-UK is invalid — it's en-GB.
  • One canonical per language: each version's rel="canonical" points to itself, never to the English version.

You can declare hreflang in HTML <head>, HTTP headers or the XML sitemap. The sitemap method scales best for large sites.

Decision 5: don't force-redirect by location

It's tempting to detect the visitor's IP or Accept-Language header and redirect them to "their" version automatically. Don't — or at least not without an escape hatch:

  • Googlebot mostly crawls from the US without an Accept-Language header, so automatic redirects can stop it from ever seeing your other languages.
  • Travelers, expats and bilingual users get trapped in the wrong version.

Instead, show a dismissible banner suggesting the matching language, and let hreflang steer search users to the right version from the results page.

When you remove a language

Languages get added and removed, and the removals are where traffic quietly disappears. When you retire a language, its URLs don't vanish from Google's index — they become 404s that keep getting crawled, and any links pointing at them are wasted.

This happened on Slugme.io. The original site shipped /fr, /es and /ar sections; when we went English-only and later rebuilt on Next.js, those prefixes started returning 404s. The fix was a set of permanent redirects to the closest English equivalent — each old language home goes to its dedicated language slug generator, and any deeper path drops the prefix:

// next.config.ts
async redirects() {
  return [
    { source: '/fr', destination: '/french-slug-generator', permanent: true },
    { source: '/es', destination: '/spanish-slug-generator', permanent: true },
    { source: '/ar', destination: '/arabic-slug-generator', permanent: true },
    { source: '/:locale(fr|es|ar)/:path+', destination: '/:path+', permanent: true },
  ]
}

The general rule: map each removed URL to the most relevant remaining page — the same content in another language, or the closest topic — and remove the retired language's hreflang annotations and sitemap entries at the same time. Avoid redirecting everything to the homepage, which Google tends to treat as a soft 404. Our URL normalization guide covers auditing those redirects.

Multilingual URL checklist

  • One structure for all languages (subfolders unless you have a reason not to)
  • Language codes in the prefix; region only where content truly differs
  • Slugs translated, generated with each language's rules
  • Consistent native-script or transliteration policy per language
  • Reciprocal hreflang with self-references and x-default
  • Self-referencing canonical on every language version
  • No forced IP/language redirects; a suggestion banner instead
  • Removed languages redirected, not left to 404

Frequently asked questions

Should I translate URL slugs on a multilingual site?

Yes, in most cases. A French page at /fr/guide-referencement matches French searches and reads naturally to French users, while /fr/seo-guide looks half-translated. Keep the language prefix itself (fr, de) as a code, not a translated word.

Does hreflang affect rankings?

Hreflang doesn't boost rankings; it helps Google show the right language or regional version to each user and treat the versions as alternates rather than duplicates.

Can I use one URL and switch language with cookies or JavaScript?

Avoid it. Google generally crawls without cookies and from US IP addresses, so it may only ever see one language. Each language version needs its own URL.

What should x-default point to?

The page for users who don't match any listed language — often a language-selector page or your main (usually English) version.

Keep reading