Https pages Canonicalised to http vesrion is this bad?

"I have been assigned to resolve an error in the Google Search Console related to duplicate content, where Google has selected a different canonical URL than the user's preferred one. I am having difficulty grasping the issue, but I did observe that some HTTPS pages have a canonical tag pointing to the HTTP version, which seems unusual. Additionally, the website supports multiple languages, so I am considering if that could be contributing to the error."

It’s generally not recommended to use an HTTP canonical tag for an HTTPS page. This practice can lead to several issues:

  • Mixed Content: When a user accesses your HTTPS page, but the canonical tag points to an HTTP version, the browser might load mixed content (HTTP resources on an HTTPS page), which can raise security concerns and affect user experience.

  • SEO Implications: Search engines prioritize HTTPS pages, so having an HTTP canonical tag might confuse search engines and affect your website’s ranking.

  • User Experience: Users might be redirected to the less secure HTTP version, impacting their trust in your website and potentially causing confusion.

While the multiple languages supported by the website might contribute to the duplicate content issue, the HTTPS to HTTP canonical tag issue seems more concerning.

It’s advisable to review your website’s canonical tags and ensure they point to the correct and secure versions (HTTPS). Correcting this issue will likely help address the duplicate content error reported by Google Search Console.