Discussion
  • International SEO

Translated URL slugs versus English slugs on localised pages: have you seen any measurable difference in rankings or CTR?

Published 1 reply

Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    I would not expect a measurable ranking difference between translated and English slugs, and I am not aware of a public controlled test showing one. Google has described words in URLs as a very light signal, and it reads the page content, not the slug, to understand what a page is about. The more plausible effects are on users: a URL in the reader’s own language can look more trustworthy in results and when shared, and a slug in a foreign language can look out of place. Against that, translated slugs add operational work: mapping equivalent pages across languages for hreflang, redirects in future migrations, and analytics grouping. For new builds on a platform that handles translated slugs well, translating them is a reasonable choice; changing existing slugs just to translate them is rarely worth the migration risk.

    Where slugs might matter

    Effect Likely size
    Direct ranking effect of slug words Very small, if any
    Click-through from results Possibly small; results often show a breadcrumb or path, where a native-language slug looks more local
    Trust when links are shared Possibly meaningful in some markets; native-script URLs can appear encoded in some contexts
    Operational complexity Real: mapping, redirects and analytics

    Non-Latin scripts

    For languages written in non-Latin scripts, such as Japanese, Arabic, Russian or Greek, the choice is between native script, transliteration and English. Google handles UTF-8 URLs, but native-script characters are percent-encoded in many contexts, so a shared link can look like a long string of codes. Some markets commonly use native-script URLs; others prefer transliteration or English. Look at what well-performing local sites in the market use, and what your CMS, analytics and sharing tools handle cleanly, before deciding.

    If you translate slugs

    • Maintain a mapping of equivalent pages across languages, independent of slugs, so hreflang annotations stay correct.
    • Use local terms that match the page’s target keyword, not literal translations.
    • Keep slugs short and stable; do not change them when titles are edited.
    • Avoid characters that cause encoding problems, or normalise them consistently.
    • Make sure analytics can group equivalent pages across languages, for example by a content ID rather than the URL.

    If you keep English slugs

    English slugs on localised pages are common and generally work fine, particularly for brands with a global identity and for markets comfortable with English. Make sure everything else on the page, including titles, headings, breadcrumbs, content and navigation, is fully localised, because those carry far more weight than the slug. If breadcrumbs appear in results, their labels come from your breadcrumb names and structured data, so localising breadcrumb labels can give results a local appearance even with English slugs.

    Hypothetical example:

    A retailer’s German site uses English slugs such as /de/mens-running-shoes/. The SEO team proposes translating them to /de/herren-laufschuhe/ and wants to know whether it is worth a migration. It tests on one category group: new German slugs with redirects from the old ones, compared against a matched group left unchanged. After three months, rankings in the two groups move similarly, and click-through differences are within noise. The team keeps English slugs for existing pages, localises breadcrumb labels instead, and uses German slugs only for new categories.

    Watch for this:

    Changing slugs across a whole language version is a migration: every URL changes, redirects are needed, and rankings can fluctuate for weeks. The small, uncertain benefit of translated slugs rarely justifies that risk on an established site.

    Consistency within a site matters more than the choice

    The worst outcome is a mixture: some sections with translated slugs, others in English, and a few with slugs half-translated after a partial project. That makes hreflang mapping error-prone, confuses analytics and looks inconsistent to users. Whichever convention you choose for a language version, apply it consistently to new content, document it in the content guidelines and build it into the CMS so editors do not decide page by page. If you do change convention for new sections, keep the old sections as they are rather than mixing styles within one section.

    Where the effort pays off instead

    Local keyword research, localised titles and headings, native-quality content, local navigation labels and correct hreflang all have clearer effects than slug language. If time is limited, those come first. Slugs are a decision to make once, sensibly, when a site or section is built, and then leave alone.

    Translate slugs on new builds when your platform supports it cleanly and the script works well in URLs, keep existing English slugs rather than migrating for them, and put the effort into the localisation elements that visibly matter.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.