You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened
The duplicated language pages of the WPML are added to the sitemap, even though those pages are added with canonical URLs pointed to the original content page. Due to this, SEO tools like ahrefs and others show this an issue as the URLs of non-canonical pages are added to the sitemap.
To Reproduce
Step-by-step reproduction instructions
Make sure that WPML and WPML SEO plugins are installed and activated on the website
Check the source code of duplicate created language pages; then, you can notice that the canonical URL is pointed to the original content page. Right now, the Yoast and WPML are working correctly, as the content is an exact copy of the original page.
But when we check the sitemap of Yoast generated, we can notice that the duplicate created language page is added to the sitemap, which should not be there as the canonical URL is pointed to another page (the page from which the duplicate page is created).
Expected results
The duplicate created language page with a non-self canonical page should not be added to the sitemap.
Or, the expectation would be like the following if we can enhance it this way:
When duplicating a page using WPML, Yoast SEO shall use the canonical pointing to the original page. So, the duplicated page will not appear in the sitemap.
When the duplicated page content is modified using a different language, the canonical on the relevant page shall point to self-canonical. So, the duplicated page will now appear in the sitemap.
The duplicate language page is outputted within the sitemap and the SEO tools like ahrefs may report this more in the future, and the crawl budget may be required more as Google notices these URLs within the sitemap.
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording, or a code snippet that demonstrates the bug.
Technical info
If relevant, which editor is affected (or editors):
Block Editor
Gutenberg Editor
Elementor Editor
Classic Editor
Other:
Which browser is affected (or browsers):
Chrome
Firefox
Safari
Other:
Used versions
Device you are using:
Operating system:
PHP version:
WordPress version: 6.4.3
WordPress Theme:
Yoast SEO version: 21.7
Gutenberg plugin version:
Elementor plugin version:
Classic Editor plugin version:
Relevant plugins in case of a bug:
The text was updated successfully, but these errors were encountered:
For me, it’s still unclear whether the canonical tag on the duplicate translated page should point to the original page or to itself. Currently, the canonical points to the original page, and this happens even when Yoast SEO is disabled. According to what was discussed here, the canonical on the duplicate translated page should point to itself, even if the content is identical (the menus on the page could be different).
That said, if the canonical tag on the translated page points to somewhere else (i.e. original post), I’d expect the translated page to be excluded from the sitemap, and this is currently not happening.
Please give us a description of what happened
The duplicated language pages of the WPML are added to the sitemap, even though those pages are added with canonical URLs pointed to the original content page. Due to this, SEO tools like ahrefs and others show this an issue as the URLs of non-canonical pages are added to the sitemap.
To Reproduce
Step-by-step reproduction instructions
Make sure that WPML and WPML SEO plugins are installed and activated on the website
Create a new post and click on the Duplicate page option provided by WPML (https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/) for the creation of other languages
![duplicate](https://private-user-images.githubusercontent.com/34977009/293639664-a04f7ef0-a2c7-4dfc-96ad-cb01921d3d2d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1Njk1MTAsIm5iZiI6MTcyMDU2OTIxMCwicGF0aCI6Ii8zNDk3NzAwOS8yOTM2Mzk2NjQtYTA0ZjdlZjAtYTJjNy00ZGZjLTk2YWQtY2IwMTkyMWQzZDJkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA5VDIzNTMzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU3MGVhMjQ0MzBjOGMxMzA1NDQ3YmUyNTNhZmJjYjA3NWIxZTE4NzMwNjA3MDM0MWE5OTNhZjI3OTY4MTA0ZGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.sfqDdAgvFr_Gfzv3FbhgLa3QYWDMhcZmw3BmTXVRuX8)
Check the source code of duplicate created language pages; then, you can notice that the canonical URL is pointed to the original content page. Right now, the Yoast and WPML are working correctly, as the content is an exact copy of the original page.
But when we check the sitemap of Yoast generated, we can notice that the duplicate created language page is added to the sitemap, which should not be there as the canonical URL is pointed to another page (the page from which the duplicate page is created).
Expected results
The duplicate created language page with a non-self canonical page should not be added to the sitemap.
Or, the expectation would be like the following if we can enhance it this way:
Slack conversation with more details: https://yoast.slack.com/archives/C02D43TFT/p1666101600499169?thread_ts=1666081013.387359&cid=C02D43TFT
Actual results
The duplicate language page is outputted within the sitemap and the SEO tools like ahrefs may report this more in the future, and the crawl budget may be required more as Google notices these URLs within the sitemap.
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording, or a code snippet that demonstrates the bug.
Technical info
Used versions
The text was updated successfully, but these errors were encountered: