karoliinapaappa

LingoSlug Lite is a lightweight solution for multilingual URLs when you want localized permalinks (per-language slugs) and redirects, but you do not need a full multilingual suite.
It is designed for two common setups:
<ul>
<li>Sites where the same WordPress page (same page ID) is rendered in different languages by another language/translation solution (locale switching), and</li>
<li>Sites where each language is managed as a separate page — but you still want clean, localized URLs.</li>
</ul>
LingoSlug Lite handles URL slugs + redirects, but does not translate content.
Example:
Before: 
– (EN) <code>example.com/contact/</code> 
– (DE) <code>example.com/kontakt-page/</code>
After: 
– (EN) <code>example.com/en/contact/</code> 
– (DE) <code>example.com/de/kontakt/</code>
Slug cleanup example (same language):
Before (default WordPress slug): 
– <code>example.com/en/contact-page-2/</code>
After (configured clean slug): 
– <code>example.com/en/contact/</code>
LingoSlug Lite does not translate content and does not create language pages for you.
Problems this plugin solves:
<ul>
<li>Ugly or inconsistent URLs like <code>/sample-page/</code> or <code>/english-page-2/</code></li>
<li>Duplicate URLs / wrong-language URLs after switching languages (automatic redirects help keep URLs consistent)</li>
<li>Better search engine consistency: redirects help crawlers index the correct language URL instead of duplicates/wrong-language URLs.</li>
</ul>
Who this is for:
<ul>
<li>You want language-aware URLs (e.g. <code>/{lang}/{slug}/</code>) for selected pages.</li>
<li>You manage languages manually and just want URL hygiene (slugs + redirects).</li>
<li>Your language solution sets the WordPress locale per request and/or uses a <code>/{lang}/...</code> prefix.</li>
</ul>
Features:
1) Per-language slugs 
– Configure a page and define a slug per language code (e.g. <code>en</code>, <code>sv</code>). 
– The plugin adds rewrite rules so configured pages can have language-aware URLs. 
– Permalinks are filtered so links point to the configured slug for the current locale. 
– As a fallback, a query parameter can also be used (configurable in settings, e.g. <code>?lang=en</code>). 
– Free version note: the plugin allows the site default language + 1 additional language (max 2 total).
2) Automatic redirects 
– Helps avoid duplicate or wrong-language URLs after switching languages (redirects to the correct slug for the current locale).
3) Optional switcher 
– Enable an optional navigation switcher via shortcode <code>[lingoslug_lite_switcher]</code>. 
– Shortcode parameters: 
 – <code>page_id</code> (optional): Render the switcher for a specific page ID. If omitted, the plugin uses the currently viewed page when possible. 
– Important: The switcher requires another plugin to translate the page dynamically (same page ID) by switching the site language/locale. LingoSlug Lite does not automatically map separate translated pages to each other.
4) Slug cleanup 
– Configure clean, consistent slugs (per language) even if the default WordPress slug is “ugly”. 
– This also works within a single language (e.g. use <code>/en/contact/</code> instead of <code>/en/contact-page-2/</code>).
Privacy:
<ul>
<li>LingoSlug Lite does not collect personal data and does not send data to third-party services.</li>
</ul>
Upgrade to LingoSlug Pro for:
<ul>
<li>Unlimited languages (no free 2-language limit)</li>
<li>Force a page to a specific language URL (useful for mixed-language menus)</li>
<li>Language switcher: shortcode or automatic output (no shortcode needed)</li>
<li>Multilingual SEO extras: optional <code>hreflang</code> output to help Google show the right language version to the right visitors</li>
<li>Optional SEO tools: noindex controls and attachment page handling</li>
</ul>

LingoSlug Lite

Simple clean multilingual URLs with per-language slugs and automatic redirects — for sites where translations are handled separately.

Pieter Bos

Chinese characters don’t come out good in permalinks. Without the Pinyin Slugs plugin activated, the example post I made for the screenshot will get a slug like this: %e6%90%9c%e7%b4%a2%e5%bc%95%e6%93%8e%e4%bc%98%e5%8c%96. With the plugin the slug automatically becomes sousuoyinqingyouhua.
Search engines such as <a href="https://www.baidu.com" rel="nofollow ugc">Baidu</a> cannot make much of the first slug, but they can handle pinyin perfectly, especially when it is written as one long string without hyphens or underscores.
It is possible to limit the amount of characters in the slug. The default is 100, which should be plenty for most.
The Pinyin Slugs plugin was forked from the <a href="https://wordpress.org/plugins/pinyin-permalink/" rel="ugc">Pinyin Permalinks</a> plugin by user <a href="https://profiles.wordpress.org/xiaole_tao/" rel="nofollow ugc">xiaole_tao</a> as that project seemed abandoned. There have been many improvements since; read the changelog for details.
I have decided to only support this plugin through <a href="https://github.com/senlin/pinyin-slugs/issues" rel="nofollow ugc">Github</a>. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue over at Github. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.
PLEASE DO NOT POST YOUR ISSUES VIA THE WORDPRESS FORUMS
Thanks for your understanding and cooperation.
<h4>WPML Compatible</h4>
The Pinyin Slugs plugin has received the <a href="https://wpml.org/plugin/pinyin-slugs/" rel="nofollow ugc">WPML Certification of Compatibility</a> and is featured on the WPML website with the article <a href="https://wpml.org/documentation/how-to-build-a-wordpress-site-in-china/" rel="nofollow ugc">How to Build a WordPress Website in China and Reach an International Audience</a>.

Pinyin Slugs

Transforms Simplified or Traditional Chinese character titles into Pinyin to create a permalink friendly slug.

LingoSlug Lite vs Pinyin Slugs