top of page

[FIX] No Redirect or Canonical to HTTPS Homepage From HTTP

How to Fix No Redirect or Canonical to HTTPS Homepage From HTTP

How to Fix No Redirect or Canonical to HTTPS Homepage From HTTP When you’re switching to HTTPS, one common issue is the lack of redirection from HTTP pages for your website. Learn how to fix that here!

If you are running a website and want to ensure your visitors get the best experience when browsing your site, then you need to make sure that it is secure.

HTTPS encrypts communication between the browser and server, which helps protect against data theft or eavesdropping. Without this protection, any information transmitted over HTTP can be viewed by third parties.

Google has also announced that they give preference to pages that use this type of encryption so having HTTPS will be helpful for your SEO.

If your website doesn’t have this encryption, your rankings are going to be automatically demoted.

Here are some of the most common HTTPS errors that you might find when you run an audit of your website on SEMrush:

  1. Homepage does not use HTTPS encryption.

  2. Non-secure pages,

  3. No redirect or canonical to HTTPS homepage.

  4. HTTP URLs, insight map,

  5. Issues with Mixed Content.

  6. Links on HTTPS pages lead to HTTP pages.

Switching from HTTP to HTTPS requires some changes such as updating links in WordPress; creating redirects from old pages that point to new destinations so they don’t show up as 404 errors; or adding a “canonical” tag pointing all URLs back at the website’s homepage under SSL encryption.

If you see any of the items listed above during your website audit, we suggest you go through the checklist from SEMrush and try to fix those issues and make sure all of the pieces are in place.

Sample issues in HTTPS Implementation when you run a Site Audit via SEMRush:

Some of them you may already have in place, but you just want to go through that checklist to make sure everything is implemented in the correct order.

And if you’re unsure about doing technical stuff like this yourself, you can always submit a ticket to us so we can help you out with it.

Related Posts

See All


bottom of page