Did this ever get picked up?
Hi there, @user31561 and welcome to the Community 
Do I get it right that the widget language option additionally translate the original website content to the same language? If so, could you please share a link to the page, where your widget is installed?
1 Like
Yes, that’s right. From what I have experienced, the issue doesn’t occur on the user’s first visit, but when switching from the original site language to another language and then back again. In those cases, the widget occasionally translates parts of the original content incorrectly.
After revisiting the page, the lang parameter remains in the URL (I assume via cookies or some local storage). Ideally, selecting the original/default site language should remove the lang parameter entirely and revert to a clean URL.
Site URL in question: kjobinghus.com.
I considered removing the default language from the list of languages in the widget, which solves the issue on the surface as you can’t revert to the original language, but is misleading for the user if using a dropdown style widget.
2 Likes
Hi there, @user31561
Thanks for sharing the link!
I’ve checked the content on your site, and I don’t see any difference in the text between the original version and what you see after switching back to Dansk.
Just to make sure I’m understanding correctly: the text looks the same for you too, and the only issue is that the URL gets ?lang=da added after switching back. It doesn’t affect the translation — you’d just like that parameter removed. Is that right?
1 Like
Hi Max,
After receiving some examples and details from my client, it seems to be an issue specifically when English is used (a lot of words used in Danish are borrowed directly from English). The button text on the screenshot attached should read “Galleri” and “Book nu” but instead gets translated. So, I guess the issue is when other languages are mixed in the default language. The original language and Danish words appear fine. Either that or it is a problem with translation on link elements, as the link text on the other screenshot attached are also not the default.
I know you have the word exclusion could work for this, but a default language feature would be a lot cleaner and avoid any unintended weird translations.
1 Like
And yes, removing the parameter would give a cleaner look, but I am more concerned about the translations
2 Likes
Got it, thanks!
The page should not be translated back to the original language if the HTML lang tag of the default website’s language matches the language set in the widget. Here’s an example of how it should look:
Your website previously didn’t have this attribute to set Danish as the default language. To fix this, we added it using the following script in the Custom JS field on the Settings tab of your widget’s settings:
document.documentElement.lang
With this code in place, the page will no longer automatically switch back to Danish when switching between other languages.
2 Likes
Thank you so much! 