I am reaching out to seek resolution for a couple of issues I've encountered after updating the default language settings on my website using the WPML plugin.
I have recently made some changes to the language configuration of my website. The old default language was English with the URL mywebsite.co. I've added Australian English as a new language and set it as the new default, now accessible at mywebsite.co/au. Following this update, I have experienced the following issues:
Language Tags and Category URLs: Post-update, I've been unable to manage the language tags and category URLs for the new default language. Despite setting Australian English as the default, the tags and category URLs are not reflecting this change and continue to display as if in the previous default language.
Canonical Tag Confusion: Initially, the blog posts were published in the default language (English) and other languages used canonical tags that pointed back to the default language URLs. However, after the introduction of the new default language, certain blog posts that should only index in Australian English are now also indexed in other languages with their canonical tags inappropriately pointing to the new self blog page instead of the original AU English content.
I would appreciate your guidance on the following:
1) How to effectively manage language-specific tags and category URLs for the new default language in WPML?
2) How to correct the canonical tags so that all non-default language content appropriately references the original content in the default language?
I suspect these challenges are a result of the changes to the default language settings, possibly combined with a misconfiguration within WPML. I would be grateful if you could provide a step-by-step solution or any additional support to rectify these issues.
Thank you for your attention to this matter, and I look forward to your prompt reply.
Following our recent discussions, I tried to solve the issue we've been facing with our multilingual blog posts, but unfortunately, I haven't been able to resolve it successfully.
The primary concern is that our main blog posts are published in the primary language (/au) and are not published in other languages (/in , /sg, /ph ). These other language versions are being indexed but lead to duplication issues. This is happening because the alternate language blog posts are incorrectly setting the canonical tag to reference their page rather than pointing to the main language blog post.
Furthermore, a similar problem with our tag and category pages, maintaining the previous default language setting, which compounds the issue at hand.
by your expertise, I thought it advisable to bring this to your immediate attention. A quick review from your end might shed some light on the root cause and potentially guide us toward a viable solution.
I appreciate your timely input on this matter and look forward to your suggestions.
Previously, our parent language blog was located at mywebsite.co/blog-slug. However, as part of our efforts to enhance user experience and better organize our content, we've made some adjustments.
Now, after adding a new language blog, the URL for the parent language blog has been modified to mywebsite.co/au/blog-slug. This change allows for better categorization and navigation, especially for users who prefer content in a specific language.
To facilitate this transition, we've also made adjustments to the default locale settings. The default locale for the old parent language has been changed to 'en', while 'au' has been set as the new default language. These changes aim to streamline the browsing experience and ensure that users can easily access content in their preferred language.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
The language directory inside the site's URL is coming from the language code and the default language code here was "en".
You need a custom language to use a language code like "au".
I need to ask this again, as you did not answer my question.
The posts and their categories were created while the site was using "en" as language code?
If so, then take note that all original content is registered on the WPML language and translation tables with language code "en" and there is not way to undo this.
You can not convert such existing "en" content to have the source language code "au". The "au" post in this case would always be translations of the original "en" posts.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
The topic ‘[Closed] Assistance Required with WPML Plugin Translation and URL Issues’ is closed to new replies.
