canonical domain and a domainname with german umlauts

[janvl]

Hi,

i get notifications from Google:

Alternative page with correct canonical tag
Duplicate - Google has designated a different page than the user as the canonical page

Now this is my first domain with an umlaut - kfz-müller.at which is translated to xn--kfz-mller-u9a.at

In the Sitemap manager the Links are all like xn--kfz-mller-u9a.at

Has anyone got an idea what has to be adjusted so Google and CMSMS handle these kind of Domains correct?
I would like the root_url to be kfz-müller.at should i put that in the config.php?

Regards,
Jan

[janvl]

Putting the root_url in helps, but the sitemap generated by "Sitemap Manager" produces Links with xn--kfz-mller-u9a.at.

I guess the Template must be adjusted. I am searching.

Regards,
Jan

[tomphantoo]

Snippets adapted from several online places:

Umlauts in domain names are translated by the browser into a so-called Punycode. An "xn--" is put at the front of the domain and other changes follow that.

A visitor to the website does not see this in the browser but this coding can sometimes become a problem. Not all browsers, operating systems, and applications necessarily support accented domain names in the same way, which can lead to compatibility issues in some cases.

Many email clients do not support umlaut entries, so the Punycode variations must always be used in these cases e.g. instead of emailing to "info@kfz-müller.at", the address changes to "info@xn--kfz-mller-u9a.at".

[janvl]

Thanks for your reaction.

I am already familiar with punycode and know the problems with e-mail.
Since the website mainly serves people living in this area a "umlaut-domain" could be usable as no E-Mail-addresses are used with this domainname.

Now i saw that google/bing/yandex can handle "umlaut-domains" for the search-engine but SitemapMgr does not produce them, i guess i will have to manually generate the right search-engine-sitemap what do you think?

Regards,
Jan

[tomphantoo]

I guess you're working with the SitemapMgr module, which is a bit out of date. But mere freshening of that might not help much, unless some new logic is applied, possibly in that module, or upstream of that.

It seems to me that the process for populating sitemap URLs for content pages goes something like this:
parse_url($_SERVER['PHP_SELF']) >> const CMS_ROOT_URL >> page-content-class::GetURL() >> Navigator node URL property >> sitemap URL

[janvl]

Thanks for the answer,

since this small website does not change much, i can produce a sitemap manually and adjust it to see if it works with "umlauts".
The module will be deleted. A pragmatical solution.

Regards,
Jan

[webform]

It shouldn't be necessary to delete the module and create a manual site map.
You can edit and change the template for Sitemap Pages in the Design Manager or create a new sitemap template.

[janvl]

Thanks,

i will check it again, it does not have a high priority.
It is still only 1 domain with an umlaut and i still have the domain without as well.
Regards,
Jan