This is the Google Webmaster Tools complain:

"Google has detected that some pages on your site have implemented the rel-alternate-hreflang tag incorrectly. In particular, there seems to be a problem with incorrect language and region codes, or incorrect bi-directional linking (if page A links with hreflang to page B, there must be a link back from B to A as well). Google uses the hreflang attributes to serve the correct language or regional URL to the right users in search results. Until you correct the errors on the hreflang links, your website will not benefit from additional language or region targeting."

This happens because the hreflang metatag does not appears on the localized nodes. Any help?

Comments

carlos.macao created an issue. See original summary.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

Can you please show me what meta tags are on the original vs the translated node? What are you using for handling the translations - Content Translation or Entity Translation?

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Issue tags: -hreflang metatag +hreflang
carlos.macao’s picture

carlos.macao CreditAttribution: carlos.macao commented

Hi Damien,

Original Node:

<link rel="alternate" href="http://ana-macao-kw.pt/oeiras-golf-residence-moradia-t8-luxo" hreflang="pt-pt" />
<link rel="alternate" href="http://ana-macao-kw.pt/en/oeiras-golf-residence-luxury-villa-v8" hreflang="en" />

Translated node:
No hreflang metatag.

What are you using for handling the translations - Content Translation or Entity Translation?

Both.

carlos.macao’s picture

carlos.macao CreditAttribution: carlos.macao commented

Any news?

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Related issues: +#2832101: hreflang tokens should support Content Translation

In #2759461: x-default is omitted instead of hreflang when URLs match I fixed a problem with it deleting the x-default meta tag, please test out the latest 1.18 release and let me know if the problem persists. Content Translation will be worked on in a separate issue: #2832101: hreflang tokens should support Content Translation

carlos.macao’s picture

carlos.macao CreditAttribution: carlos.macao commented

Well, for the node I was talking (Content Translation), now, don't see any hreflang metatag, except x-default. But on both nodes (translated and original) x-default metatag references himself instead of the original node (pt-pt). The tests were done with Content Translation active and Entity Translation disabled.

In both nodes:

Default locale (x-default) -> [node:source:url]
hreflang value for Português, Portugal (Português) -> [node:url-pt-pt]
hreflang value for Inglês (English) ->[node:url-en]