Recommend not to use
-
Hi,
We are sorry to hear that you have had such a non-positive experience.
We could not locate your account with your username and do not quite understand what issue you encountered.Please contact our team at?[email protected]?so our team members can discuss your concerns in more detail.
You can ask for Chris, our Head of Support, so he can personally take care of your demand and help you improve your experience with our plugin.Best,
The Weglot Team
Hey, your support is really bad or maybe HR is not doing good job. You asking 150+ EUR for what? Scammers
- This reply was modified 1 year, 8 months ago by matejem.
Hi Matej,
Thanks a lot for your message.
I’ve found the conversation you’re currently having with one of our support members, and I’ve just sent you a message to try to help you further.
1.?About the slow translated pages
The load time can be longer the first time Weglot translates the content, and then be way better on the second visit to the page.Indeed, Weglot translation mechanism is working like this:
- It scans the original content of your website (HTML file)
- After the scan, Weglot parses (read and cut) the elements between HTML tags.
- It automatically translates this original content to its translated equivalent.
- During the translation process, Weglot is also storing these contents in your Translation List available in your Weglot Dashboard
The translation is made server-side in order to allow the translated versions to be translated for SEO purposes.
?Solution => Are you currently working with a cache plugin on your website? If you do, could you let me know which cache plugin are you currently managing?
?If you don’t, could you try to install a cache plugin and check on your website if it seems to work better with the cache system?
?2.?About the generation of ?automatic translations, be aware that?Weglot generates a translation every time it meets new content, that’s why it’s able to translate your whole website in a few seconds/minutes.
Weglot matches a translation with specific original content.??Translations are generated and added progressively to your?Translation List?when someone visits your website in the translated language.?Weglot proposes a solution to stop translating specific content on your website by excluding blocks or URLs from translation.
It means that the excluded content won’t be translated at all.– Exclude Blocks –
If you want to exclude a specific part of your website, go to your Weglot Dashboard > Project Settings (Exclusions) > Exclude block section.
There, you can paste the right CSS selector of the block you want to exclude.To find the CSS selector:
– Right-click on the element you want to exclude
– Go to “Inspect”
– Use the arrow on the top left of the console
– Click on the element you want to exclude
– Copy the class or the id of this element.
– Go to your Weglot Dashboard > Project Settings (Exclusions) Exclude Blocks field
– Paste the class (add a dot before the class) or the id (add a # before the id) in the tiny box, then click on “Add”
– Save your changes– Exclude URLs –
If you want to exclude URLs, you can do it directly from your Weglot Dashboard > Project Settings (Exclusions) > Exclude URL section.
Only add the relative URL of the page that you want to exclude.
For instance, if your page is https://www.mywebsite.com/page1/, only add the relative URL: /page1 (with the status “Match Regex” or “Contains”)we’re pleased to send you the documentation regarding the exclusion with Weglot
See >?How to exclude URLs/blocks/words from translation??? I can notice that you deleted your project.
?If you can let us another chance, we’ll be really glad to help you further with the exclusion of content you no longer want to translate.
?How can we improve the experience you had with our plugin?
?
?Don’t hesitate to come back to us directly in the email thread at [email protected] so we can help you further.
Wishing you a wonderful day,
The Weglot Team
- The topic ‘Recommend not to use’ is closed to new replies.