URL Slug Translation
By default, a translated page keeps its original slug with a language prefix added. For example, a German version of your “About” page would live at /de/about/. With URL Slug Translation active, you can give it a proper German slug instead: /de/ueber-uns/.
This matters for SEO. Search engines treat URL path segments as relevance signals. A slug in the visitor’s language communicates that the page genuinely serves that locale, not just that a language prefix was slapped onto an English URL.
Three Types of Slugs
Section titled “Three Types of Slugs”Omnalingo Pro can translate three different kinds of slugs, each controlling a different part of your URLs.
Page and post slugs
Section titled “Page and post slugs”The slug for an individual page or post. If your About page lives at /about/, the slug is about. Translating it for German might give you ueber-uns, making the German URL /de/ueber-uns/.
This is the most common type — you’ll translate these one page at a time in the visual editor.
Term slugs
Section titled “Term slugs”The slug for a category, tag, or other taxonomy term. If you have a product category at /product-category/shoes/, the slug is shoes. A German translation might be schuhe, giving you /product-category/schuhe/ for German visitors.
Term slugs are also set in the editor, on the term’s own edit screen.
Rewrite bases
Section titled “Rewrite bases”The prefix segment that identifies a post type or taxonomy in the URL — not tied to any individual page, but applying site-wide. For example, WooCommerce uses product as the rewrite base for its products, giving URLs like /product/my-item/. Translating this base to German (produkt) changes the URL structure to /de/produkt/my-item/ for all German product pages at once.
Rewrite bases are set from the bulk actions area in the Omnalingo editor, not on individual posts.
Translating a Page or Post Slug
Section titled “Translating a Page or Post Slug”- Open the page or post in the Omnalingo visual editor.
- Find the URL / Slug field below the title and content fields for the target language.
- Enter your translated slug, or click AI Translate to generate one automatically.
- Save your changes.
Slugs are generated automatically when you translate a title. When you translate a page’s title, Omnalingo fills in the slug field automatically based on the translated title. You can leave the auto-generated slug as-is or override it with your own.
Slug format: Use lowercase letters, numbers, and hyphens. Avoid spaces and special characters. Omnalingo handles common accented characters for you (for example, translating a German title with umlauts will produce a properly formatted slug).
Slug Conflict Warning
Section titled “Slug Conflict Warning”If you enter a slug that is already used by another page in the same language, you will see a conflict warning in the editor. The warning shows which other page already has that slug. You will need to choose a different slug before saving.
No two pages in the same language can share the same translated slug — this would make it impossible for the site to know which page to show.
After Translating Rewrite Bases
Section titled “After Translating Rewrite Bases”WordPress caches its URL routing rules. When you save a rewrite base translation, this cache is not updated automatically. Until the cache is refreshed, any URL using the translated rewrite base will return a 404 error.
To fix this: Go to Settings → Permalinks in the WordPress admin and click Save Changes. You do not need to change anything — just clicking Save is enough to flush the URL cache.
If you use a caching plugin (WP Rocket, W3 Total Cache, etc.), also purge its cache after flushing permalinks.
What Happens If Pro Is Deactivated
Section titled “What Happens If Pro Is Deactivated”Deactivating the Pro plugin does not delete your slug translation data — it stays in the database safely. However, with Pro inactive, Omnalingo no longer knows about your translated slugs, so:
- Frontend links revert to original slugs with a language prefix only
- Previously working translated URLs (like
/de/ueber-uns/) return 404 - The slug fields disappear from the editor
Reactivating Pro immediately restores all translated URLs and editor features without any data loss.
Common Issues
Section titled “Common Issues”Translated URL gives 404
Section titled “Translated URL gives 404”- Flush permalinks. Go to Settings → Permalinks → Save Changes. This is the most common cause and fix.
- Purge your caching plugin. If you use a caching plugin, clear its cache after flushing permalinks.
- Check that Pro is active. If the Pro plugin was recently deactivated and reactivated, the flush above should resolve any 404s.
Slug field not showing in the editor
Section titled “Slug field not showing in the editor”Confirm that the Omnalingo Pro plugin is active. The slug fields in the editor are added by Pro — they will not appear if Pro is not running.
Slug conflict warning
Section titled “Slug conflict warning”Another page in the same language already has the slug you entered. The warning message shows which page it is. Choose a different slug that is unique within that language.