Is HTTPS Better for SEO?

Yes, HTTPS is better for SEO, although mostly not for the reason most articles give. Google did announce HTTPS as a “very lightweight” ranking signal in 2014, but its current documentation says page experience aspects other than Core Web Vitals don’t directly help a site rank higher, so switching protocols should not be expected to lift a page by itself. The real SEO case for HTTPS is that Google prefers to index the HTTPS version of a page, Chrome warns visitors away from HTTP pages, and an HTTP site loses referral data and puts its forms at risk. In 2026 an HTTP site has a problem to fix, and the fix is worth doing even though it is not a ranking shortcut.
What Google has said about HTTPS and rankings
The starting point is Google’s August 2014 announcement, HTTPS as a ranking signal. It described HTTPS as “a very lightweight signal”, affecting fewer than 1% of global queries and “carrying less weight than other signals such as high-quality content”, and it said Google might strengthen it over time to encourage the switch. Most of the pages that rank for this question still stop there, which is why the idea of HTTPS as a tiebreaker between two otherwise equal pages keeps circulating.
The more lasting change came in December 2015, when Google announced it would start indexing HTTPS pages by default. When the same content is available over both HTTP and HTTPS on one domain, Google typically chooses the HTTPS URL as long as the secure version meets a short list of conditions, which the checklist further down follows. Search Console’s HTTPS report still says the same thing today: if a page has both an HTTP and an HTTPS address, “Google prefers to index the HTTPS version.”

Google’s current page, Understanding page experience in Google Search results (last updated 22 September 2026), lists “Are your pages served in a secure fashion?” among its self-assessment questions. Its FAQ then says that Core Web Vitals are used by the ranking systems, and that “beyond Core Web Vitals, other page experience aspects don’t directly help your website rank higher in search results”, although they make a site more satisfying to use, which is what the ranking systems aim to reward. Read together, the documented position is that HTTPS is expected, that Google indexes the secure version when it can, and that you should not plan on a ranking jump from the switch alone. Anyone quoting a number of positions gained from HTTPS is guessing, because Google has never published one and most migrations happen alongside other technical fixes that muddy any before and after comparison.
HTTP vs HTTPS: what changes for your site
The difference between the two protocols is encryption and authentication. HTTP sends everything between the browser and the server as readable text, while HTTPS encrypts it using TLS (still widely called SSL) and lets the browser confirm that the certificate belongs to the domain it is visiting. For search, the practical effects look like this.
| What changes | On HTTP | On HTTPS |
|---|---|---|
| Direct ranking effect | Misses the 2014 “very lightweight” signal, whatever weight it still carries | Google’s current docs say page experience aspects beyond Core Web Vitals don’t directly lift rankings |
| Which URL Google indexes | The HTTP URL loses out wherever a valid HTTPS version exists | Google prefers this version when its conditions are met |
| What Chrome shows | “Not secure” in the address bar, and a warning before the first visit once Chrome’s HTTPS-first default reaches the user | No warning |
| Referral data from secure sites | By default the browser sends no referrer, so the visit loses its source | The referring site’s origin is passed by default |
| Forms and personal information | Sent as readable text | Encrypted in transit |
| Newer browser features | Many are restricted to secure connections | Available |

On the last row, Chrome’s own team wrote in 2018 that HTTPS opens the way to performance improvements and to powerful new features “that are too sensitive for HTTP”, so the old worry that encryption slows a site down no longer holds in the Chrome team’s view. The certificate itself is a separate decision, and the question of which certificate a small business actually needs has its own answer, since the type of certificate does not change how Google treats the page.
Why the browser matters more than the ranking signal
Since Chrome 68 in July 2018, Chrome has marked every HTTP page as “Not secure” in the address bar, as the Chromium team announced in A secure web is here to stay. That label sits next to the page before a visitor has read a word, which is a poor first impression on a page asking for a phone call or a quote. It does not change where the page ranks, but it does change what happens after the click, and a click that bounces is wasted whether it came from organic search or an ad.
The next step is bigger. In October 2025 Google’s security team announced that with the release of Chrome 154 in October 2026 it would turn on “Always Use Secure Connections” by default, meaning Chrome “will ask for the user’s permission before the first access to any public site without HTTPS” (HTTPS by default). The post explains that Chrome will not keep warning about a site a user visits regularly, but a new visitor arriving from a search result is exactly the person who sees that warning for the first time. For an HTTP site, that turns a label in the corner into a page that stands between the searcher and the content.

The same applies to paid traffic. If a business runs Google Ads to a landing page that is still on HTTP, it pays for the click and then the browser questions the page before it loads. As an illustrative example, picture a Calgary renovation company whose site moved to HTTPS years ago except for an old quote-request page on a subdomain that still loads over HTTP. Its ads and its organic listing both point visitors into that form, and every new visitor meets a warning at the exact moment they are asked for their name, phone number and address. Nothing about the company’s rankings would reveal the problem, which is why it is worth clicking through your own forms from a private browser window every so often.
Referral data and privacy
There is also an analytics cost. Modern browsers apply a default referrer policy, documented on MDN’s Referrer-Policy page as strict-origin-when-cross-origin, which sends no referrer at all when a visitor follows a link from an HTTPS page to an HTTP one. Sites can set their own policy, so not every source is lost, but on an HTTP site a share of the visitors who arrived from other secure sites shows up in analytics with no source, usually lumped into direct traffic. Over time that makes it harder to see which links and channels are worth the effort.
For Canadian businesses, the privacy side is worth a moment too. The Office of the Privacy Commissioner of Canada’s guidance on PIPEDA’s safeguards principle says personal information must be protected in a way that suits how sensitive it is, and it lists encryption among the example technological safeguards, while noting that PIPEDA does not prescribe specific measures. Alberta and British Columbia each have their own private-sector privacy law, so which one applies depends on the business, and a lawyer is the right person to ask. Whatever the law requires, a contact or booking form that sends names, phone numbers and addresses as readable text is hard to defend.
How to switch from HTTP to HTTPS without losing rankings
Google treats a move from HTTP to HTTPS as a site move with URL changes, and its site move guidance applies. The checklist below follows the conditions Google listed in 2015 for choosing the HTTPS URL, plus the points from that guide that cause the most trouble in practice.
- Install a valid TLS certificate for every hostname you use, including both the www and non-www versions. Many hosts include one with the plan.
- Send every HTTP URL to its HTTPS equivalent with 301 redirects, one hop each, with no chains through other HTTP pages. Google’s guide says to keep redirects for as long as possible, generally at least a year.
- Point every canonical tag at the HTTPS URL. A canonical that still names the HTTP page is one of the conditions that stops Google from choosing the secure version.
- Update internal links, menus and image URLs to HTTPS so the site has no on-host links to HTTP pages. On WordPress, old URLs stored in the database are the usual culprit, and a database search and replace fixes them.
- Remove mixed content, meaning scripts, stylesheets, images or embeds still loaded over HTTP. Google’s 2015 conditions exclude pages with insecure dependencies.
- List only HTTPS URLs in the XML sitemap and make sure robots.txt and any noindex tags were not left blocking the secure version.
- Once everything works, consider adding an HSTS header, which tells browsers to use HTTPS for the domain every time. Add it only after testing, because browsers remember it.
- Verify a Domain property (or an HTTPS URL-prefix property) in Search Console and watch the HTTPS report, which shows how many indexed URLs are HTTP vs HTTPS and why an HTTPS version could not be indexed.

Expect some movement while Google recrawls. Its site move page says a small to medium site can take a few weeks for most pages to move, larger sites take longer, and visibility may fluctuate during that time. A drop that lasts longer than that usually points to a broken redirect, a stray canonical or blocked HTTPS pages, all of which the HTTPS report and a crawl will show.
When HTTPS is not the problem
Most business sites switched years ago, so for many readers the real question is why an HTTPS site still is not ranking. HTTPS is a one-time requirement, and once it is done properly there is nothing more to gain from it in Google. The reasons a page sits on page two are almost always elsewhere: content that does not answer the search better than the pages above it, too few links from other sites, weak internal linking, or crawl and indexing issues that a technical SEO checklist will surface. SEO also takes months, so a page that went live recently may simply not have had time.

If you are not sure whether your site’s move to HTTPS was finished cleanly, a technical audit checks redirects, canonicals, mixed content and the HTTPS report before it moves on to the work that does change rankings. SEO Company To-The-TOP! is a solo practice in Calgary that has done White Hat SEO since 2007, and you can call (403) 308-5949 to talk through what your site needs.
Contact Calgary SEO Company To-The-TOP!
Questions about anything in this article, or about your own rankings? Talk to a Calgary SEO specialist directly.
Phone: (403) 308-5949
Address: 1509 14 Ave SW, Calgary, AB T3C 0W4
Hours:
Monday to Friday: 10:00 am – 7:00 pm
Saturday: 12:00 pm – 4:00 pm
Sunday: closed
