lelantus

MegaMuc,

I was able to migrate my website from qTranslate-x to WPML and that got my google search results back to normal. Below is the post I had put on my own tread about this.

If anyone ever finds a way to modify the Hreflang tags that are automatically created by the qTranslate-x plugin then you wont need to migrate, but I could not figure it out.

“For anyone else who has this issue. The root cause has got to be the Hreflang tags generated by qTranslate-x. I have made a local copy of my site and used WPML and their qTranslate X Cleanup and WPML Import plugin to successfully migrate from qTranslate-x to WPML with minimal work required.

Some page titles may also be lost and will just show the language that was there (en). Menus, Widgets, Posts, Pages and any other custom fields stored in WordPress may need to be fixed slightly for language tags or lost titles.

I am waiting for my webhost to upload my site and switch it live by the end of the week. Ill report back if there are any issues with google not resolving to the new Hreflang tags. But I can already see that my website Hreflangs are now correctly pointing my primary language EN to https://www.domain.com instead of https://www.domain.com/en, sublanguages are pointed to https://www.domain.com/lang=?”

-and this worked.

For anyone else who has this issue. The root cause has got to be the Hreflang tags generated by qTranslate-x. I have made a local copy of my site and used WPML and their qTranslate X Cleanup and WPML Import plugin to successfully migrate from qTranslate-x to WPML with minimal work required.

Some page titles may also be lost and will just show the language that was there (en). Menus, Widgets, Posts, Pages and any other custom fields stored in WordPress may need to be fixed slightly for language tags or lost titles.

I am waiting for my webhost to upload my site and switch it live by the end of the week. Ill report back if there are any issues with google not resolving to the new Hreflang tags. But I can already see that my website Hreflangs are now correctly pointing my primary language EN to https://www.domain.com instead of https://www.domain.com/en, sublanguages are pointed to https://www.domain.com/lang=?

The problem is in the hreflang tag from the plugin. DE is pointing directly to .de/de instead of leaving it as .de

<link hreflang="de" href="https://www.wordup.de/de/" rel="alternate">
<link hreflang="en" href="https://www.wordup.de/en/" rel="alternate">
<link hreflang="x-default" href="https://www.wordup.de/" rel="alternate">

If you find a way to edit the hreflang for DE to point directly to https://www.wordup.de/ please let me know as I am having the same issue.

Google must have decided to follow hreflang tags with their bots rather than just follow the default for languages that are specified in the hreflang’s.

Yes WE. There are at least 2 other threads right now all with the same issue.

Where has the author of this plugin gone? The main site has shown unavailable for months now. The only pages still working are from wordpress and github.

No. This is an issue generated by the plugin. The correct setup is to have EN language go to .com and ES language go to .com/es. There are only 2 languages. And the plugin is generating 3 hreflang codes that points EN to .com/en, ES to .com/es and leaves default to go to .com. This code is not correct.

Obviously google has made a change in recent months that it now more closely examines the hreflang based on location. This means we need to plugin to change to show the default language as .com as it is supposed to do.

If I turn off the hide url for default language then my website will show .com/en in the actual url. I do not want the /en anywhere in my website.

I already have the hide url for default language option turned on.

the plugin is creating these three lines of code in my header.

<link hreflang="en" href="https://www.domain.com/en/" rel="alternate">
<link hreflang="en" href="https://www.domain.com/es/" rel="alternate">
<link hreflang="x-default" href="https://www.domain.com/" rel="alternate">

This is wrong, the hreflang needs to point directly to .com.

If the hreflang tags require that all languages have a hreflang, then we just need to point .com/en for en hreflang to instead be .com for en hreflang. How can we edit that code?

The fact that from a Spanish location it is showing up as /es means that the hreflang tags that are being generated from the plugin are not meeting google’s requirements. I suspect that the appropriate way to list the hreflang is just to have default and es and there should not be any hreflang for the en.

Do you know what file contains the code that is generating the hreflang lines of code?

Could this be because of the hreflang rules are setup for en and es and default? So visits from a EN-US location are defaulting to en despite the Default-x rule? But visits from dutch are directly taking the Default-x.

We have disabled our cache plugin today. But I am uncertain if this is the root cause.

Thats very odd, bing is correctly showing just .com…

• This reply was modified 8 years, 2 months ago by lelantus.

Hi Terry,

I checked using Startpage, i see it as /en. Please see the screenshot https://imgur.com/nQs4HIX

Hi Terry,

we noticed that too, our issue is when googling “ivfmd” that the results are shown with /en.

Hi Terry,

its https://www.ivfmd.com (will likely redact later).