: Will canonical tag referencing unsecure HTTP URLs on a HTTPS page cause the unsecure message? If a secure HTTPS page has a canonical tag referencing the HTTP version, will this cause the message
If a secure HTTPS page has a canonical tag referencing the HTTP version, will this cause the message in the browser that the page is using unsecure elements and prevent the green lock icon appearing?
e.g
wwww.example.com/
has the following canonical tag defined:
<link rel="canonical" href="http://wwww.example.com/" />
I know if that if other elements on a HTTPS page are called unsecured via HTTP you get the following warning in browsers:
As opposed to the lock icon:
Will this also happen if the canonical tag is using HTTP? I've read else where that it wont, but I'd like to see a live example.
More posts by @BetL925
2 Comments
Sorted by latest first Latest Oldest Best
It shouldn't. The unsecure warning comes about when a secured page incorporates non-secured elements. A canonical tag is a link, not an object to be incorporated into the page, so there's no reason why the padlock should care whether the URL it points to is http or https.
Web browsers do not care about canonical URLs. It is for search engine use only (specifically Google).
Additionally, canonical URLs do not affect the loading or rendering of a web page. So no assets will be loaded over HTTP which is what would cause an insecure error message.
So, no, they will not display any error message.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2025 All Rights reserved.