Troubleshooting - Why is my website not fully translated, but only some parts?

In this article, you'll find the reasons why your website is not fully translated.

You selected a language with the Weglot button, and you noticed that some parts of your content were not translated. Here are 4 potential reasons that might cause this and the related solution:

1. Number of words

Check your number of translated words in your Weglot dashboard under "Plan Usage". 

If you see "Quota Exceeded", it means you have reached the limit of the total translated words within your current Weglot plan.

To make sure all your website content is translated, you can upgrade to the next plan by going to your Weglot account, clicking on Billing > Upgrade, and selecting the next Weglot plan as well as your billing frequency. 

2. Excluded content

Check if you already excluded the untranslated part directly in the Weglot settings in your Weglot Dashboard > Settings > Translation Exclusions

If you excluded that part, remove the corresponding block by clicking on the trash icon and refresh your website.

3. Exception rules

Check if you have an exception rule that could apply to the untranslated part directly in your Weglot Dashboard > Translations > Glossary

If it's the case, remove this rule and refresh your website.

4. Javascript content

Check if JavaScript generates the untranslated content. 

This is often the case for dynamic content, previews of products, or blog posts. Go here to know if your content is generated by Javascript.

5. Pending translations

Check if you have the pending translation activated in your Dashboard > Settings. 

When the pending translation option is activated, all the new translations will be stored in your Translation List.

You can access the pending translations by clicking the button action > View pending translation.

To display the new translations, you need to approve them. And after a refresh on your website, the content will appear.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us