TranslateWP does not translate URL slugs, does not let you pick the AI model, and has no translation editor on the free plan. Translated pages still get their own language folder, hreflang and canonical tags on every plan. Orbital (Pro) adds a front-end editor and lets you use your own AI provider keys.
What is and is not included?
| Feature | Terrestrial (Free) | Orbital (Pro) |
|---|---|---|
| Translation editor | No | Front-end editor; corrections kept until the original changes |
| Language folders (/de/about/) | Yes | Yes |
| hreflang with x-default | Yes | Yes |
| Per-language canonical tags | Yes | Yes |
| Translated URL slugs | No | No |
| Translated sitemaps | No | Yes |
| Choose the AI model | No | No; add your own AI provider keys instead |
Can I edit a translation?
The free plan has no translation editor. Use the Lexicon and translation settings to guide future results. With Orbital (Pro), the front-end editor lets you correct any translation on the page, and your correction is kept until the original text changes.
Are URL slugs translated?
No. Every translated page has its own language folder, such as /de/about/, and older ?lang= links redirect permanently to it. The page slug stays in your original language.
Can I choose the AI model?
TranslateWP chooses the AI model for your plan. With Orbital (Pro), you can add your own AI provider keys and set the order they are used in, for the whole site or per language.
Feature questions
Do untranslated slugs hurt SEO? Search engines use hreflang and canonical tags to match language versions, and TranslateWP adds both on every plan. See Google’s guide to localized versions.
Will slug translation be added? Yes, translated slugs are planned. Today, a translated page keeps your original slug inside its language folder, such as /de/about/.