Skip to content

Canonical Tag changes For HTTP to HTTPS Move?

DeeeeeeeeDeeeeeeee the Americas
edited December 2020 in Other / Off Topic
I went ahead and changed the canonicals on the site that (seems to be) negatively affected by the G update, from:
<link rel="canonical" href="http://example.com/page-b" />
to
<link rel="canonical" href="https://example.com/page-b" />
along with switching to HTTPS. Is this a bad idea, in  terms of SEO? I am thinking it may be an  issue.

I also changed the .htaccess so the non-HTTPS version of all  the pages now 301 redirect to their  HTTPS versions.

I also changed all internal links on the site to HTTPS from HTTP.

Reading around the web and seems no clearest answer.

Any sage counsel much appreciated!! I don't want to mess up!

Thanks.


Comments

  • SvenSven www.GSA-Online.de
    Using https is a good move. Though consider using href="//example.com.." as that will use the protocol it is linked from.
  • DeeeeeeeeDeeeeeeee the Americas
    Though consider using href="//example.com.."

    OK, many thanks, Sven. I've never seen this before.

    Tho I'm unsure: do you mean for internal linking or within the canonical tags, or both?

  • SvenSven www.GSA-Online.de

    So using a full URL with scheme/protocol is what they suggest there even using it without should be fine.
  • DeeeeeeeeDeeeeeeee the Americas
    edited December 2020
    OK, Sven, thank you. That doc suggests it's OK as relative without protocol, but seems to at the same time say it's best practice to include it.

    I'm confused. :(  I guess I'll leave it as https:// ??
  • SvenSven www.GSA-Online.de
    yes use https:// if you can make sure to always support that.
    Thanked by 1Deeeeeeee
Sign In or Register to comment.