Errors in hreflang tags

Hi,

it seems as if Google changed something, and now does not recognize URLs like https://example.com/?noredirect=en_US as before, and only looks for (and accepts) https://example.com/ without any query variables. We will have a look at this, especially as you’re, unfortunately, not the first to report this.

Kind regards,
Thorsten

Hey Thorsten,

any news so far? We’re facing the same issues here.

Thanks in advance,
Peter

Hi Thorsten.

It is not really the case that Google “changed something”, probably just the Search Console is now reporting it: https://plus.google.com/+JohnMueller/posts/17fbv5phpks

Why don’t you just make the parameter optional? It appears highly unnecessary especially when automatic redirection is deactivated, but creates a potential conflict with rel-canonical markup.

Best
Rene

Hi all,

the hreflang links (as well as the headers) have been fixed.

A release will follow (very) shortly.

@mbd.berlin the noredirect parameter doesn’t belong into the URL used in hreflang contexts – that has been fixed now. But it should not be there (the noredirect parameter) if you don’t use the automatic redirect. Is this the case for you?

Kind regards,
Thorsten

Hi Thorsten

thanks for the swift reply & update!

Yes, the parameter also appeared in the hreflang elements before the update

<link rel="alternate" hreflang="de-DE" href="https://xxx/de/?noredirect=de_DE">
<link rel="alternate" hreflang="en-US" href="https://xxx/">

and now seems fixed with the current version of your plugin:

<link rel="alternate" hreflang="de-DE" href="https://xxx/de/">
<link rel="alternate" hreflang="en-US" href="https://xxx/">

Thanks again
Rene

Thanks!