My website has only one locale defined in the backend.
This raises the question of the need for the Winter.Translate plugin, but it's required by one of my other plugins (OFFLINE.MALL).
The problem is that the sitemap generated prefixes all URLs to CMS pages with the language (e.g. http://mywebsite.tld/fr/rendez-vous) even though these pages don't exist in any other language.
This generates duplicate content and canonical URL problems for search engines, as the page is accessible with the URL /rendez-vous and defined in the sitemap as /fr/rendez-vous.
In this case, the sitemap also proposes an alternative link which is the same as the main one.
Couldn't the localized and alternative link generation be conditional on having at least two locales defined in the site parameters?
My website has only one locale defined in the backend. This raises the question of the need for the Winter.Translate plugin, but it's required by one of my other plugins (OFFLINE.MALL).
The problem is that the sitemap generated prefixes all URLs to CMS pages with the language (e.g.
http://mywebsite.tld/fr/rendez-vous
) even though these pages don't exist in any other language.This generates duplicate content and canonical URL problems for search engines, as the page is accessible with the URL
/rendez-vous
and defined in the sitemap as/fr/rendez-vous
. In this case, the sitemap also proposes an alternative link which is the same as the main one.Couldn't the localized and alternative link generation be conditional on having at least two locales defined in the site parameters?