Problem: After migrating a website from Wedos to Hostinger, the client reported that WPML lost the connection between many original posts and their translations. The translations exist in the database but are not linked in the WPML dashboard. Additionally, there are "ghost" redirects between unrelated languages, such as a request for a Chinese page being redirected to a Portuguese page. Solution: We first verified that the translations were not done using the Advanced Translation Editor (ATE) and confirmed that no domain migration was involved, only a hosting change. We suggested checking if some translations were manually created or modified directly in the WordPress editor, which might cause them to appear empty in the WPML Translation Editor. We recommended the client to go to WPML --> Support --> Troubleshooting and click on "Fix element_type collation". If the issue persists, we asked for specific URLs where the problem is visible, exact steps to reproduce the redirect, and additional details such as whether the issue occurs while logged in or in incognito mode, and if it happens after a specific action.
Please note that this solution might be outdated or not applicable to your case. We highly 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing SEO issues with their multilingual WordPress site using WPML. Over 530 URLs are being indexed as 'Pages with redirect' due to WPML-generated multilingual slugs, which either redirect (301) or are empty, yet are included in sitemaps and crawled by search engines. The client is concerned as these URLs are from untranslated or fallback language pages and wants to prevent them from being indexed.
Solution: We clarified that WPML does not generate URLs for untranslated content. It's likely that these URLs are being auto-generated by WordPress itself. We recommended checking the database to see if such pages exist. If they do not, it might be WordPress generating these URLs. We suggested looking into the WordPress function wp_guess_url and considering disabling it to see if this resolves the issue.
We also confirmed that WPML never had an SEO option to 'Hide content that is not translated in search results.' The issue of URLs like /ar/联系我们/ appearing is not from WPML, especially since the default language is English. It's likely that these 'fake' URLs are coming from WordPress's URL auto-guessing feature.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly 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 problems persist, please open a new support ticket.
Problem: The client is experiencing critical performance issues with WPML on their multilingual site, including high Time To First Byte (TTFB) and additional database queries. They have tried various optimizations but the issues persist. They also face SEO issues with WPML-generated multilingual slugs being improperly indexed by Google. Solution: We recommend setting up a staging site to safely test changes without affecting the production environment. Follow these steps: 1) Install the Query Monitor plugin from https://wordpress.org/plugins/query-monitor/ 2) Monitor the load time and number of queries using the tool provided by the plugin. 3) Disable all WPML plugins and check the load time and query count again. 4) Disable all other plugins, activate only WPML plugins, and switch to the WordPress default theme to isolate the issue. Please report back with the results of each step.
If this solution does not resolve the issues or seems outdated, we highly 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client was unable to activate the editor for managing translations on other languages after making changes to a page. Additionally, Google was not indexing the pages with the translated languages. Solution: 1. We first asked the client to clarify what they meant by 'the editor to manage the changes on other languages is not active.' This was to ensure we fully understood the issue. 2. We suggested that the issue with Google not indexing the translated pages might be related to the SEO plugin. We recommended contacting the SEO plugin support team for further assistance. 3. Upon further investigation, we identified it as a known issue on our end and confirmed that we had resolved it. We asked the client to recheck the translations. 4. We discovered an extra marker in the translation that was causing issues and removed it to ensure the system worked correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing automatic 301 redirects on all translated pages of their multilingual website, redirecting each non-English page to its English counterpart despite the 'Redirect visitors based on browser language' option being disabled in WPML settings. Additionally, translated pages are automatically assigned a slug ending with -2, even though no duplicates exist. Solution: For the issue of 301 redirects, it appears that the redirects are expected behavior when accessing the default language page directly. The Italian version of the page should be accessed via its correct path, which includes the language directory, e.g.,
https://caalvise.com/it/contatti/
. This should resolve the indexing issues as the correct URLs will be accessed. Regarding the slug issue with '-2', it was identified that there is indeed a page with the original slug 'hotelsinvenice' on the site. The client can edit this page directly by accessing https://caalvise.com/wp-admin/post.php?post=87801&action=edit&lang=en.
If these solutions do not resolve your issues or seem irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client needed assistance with updating links on translated pages and synchronizing menus across different languages using WPML. Solution: 1. We advised the client to follow the steps described in our guide for translating menus, which can be found here: Translating Menus Documentation. 2. We confirmed that the actions described would synchronize the menus as intended. 3. We emphasized the importance of creating a full site backup before making any changes to ensure that the client can restore the site if necessary.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
