Hello @lrkjaer,
Thank you for reaching out to us!
Regarding your first question, I just want to make sure I understand the situation correctly. When using TranslatePress, products are not duplicated for the additional languages. Instead, TranslatePress translates the content directly from the default language into the additional languages, string by string, and saves the translations in your local database, displaying them when the page is viewed in the additional language.
So translated pages still have their own URLs. For example, a product like:
website.nl/product/example-product
can become something like this in German:
website.nl/de/product/example-product
if the slug is not translated.
So German product titles and slugs can exist, but they are created by translating them in the Translation Editor.
If I have misunderstood the issue, please let me know and feel free to share a few more details about what you are trying to achieve. I will be happy to clarify further and guide you in the right direction.
Regarding your second question about the site structure:
You do not need to change your default language to English unless you specifically want English to be your primary content language. TranslatePress works directionally from the default language to the additional languages, so translating from Dutch → German, Swedish, etc. works perfectly fine.
Also, TranslatePress normally uses a subdirectory structure for languages (for example /de/ , /fr/ , etc.). If you eventually want to use separate domains per language (for example .nl , .de , .se ), this is possible using one of our Pro add-ons. You can find more details here:
https://translatepress.com/docs/developers/different-domain-per-language/
Unfortunately we are not allowed to speak more about the paid versions here. In case you would like to have that conversation, please open a support ticket using our site: https://translatepress.com/support/ask-a-presale-question/.
Let me know how it goes.
