This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported that translated pages were not appearing in their sitemap.
Solution: We recommended checking if the WPML SEO plugin was installed and active, which helps with sitemap generation. If the issue persisted, we asked for an example of a missing translated page/post and the Debug Information from WPML > Support. After the client updated the pages using the Gutenberg editor, the sitemap refreshed and included the previously missing pages. This suggests that a caching mechanism might have been holding an outdated version of the sitemap. We also checked the settings by toggling the no-index and no-follow options for the pages, which confirmed that the sitemap was updating correctly.
If you're experiencing a similar issue, we recommend: 1. Ensuring the WPML SEO plugin is installed and active. 2. Updating the pages using the Gutenberg editor to refresh the sitemap entries. 3. Checking for any caching mechanisms that might be affecting the sitemap. 4. Providing Debug Information by following the instructions here.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket here.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
In summary, these are the steps that you need to take in order to retrieve it:
- Go to WPML > Support > Debug Information
- Copy the Debug Information from there.
- Find the “Additional Data” section below this chat.
- Click on the “Debug Info” item to expand it.
I'm enabling the Debug Info template for your next reply.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello,
Thank you for sharing that info.
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
I'm glad to hear that your sitemap issue has been resolved. After reviewing your described actions and the outcomes, it seems that updating the pages in the Gutenberg editor and then seeing the pages appear correctly in your sitemap likely refreshed the sitemap entries. This kind of issue is often related to caching mechanisms or temporary misconfigurations that can prevent new or updated content from appearing as expected.
While it's challenging to pinpoint the exact cause without observing the issue live, it's possible that a caching layer (either within your WordPress setup, a plugin, or at the hosting level) may have temporarily held onto an older version of your sitemap. Updating the pages likely invalidated the cached version, prompting the system to regenerate the sitemap and correctly include the updated content.
I went ahead and checked your settings, temporarily enabled the option no-index and no-follow for both pages that you shared previously and they were properly removed from the sitemap. Then, upon disabling the no-index and no-follow options and regenerating the sitemap the pages were correctly added to the sitemap again, so everything looks OK at the moment.
I'm afraid that in order for us to dig deeper into this issue, it'd be necessary to replicate it to help us debug and find the culprit.
But hopefully it's not going to be necessary as long as the sitemap remains fully functional.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello,
I went to the RankMath settings, accessed the sitemap section, disabled the sitemap for the pages and saved it. Then I refreshed the page, re-enabled the sitemap for pages and saved the settings.
That forced the sitemap to be recreated with all current pages.
