Problem: You are trying to translate products on your site using WPML and find the new product translation method, which requires assigning translators, unsuitable for your needs. You prefer a method where every admin can translate content directly without needing to be assigned as a translator. Solution: If you're experiencing this issue, we recommend the following steps: 1. Ensure that the classic translation method is selected in WPML. This can be done by navigating to WPML -> Translation Management and checking the settings. 2. If you want administrators on your site to translate products directly, they should go to WPML -> Translation Management, select the products, and assign them to themselves. 3. Alternatively, you can translate products by editing a product in the original language and then clicking on the translation icon that appears in the right column under the Languages block.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket.
Problem: The client is concerned that the 'fallback to default language' setting in WPML for untranslated pages and posts might cause Google to penalize their site for duplicate content.
Solution: We reassured the client that using the 'fallback to default language' option does not negatively affect SEO. WPML communicates with Google to ensure that the default content is recognized, and Google will ignore the same content on secondary language pages. Once a post or page is translated, Google will index it as new content, not a duplicate. For more details, the client can refer to our documentation on Displaying Untranslated Content on Pages in Secondary Languages.
If this solution does not apply or is outdated, or if the client is facing a different issue, we recommend opening a new support ticket. It's also advisable to check the related known issues, verify the version of the permanent fix, and confirm that the latest versions of themes and plugins are installed.
