Skip Navigation

Home › Support › English Support › [Escalated to WPML Developers team] Conflicting hreflang with canonical for duplicated page

[Escalated to WPML Developers team] Conflicting hreflang with canonical for duplicated page

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 13:00 8:00 – 13:00 8:00 – 13:00 8:00 – 13:00 8:00 – 13:00 -
- 14:00 – 17:00 14:00 – 17:00 14:00 – 17:00 14:00 – 17:00 14:00 – 17:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 5 replies, has 2 voices.

Last updated by haydenN 4 years, 2 months ago.

Assisted by: Raja Mohammed.

Author Posts
March 9, 2021 at 6:00 am

haydenN

My semrush is showing errors of conflicting hreflang and canonical, but I checked the backend of the pages and no canonical i set for those
March 9, 2021 at 7:37 am
March 10, 2021 at 2:27 am #8268689

haydenN

Hi, may I know what's the follow up on this?
March 10, 2021 at 4:48 am #8269425

Raja Mohammed
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

The issue is still discussed with our developers, What you are experiencing is an intended behaviour with WPML and YOAST. However there are some SEO audit issue our developers will make a decision on this after detailed investigation and checking with SEO best practices.

As of now the stand is that with duplicate option the canonical should always point to the default langauge url to prevent SEO penalities.

March 10, 2021 at 1:39 pm #8275033

haydenN

Okay. I will wait for your next reply when you have the answer to the problem,

Thanks!
March 11, 2021 at 6:14 am #8280761

Raja Mohammed
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Since there is difference of opinion in handling duplicate contents and we are trying to get this working with more reliable resources from google. Also just in case if we could not arrive at any solution we will try to add some filters the code to make it work for differnt clinet.

As of now the status of the ticket is still being discussed by developers, I could not say how long this would take as it involves adding a new feature to the plugin which never exisited before.

I mark the ticket as escalated to developers and update once I have more news to share.

Regards
Raja
March 18, 2021 at 3:39 am #8338213

haydenN

Alright. Looking forward for your reply. Thanks