Skip to content

International SEO

Translated URLs: Should Your Slugs Be in the Local Language?

By Shayan Ahmad · · 6 min read

Translated URLs: Should Your Slugs Be in the Local Language? (WhiteLinko blog banner)

When you translate a website, the page content changes language, but what about the URL? Should your German product page live at /de/products/running-shoes or /de/produkte/laufschuhe? Should an Arabic page use Arabic script in its address? There is no single right answer, but the choice affects how searchers see your links, how easy they are to share and how much work your team takes on. This guide looks at the pros and cons of local-language URLs, the encoding issues that catch people out, and how to decide what suits your site.

What Google Says About URL Language

Google can crawl and index URLs in any language, including non-Latin scripts such as Arabic, Urdu, Chinese or Cyrillic. Google's general guidance for multilingual sites encourages using the language of the audience in URLs where it makes sense, because it can help users understand what a page is about before they click.

That said, URL words are a small signal. A page with an English slug can rank perfectly well for searches in another language if the content, title and headings are in that language and hreflang is set up correctly. The decision is more about users and practicality than about rankings.

The Case for Local-Language URLs

They match what people search for

When a French searcher sees a result with /fr/chaussures-de-course, the URL reinforces that the page is in French and about running shoes. An English slug on a French page can look like a mistake or a half-finished translation.

They look trustworthy and consistent

Fully localised sites, where navigation, content and URLs all match the language, feel more professional. This matters most in markets where buyers are wary of foreign sites.

Words in URLs can appear in search results

Google often shows a breadcrumb-style path in search results. Local-language words there give searchers another small reason to click.

The Case Against, or for Caution

More work to manage

Every translated slug must be created, checked and maintained. If a product name changes, you may need to update slugs in several languages and add redirects. For large catalogues, this can be a significant burden.

Mapping between versions gets harder

Hreflang, country selectors and internal tools all need to know which URL in one language matches which URL in another. With identical slugs, this mapping is easy. With translated slugs, you need a reliable lookup, usually handled by your platform or translation plugin.

Platform limitations

Some platforms only translate part of the URL. For example, the slug might be translatable while fixed path segments such as /products/ or /collections/ stay in English. That is usually fine; partial translation is common and does not cause SEO problems.

Encoding Issues With Non-Latin Scripts

This is where many teams get caught out. URLs can technically only contain a limited set of characters. When a URL includes Arabic, Urdu, Chinese or accented letters, browsers and servers convert them using percent-encoding.

What this looks like

An Arabic slug that looks clean in the browser's address bar may turn into a long string of percent signs and codes when copied and pasted into an email, a spreadsheet or some social platforms. Modern browsers usually display the readable version, but many other tools show the encoded one.

Problems it can cause

  • Ugly shared links that look suspicious or broken when pasted.
  • Length limits in some tools, since encoded URLs are much longer.
  • Inconsistent links if some systems link to the encoded form and others to the decoded form, or use different Unicode normalisation for accented characters.
  • Analytics and reporting confusion, where the same page appears under different-looking URLs.
  • Right-to-left display quirks for Arabic and Urdu, where the mix of left-to-right path parts and right-to-left words can display oddly.

How to reduce the risk

  • Make sure your server, CMS and CDN handle UTF-8 URLs consistently.
  • Use the same form of each URL everywhere: in sitemaps, canonicals, hreflang and internal links.
  • Test sharing important URLs in email, messaging apps and social platforms used in your market.
  • Check Search Console for duplicate or unexpected variants of the same page.

Middle-Ground Options

Transliteration

Instead of native script, you can write local words in Latin letters, for example a Roman Urdu or transliterated Arabic slug. This avoids encoding issues while keeping local words. It works well where searchers commonly use Latin letters themselves, as many Urdu speakers do online.

Translate slugs, keep folders

Translate the meaningful part of the URL, the slug, while keeping structural folders like /de/ or /products/ consistent. This is the most common approach and keeps mapping manageable.

Remove accents

For languages with accented Latin letters, such as French, German or Spanish, many sites use unaccented versions in URLs, such as "telephone" rather than "téléphone". This keeps URLs readable everywhere while staying in the local language.

A Quick Research Step Before You Decide

Before settling on an approach, look at what already works in your target market. Search for your main products or services in that language, with your location set to the country, and note how the top-ranking local sites format their URLs. Do they use native script, transliteration or English slugs? Do the big local retailers or service providers translate their folders?

This does not dictate your choice, but it shows what local searchers are used to seeing. If every leading site in a market uses Latin-letter slugs, native-script URLs may look unusual. If they all use fully local URLs, English slugs may make your site stand out for the wrong reasons. Combine what you see with your platform's capabilities and your team's capacity, and choose the option you can maintain consistently.

How to Decide

  1. Who is the audience? If buyers expect a fully local experience, translated slugs are worth the effort.
  2. What script does the language use? For non-Latin scripts, weigh readability against encoding issues, and consider transliteration.
  3. How big is the site? Large catalogues need automated slug translation and reliable mapping.
  4. What does your platform support? Work with your CMS rather than against it.
  5. Are you changing existing URLs? Changing live URLs means redirects and a temporary period of reassessment. It is only worth doing with good reason.

Platform details matter here. Our Shopify SEO service and WordPress SEO service cover how translated URLs work on each. For bilingual Arabic and English sites in the Gulf, our UAE SEO page shows how we approach that market.

If You Change Existing URLs

  • Map every old URL to its new version and set up permanent redirects.
  • Update hreflang, canonicals, sitemaps and internal links to the new URLs.
  • Monitor Search Console for crawl errors and indexing changes for several weeks.

Our technical SEO service handles URL changes like these, and our international SEO service covers the wider multilingual setup.

FAQs

Do translated URLs improve rankings?

Only slightly, if at all. Content, titles and hreflang matter far more. The main benefits are for users: clearer, more trustworthy links in their own language.

Can Google index URLs in Arabic or Urdu script?

Yes. Google can crawl and index non-Latin URLs. The main issues are practical, such as how encoded URLs look when shared and keeping links consistent.

Should I translate the folder names too?

It is optional. Many sites translate only the slug and keep structural folders consistent, which is easier to manage and causes no SEO problems.

Is it worth changing English slugs on an existing translated site?

Only with a clear reason and a careful redirect plan. If the site performs well, the benefit may not justify the risk and effort.

Get Your Multilingual Setup Reviewed

If you are planning a translated site or unsure whether your current URLs are causing problems, request a free SEO audit. We will check your URLs, hreflang and language versions and tell you what to change.

  • translated urls
  • multilingual seo
  • url structure
  • hreflang
  • international seo

Have a question about this for your own site?

A 15-minute call is usually enough to tell whether it applies to you and what to do first.

Book a 15-min callGet My Free SEO Audit

Related posts

Ranking in Canada Without a Canadian Office (WhiteLinko blog banner)

International SEO

Ranking in Canada Without a Canadian Office

How foreign businesses can rank in Canada without a local office: domain choices, Canadian spelling, French for Quebec, local proof and Canadian links.

All blog posts →

Talk to WhiteLinko

Want this applied to your site?

Book a 15-minute call to talk through your goals, or start with a free SEO audit: a prioritised list of fixes, reviewed by a specialist.

Free PDF · 2026 edition

The WhiteLinko SEO Checklist

Six pages of tick boxes: technical, on-page, content, local, links, AI search and GA4.

Get the checklist
Free SEO Audit