Picture a shopper in Madrid. A friend sends her a link to your Spanish page, and it ends in /es/about-us. She clicks anyway, because the page is in Spanish. But the address looked a little foreign, and that tiny hesitation is the whole story of translated URL slugs.
The slug is the page name at the end of an address. Translate it, and the same link reads /es/sobre-nosotros. It’s a small change. It can make your links friendlier, and, done carelessly, it can also break pages that Google already sends visitors to.
This guide gives you a straight answer: what Google actually says, when translated slugs are worth it, the six ways they break, what a safe change looks like, and a 15-minute check you can run on any site.
Key takeaways
- Google reads the visible content of a page to decide its language. It doesn’t use the URL for that.
- Google still recommends words in your audience’s language in URLs, because people read them.
- The real risk is changing the addresses of pages that are already indexed, with no redirects.
- Latin-alphabet languages are the easy case. Russian, Arabic or Japanese slugs work but turn into percent signs when copied.
- On WordPress, ConveyThis gives every language its own folder, hreflang tags and translated sitemaps on every plan, including Free, and translates slugs with one setting.
One page, four addresses
Here’s the same “About us” page in four languages. Only the page name changes. The domain and the language folder stay put.
Leave the slugs untranslated and all four end in about-us. That’s still a valid multilingual site: each language has its own address, which is the part search engines need. If your translated pages don’t have their own addresses yet, fix that first. Our guide to subdirectories and subdomains shows the options.
Does Google care whether the slug is translated?
Less than most people think.
Myth: translated slugs help Google understand that a page is in Spanish.
What Google says: “Google uses the visible content of your page to determine its language.” The URL isn’t used for that (Google Search Central).
A Spanish page with an English slug is still a Spanish page to Google. So why does Google’s own URL guide say “Use words in your audience’s language in the URL (and, if applicable, transliterated words)” (Google Search Central)?
Because of people. Your address shows up in search results, in chat messages, in newsletters and in ads. A reader in Lyon understands /fr/tarifs at a glance and has to think for a second about /fr/pricing. Translated slugs are about that second.
So treat them as a usability and trust upgrade, not a ranking lever. What moves international search far more is a separate URL for each language, linked with hreflang tags.
That foundation is what a translation tool should give you on day one, before you ever think about slugs. On WordPress, ConveyThis does it out of the box: every language gets its own folder such as /es/, with hreflang tags, translated titles and meta descriptions, and translated sitemaps for Yoast, Rank Math and SEOPress. It works on every plan, including the free one.
Should you translate your slugs? The 30-second answer
Find your situation:
Translate
A new language, slugs made of real words, a Latin-alphabet language such as Spanish, French or German.
Test first
Russian, Arabic, Chinese, Japanese and other non-Latin languages. Try a few pages before the whole site.
Leave alone
Translated pages that already rank, unless the old addresses keep working. Slugs that are product codes, IDs or brand names.
A few situations deserve a closer look.
Your translated pages already get traffic. Changing their addresses is a site migration in miniature. Every saved link, every Google result and every ad points to the old address. Only switch if the old addresses keep loading or redirect.
Your target language isn’t written in the Latin alphabet. Google accepts these addresses, and browsers show them nicely in the address bar. Then someone copies the link into an email:
That’s why many sites keep the original slug for these languages, or use a transliterated one.
Your page titles change often. If the slug follows the title, every rewrite can move the page. Lock the slugs of your key pages once and leave them.
Six ways translated slugs break
Slug translation fails in predictable ways. Once you know them, the check at the end takes minutes.
1. Old addresses return 404. Last month Google indexed /es/about-us. Today the page lives at /es/sobre-nosotros. If the old address doesn’t load or redirect, every saved link is dead.
2. Accents and apostrophes. /fr/à-propos can work in your menu and fail in a newsletter, because two systems encoded the à differently. Letters like é, ü and ç, and apostrophes, cause most broken links.
3. Two pages, one slug. “Contact” and “Contact us” both translate to contacto. Only one page can have that address, so the other needs a different one.
4. Nested pages lose a level. /services/web-design has two parts, and each is translated on its own: /servicios/diseno-web. If they get merged into /servicios-diseno-web, the page can’t be found.
5. The signals disagree. Your menu links, the canonical tag, hreflang and the sitemap should all name the same address. The canonical tag is a strong hint, not an order: Google chooses which address to index from all of these signals together. When they point to different addresses, Google may pick one you didn’t intend, and that’s the one people see in search results.
6. Technical addresses get translated. Feeds, API endpoints, file downloads and checkout steps must keep their exact addresses. A translated /feed/ is a broken feed.
What a safe slug change looks like
Say your Spanish “About us” page has been indexed at /es/about-us for a year, and you switch to translated slugs. When everything is set up right, this is what each address returns:
/es/about-us → 301 → /es/sobre-nosotros
/es/sobre-nosotros → 200
/es/sobre-nosotros
en → /about-us
es → /es/sobre-nosotros
fr → /fr/a-propos
x-default → /about-us
/es/sobre-nosotros
Three things to notice. Every signal names the same new address. The old address answers with a single 301, not a chain of redirects or a 404. And the hreflang tags are the same on every language version, so each version points to all the others. If the old address keeps loading as a normal page instead of redirecting, make sure its canonical tag points to the new one.
Example: tracking down a batch of 404s
Two weeks after a switch, Search Console’s Pages report shows a few dozen new “Not found (404)” addresses, all under /fr/. Here’s how to find the cause in ten minutes instead of fixing pages one by one:
- Export the list from the report and sort it.
- Look for a pattern. In this case every address contains an apostrophe or an accent:
/fr/l-equipeworks, but a newsletter links to/fr/l'equipe. - Open the page in your menu and compare its address with the broken one. The difference is the character the two systems wrote differently.
- Fix the source, not the symptom. Edit the slug so it has no special characters, or add a 301 from the broken form. With ConveyThis, editing a slug is one field in My Translations. Then update the old newsletter link if you can.
- Click Validate fix in Search Console, so Google rechecks the whole group.
One pattern, one fix. That’s why the quick check below includes a page with an accent in its name.
ConveyThis for WordPress
Skip the six ways it breaks. Let the plugin handle the plumbing.
/es/, with no DNS changes20,000+ websites translated · 200+ languages · Rated 4.8/5 on Capterra from 36 reviews
How do I translate URL slugs on WordPress with ConveyThis?
Most of the risks above come from slugs that change somewhere you can’t see. With ConveyThis, every translated slug lives in one place, your dashboard, where you can review and edit it like any other translation.
The plugin already puts each language in its own folder, such as example.com/es/, with no DNS changes. Installing it takes a few minutes, and translating the page names takes one more setting:
- In your WordPress admin, open ConveyThis and go to Extended settings.
- Set Translate URLs to Yes and save.
- Open a few translated pages from your menu and check that their links work.
Slugs are translated automatically, like the text on the page. From there, you’re in control:
- Edit any slug. A translated slug is stored like any other translation. Open My Translations in your ConveyThis dashboard and change it. Do this for your five or ten most important pages. See how to edit translations.
- Fine-tune links. The Links tab in the plugin controls how translated links are handled, including whether they end with a slash like your original pages.
- Keep old links alive. The address with the original page name, such as
/es/about-us, keeps loading, so links people saved earlier don’t break.
One honest note: switching the setting on or off changes the addresses of your translated pages, so decide once and don’t toggle it on a live site. The help article on translated URLs has the details, and the Extended settings guide explains every option on that screen.
On other platforms, ConveyThis gives each language its own subdomain or subdirectory. Translated page names are available in the WordPress plugin today.
The 15-minute check
Run this after you turn translated slugs on, with any tool, not only ours. Tick each item as you go.
Tick off as you go
If one check fails, fix or edit that slug before you move on.
Two weeks later: watch Search Console
The quick check tells you the site works. Search Console tells you what Google found. Two steps:
- Right after the switch, inspect one translated address with the URL Inspection tool and click Request indexing.
- About two weeks later, open the Pages report and look at “Not found (404)” and “Page with redirect” for addresses in your language folders. A handful of redirects is expected after a switch. New 404s are not: go back to the example above.
FAQ
Do translated URL slugs improve rankings?
Not by themselves. Google decides the language of a page from its visible content and doesn’t use the URL for that. A translated slug makes the address easier to read for people who search in that language. A separate URL for each language, linked with hreflang, matters far more than the words in the slug.
Will translating slugs break my existing translated pages?
It can. Translating a slug changes the address of the page. If the old address stops loading and has no redirect, saved links and Google results lead to a 404. Before you switch, check whether the old addresses keep working or redirect to the new ones.
Should I translate slugs into Arabic, Russian, Chinese or Japanese?
It works, and Google accepts it, but the address turns into a long string of percent signs when someone copies it. Many sites keep the original slug for these languages. If you translate, test a few pages first.
Can I edit a translated slug by hand?
Yes, and you should for your most important pages. With ConveyThis, a slug is stored like any other translation, so you can change it in My Translations in the dashboard.
Should the language folder be translated too?
No. Keep the language code, such as /es/ or /fr/, exactly as it is. Only the page names after it are translated.
The short version
Translated slugs make your addresses readable for the people you translated the site for. They don’t replace the basics: a separate URL for each language, hreflang, and pages that load. Translate slugs when you launch a new language with word-based addresses, be careful with pages that already rank, and spend fifteen minutes checking links, canonical tags and the sitemap afterwards.
If you’d rather not assemble those basics yourself, that’s what ConveyThis is for. Install the plugin, pick your languages, and your site gets language folders, hreflang and translated sitemaps in a few minutes. Review the pages that matter in the visual editor, turn on translated slugs when you’re ready, and run the check above once.
Make your WordPress site multilingual today
Language folders, hreflang and translated sitemaps on every plan, translated slugs when you want them. Start on the free plan: 10,000 words, no credit card.
Start free