Problem: The client is new to WPML automatic translation and Pay-as-You-Go services and encountered unexpected results in translation costs. The client noticed a significant difference between the word count shown in the Translation Dashboard and the actual credits used, making it difficult to estimate costs. The client asked for clarification on why the credits used are significantly higher than the expected word count, whether repeated content is charged again, and how to better estimate translation costs.
Solution: 1. Translation memory only takes effect for future translations and does not apply to translations sent in the same batch. Therefore, if the homepage and the paragliding page were sent in the same batch, the translation memory would not reduce the word count for repeated content. 2. For Divi global sections, it is recommended to first translate the global sections and then the pages using them to ensure translations are reused without extra charges. 3. The Translation Dashboard may not reliably apply translation memory for estimating word counts. A better approach would be to send the jobs directly to the Advanced Translation Editor (ATE) to see the actual word count that will be translated before applying automatic translation.
If these steps do not resolve your issue or the information provided here is outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
