TYPO3 Core

Do I get it correctly that you want to pass your tracking params to the other languages by adding them to the hreflang? Why do you want that? That information is not relevant for a search engine isn't it?

No, I don't want to show the hreflang, if the canonical is different than the current URL.

Why do you want that? I can't get the reason why you would like to hide the hreflang while it is showing the right URL. Hreflang and canonical will be using the canonicalized url's, just like they are needed for the search engine. Maybe I don't understand your issue. Can you clarify?

Maybe you can get the point here better https://www.searchviu.com/en/hreflang-canonical/ but I also descriped it in the description of this ticket.

Another example.

mypage.com/page/ => canoncical mypage.com/page/ => hreflang mypage.com/de/page/
mypage.com/de/page/ => canoncical mypage.com/de/page/ => hreflang mypage.com/page/
is ok.

mypage.com/page/?param=xyz => canoncical mypage.com/page/ => hreflang mypage.com/de/page/
mypage.com/de/page/ => canoncical mypage.com/page/ => hreflang mypage.com/de/page/
missing the way back to mypage.com/page/?param=xyz - every hreflang has to point to itself

mypage.com/page/?param=xyz => canoncical mypage.com/page/ => hreflang mypage.com/de/page/?param=xyz
would be even more worse.

So sorry to hijack your post but where do you put this in Typo3?

hreflang
<link rel="alternate" hreflang="en" href="https://www.domain.org/home/&quot;/>

Thank you,

Marc Hirdes wrote:

Hi,

I currently struggle with hreflang and tracking params. They will not be shown in the hreflang, but then they will have a lost connection. hreflang should allways refer to each other. Otherwise there will be shown an error in the Google Search Console.

my question is, if we have page like for example /home/.

The canonical is
https://www.domain.org/home/

The href-lang is
<link rel="alternate" hreflang="de" href="https://www.domain.org/de/start/&quot;/>

Everything is ok. On https://www.domain.org/de/start/

the canonical would be
https://www.domain.org/de/start/
and the hreflang
<link rel="alternate" hreflang="en" href="https://www.domain.org/home/&quot;/>

If my page is in the Google index with
https://www.domain.org/home/?my_tracking_parameter=xy

Then also the canonical and href lang would be the same as above, so without the parameter. For the canonical this works, but for the hreflang not. There would be a missing conection from https://www.domain.org/de/start/ to https://www.domain.org/home/?my_tracking_parameter=xy

Therefore the hreflang sould not be set if the canonical is a different than the current URL. But then we have the challange with the page cache. So https://www.domain.org/home/?myparameter=xy would have the same cached page as https://www.domain.org/home/.

My only solution for this problem would be to use the sitemap.xml for hreflang instead of the HTML head, as it is shown here https://support.google.com/webmasters/answer/189077#sitemap

What do you think about?

The problem is, that the addQueryString option just adds all the params it can find.
Marc suggests to disable the hreflang generation, if the requesting url is already wrong. This could be a workaround, but i'd opt for cleaning up the typolink mess in that case.

We have this problem as well in multiple projects: to reproduce, simply clear the cache and request a page with ?foo=bar
The HrefLangGenerator uses the LanguageMenuProcessor -> addQueryString kicks in and screws up the links.
I also get the param added to the the canonical url, maybe Marc can doublecheck his setup.

To get rid of THIS problem, i installed https://github.com/sourcebroker/urlguard: this xclasses the ContentObjectRender and extends the addQueryString stuff.
Now i have to include "simple" params like "foo=bar" that i want to keep, params in an extension namespace are automatically included. All other params are automatically dropped.

Having to manage a list of params that should not screw up your caching and link generation is just a dead end, also the hreflang entries can not simply be rendered with the LanguageMenuProcessor. See #89648 as well, that we need a better and more configurable way to control the params that should end up in these urls.

The problem is not addQueryString. This can be solved via the canonicalParameter Settings.

The problem is, if a page has a hreflang, all hreflang should also point to the current page (the back links). I don't know how to describe it otherwise as in the examples above, but one last try.

If my current URL links to another page via hreflang, then on the other page has also be link to the current page.

So if my url is mypage.org/?param=abc and my hreflang is mypage.org/en/, then in theorie on the mypage.org/en/ has to be a hreflang with maypage.org/?param=abc. That is not the case, if the param=abc is not in my canonical parameter list. That is totally ok, to exlude parameters, but if this the case, then the hreflang should not be set, because there is no back link to the current page.

I hope you now get the point. Otherwise we can also write via slack.

I get your point. Only thing is that I'm not sure if this is really the best practice. Will check it with the people of Yoast.

BTW, if this is wrong behaviour, at least Disney is doing this wrong as well: https://disney.de/?foo=bar

Thanks Richard for your feedback and thanks even more for the PSR-14