How to Fix URLs Where Canonical From HTTP to HTTPS

How to Fix URLs Where Canonical From HTTP to HTTPS

Free Complete Site Audit

Access a full website audit with over 300 technical insights.

Something went wrong. Please, try again later.
Trusted by
Sitechecker trusted company

Free Website SEO Checker & Audit Tool

  • Scan the site for 300+ technical issues
  • Monitor your site health 24/7
  • Track website rankings in any geo

After crawling your web resource with an audit tool, you may see a notice advising you to update your canonical links from HTTP to HTTPS. What does it mean when such a message appears and how to fix it? Let’s figure it out.

What Does “Canonical From HTTP to HTTPS” Mean?

In short, a canonical URL can be determined as the best and most trustworthy representative page among a group of similar or even duplicated pages. In other words, this is a preferred version of the page.

For example, if there are URLs like example.com?table=1234 and example.com/tables/1234, the browser will choose only one as canonical.

This HTML element is located in the document’s header and is represented by the rel=canonical identificator.

Canonical from HTTP to HTTPS notice means that a particular URL uses the Hypertext Transfer Protocol while the canonical URL uses HTTPS. The difference is that the latter one is secured.

Watch this video by John Mueller for more information:

What Triggers This Issue?

The program checks whether any internal Hypertext Transfer Protocol URLs contain a canonical link element that uses a Hypertext Transfer Protocol Secure URL as the canonical URL.

How to Check the Issue?

The first option is to check manually: right-click on the page’s blank space and choose “View page source”. Then find the link tag with the following rel=canonical attribute <link rel=”canonical” href=” https://site.com “>. Check what protocol is specified therein.

Or you can simply use a specialized tool like this one: https://codebeautify.org/source-code-viewer

The Sitechecker tool presents a focused approach to identifying and resolving issues related to the transition of URLs from HTTP to HTTPS.

Canonical From HTTP to HTTPS Issue

By selecting the “View issue” option next to the relevant category, users can obtain a detailed list of pages that are improperly directing from HTTP to HTTPS. In the Sitechecker tool, when you delve into the “Canonical from HTTP to HTTPS” issue, you’ll not only receive a list of URLs with this specific problem, but you’ll also gain access to key insights for each URL. For each page listed, you can see the page’s weight, which gives you an idea of its significance and size, the HTTP status code indicating the server’s response to the request for that page, and the date the issue was identified. With the convenient “View issue in code” feature, users can directly examine the source code, making pinpointing and resolving the canonical issues straightforward and efficient.

Canonical From HTTP to HTTPS Pages

Secure Your SEO: Fix Your HTTPS Canonicals!

Discover and correct canonical links leading from HTTP to HTTPS effortlessly.

Something went wrong. Please, try again later.

Why is This Important?

  • Users’ impression. The browser, for example, Chrome (which is the most popular according to w3counter), sends a notification to users that the web resource is not secure. This can decrease the level of trust as well as conversion. This affects the overall performance of the site.
  • Security. HTTPS protocol encrypts the information shared between your browser and the web resource.
  • SEO performance. The protocol is a signal for the system. It prevents the indexing tools from redirecting to duplicate pages. In addition, it forwards a search engine to the homepage of the most relevant version. This fosters correct page indexing.

How to Fix the Issue?

If the site uses Hypertext Transfer Protocol Secure and you found that the version referred to next to the canonical is of the HTTP protocol, the website sends mixed messages to Google, stating that the HTTP version is the preferred one and should be in the index.

To change this, fix your canonical tags to point to the correct version of the webpage. You can either update your WordPress and manually fix every tag or request the assistance of the web specialists.

We strongly advise looking through a dedicated guide on how to migrate from HTTP to HTTPS: https://www.searchenginejournal.com/https-migration-guide/195103/

Fast Links

You may also like

View More Posts
Canonical URL and AMP Pages Issue
Site Audit Issues
Canonical URL and AMP Pages Issue
Iryna Krutko
Oct 28, 2022
How to fix the issue when URL receives both follow and nofollow internal links
Site Audit Issues
How to fix the issue when URL receives both follow and nofollow internal links
Ivan Palii
May 4, 2023
Internal redirects from trailing forward slash mismatch
Site Audit Issues
Internal redirects from trailing forward slash mismatch
Iryna Krutko
May 2, 2023
close