True localization extends beyond the page body; it includes the URL structure itself. "Slug Translation" converts the semantic path of your links (e.g., /about-us) into the target language (e.g., /a-propos or /sobre-nosotros). This is critical for Multilingual SEO, as search engines prioritize URLs that match the user\'s search intent in their native language.
This guide details the configuration protocol, collision management, and routing logic for deep URL localization.
1. Enablement Protocol
Activate deep localization.
By default, MultiLipi attempts to translate slugs to maximize SEO. However, you should verify this configuration in your project settings.
Step 1: Access Project Settings
- •Log in to your MultiLipi Dashboard.
- •Navigate to Settings in the left-hand sidebar.
- •Select Project Settings from the sub-menu.
Step 2: Activate the Module
- •Scroll down to the Slug Translation section.
- •Action: Ensure the toggle is switched to
ON(Blue position).
The engine will automatically generate localized URLs for all new and existing pages (e.g., /contact → /contacto).
URLs will remain in English, even on translated pages (e.g., /es/contact).
2. Automated Topology Updates (Link Rewriting)
How the system handles internal navigation.
One of the most powerful features of the Slug Translation engine is Automated Link Rewriting.
The Mechanism:
When a slug is translated (e.g., /shop → /boutique), MultiLipi scans your localized pages for internal links pointing to the old URL.
The Action:
It automatically rewrites the tags in the HTML to point to the new, localized slug.
The Result:
Users stay within the localized ecosystem. A French user clicking "Shop" is taken to /boutique, not back to /shop.
3. Management: Manual Override
Precision control for URL keywords.
While our AI generates SEO-friendly slugs automatically, you may want to manually refine a URL to target specific local keywords or match a marketing campaign.
- •Navigate to the Translations section of your dashboard.
- •Locate the specific page row you wish to modify.
- •Click Edit Slug next to the URL preview.
- •Input: Type your preferred string (e.g., change
/productsto/boutique). - •Commit: Click
Save Changes.
Note: The system will immediately update the internal routing map to serve content at this new address.
4. Collision Management Protocol
Preventing routing conflicts.
In some languages, two different English words might translate to the same foreign word, creating a Slug Collision.
Scenario:
You have /store (retail) and /shop (verb). Both might auto-translate to /boutique in French.
The Risk:
Duplicate URLs confuse search engines and cause routing errors.
The Fix:
Use the Manual Override (Step 3) to differentiate them (e.g., keep /boutique for the store and use /acheter for the verb).
5. Legacy Redirect Strategy (301s)
Handling changes to live URLs.
If you decide to change a translated slug after Google has already indexed it (e.g., changing /fr/a-propos to /fr/notre-histoire), you must ensure users don\'t hit a 404 error.
Best Practice:
Set up a 301 Redirect in your underlying CMS (WordPress/Shopify/Webflow).
Workflow:
Redirect the old translated URL pattern to the new translated URL pattern to preserve your SEO "link juice."
6. Universal CMS Integration
Platform-agnostic routing.
Because MultiLipi operates as a proxy layer, slug translation works independently of your backend.
Supported Platforms:
WordPress, Shopify, Webflow, Wix, Squarespace, and Custom HTML.
No Backend Config:
You do not need to create these pages in your CMS. MultiLipi virtually maps the request /fr/boutique to your original /shop page while serving the translated content.