MBD.berlin

Thanks for the swift solution again, 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

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

Pim, I’m recently acquired the multisite extension.

Having installed all in one migration v5.23 and the multisite extension v3.3 i don’t find the form for filling in the htaccess credentials anymore.

Can you help?

Great Pim, looks as if I did not pay proper attention…

Thanks for opening my eyes and also a great WP Plugin!
-R

Just figured out that .htaccess access restriction was also the case for me – and though i read it only after finding out: Thanks Nicolas for sharing!

@pim: As this behaviour appears to be new since version 4.x – is there any hope this behaviour can be reverted?

Since your plugin is a great env migration tool for smaller websites and dev env often is behind .htaccess restriction, the manual workaround as also suggested by Nicolas is slightly painful.

And btw – what exactly is being requested from your(?) server that is breaking the export?

Thanks
-Rene