TL;DR
- Google described HTTPS as a very lightweight ranking signal when it announced it in August 2014, and has not published a current weight, so treat HTTPS as a baseline rather than a ranking lever.
- Chrome has labelled HTTP pages Not secure since version 68 in July 2018, so the visible cost of staying on HTTP is visitor trust, referrer data and browser features that need a secure context.
- Migrations lose traffic through execution errors: redirects sent to the homepage, canonicals still on HTTP, sitemaps listing old URLs, and mixed content on HTTPS pages.
- The Change of Address tool is for domain moves; a protocol change relies on one-hop 301 redirects, canonicals, sitemaps and a separate URL-prefix property if you use one.
HTTPS is HTTP sent through TLS encryption (the successor to SSL), so nobody between the browser and the server can read or change the traffic, and the visitor can confirm the site is who it claims to be. For SEO, Google has described HTTPS as a very lightweight ranking signal, so it is not a lever that lifts rankings. A badly handled move from HTTP can still cost traffic through missing redirects, canonicals that point back to HTTP, and mixed content. This guide stays on the SEO and migration side and does not cover installing a certificate on any particular host.
What is HTTPS and how does it differ from HTTP?
HTTP (Hypertext Transfer Protocol) is the language a browser uses to ask a server for a page. Plain HTTP travels as readable text. Anyone sitting on the path, such as a compromised public Wi-Fi network or an intermediary that injects ads, can read and alter it. HTTPS wraps the same conversation in TLS. The browser and server agree on encryption keys before any page data moves, so an observer sees only unreadable bytes.
The three things HTTPS provides
- Encryption: page content, form submissions and cookies are encrypted in transit.
- Integrity: if someone alters the data on the way, the receiving side detects it.
- Server authentication: a certificate issued by a Certificate Authority (CA) that browsers trust confirms that the domain in the address bar belongs to the server that answered.
It helps to know what HTTPS does not do. It does not say the site is trustworthy or accurate, since scam sites use HTTPS too. It does not protect against a hacked application or plugin. It protects only the path between the visitor and the server.
The visible differences
The URL starts with https:// instead of http://, the connection normally uses port 443 instead of port 80, and the server needs a certificate that matches the hostname the visitor opened. To a search engine, https://example.com/ and http://example.com/ are two different URLs even when the content is identical. That is why a migration needs redirects and canonical tags, covered below.
What are SSL and TLS certificates, and what types exist?
SSL (Secure Sockets Layer) is the older protocol. It was retired because of security flaws and replaced by TLS (Transport Layer Security). The versions in use today are TLS 1.2 and TLS 1.3. When hosting companies still say "SSL certificate", they mean a TLS certificate. In practice the two terms refer to the same file installed on the server.
By how much identity checking is done
- DV (Domain Validation): the CA checks only that the applicant controls the domain, for example by an email reply or a verification file. It is fast and automatable, and most free certificates are DV.
- OV (Organization Validation): the CA also checks that the organisation exists, and the organisation name appears in the certificate details.
- EV (Extended Validation): the strictest organisation checks. Modern browsers no longer show a green bar or a distinct company-name display for EV, so the visible benefit to visitors has shrunk a lot.
By how many hostnames are covered
- Single domain: one name, for example www.example.com.
- Wildcard: every subdomain at one level, for example *.example.com.
- Multi-domain (SAN): several listed names in one certificate, such as example.com, www.example.com and others you specify.
The most common failure is a certificate that covers example.com while visitors open www.example.com, or the reverse. Browsers then show a name mismatch warning. Before choosing a certificate, list every hostname that will really be used, including subdomains for a blog, a shop or landing pages.
Is a free SSL certificate different from a paid one?
The encryption in use does not depend on the price. What differs is the level of identity validation, certificate lifetime, any warranty the CA offers, support, and how easy renewal is. Let's Encrypt is a CA that issues free DV certificates with automated renewal, and many hosts let you switch it on with a click. For an ordinary business site a free DV certificate is technically sufficient. Reasons to pay are usually internal policy, a need for OV, or a warranty, rather than better security.
Check current rules on certificate lifetime before you plan renewals. The CA/Browser Forum, which sets the rules CAs and browsers follow, has been shortening the maximum lifetime in steps, so renewing by hand once a year is not a workable plan. Set up automatic renewal and an alert for approaching expiry.
Does HTTPS affect SEO and Google rankings?
Yes, but only slightly, and only partly through a direct signal. Google announced in August 2014 that it was using HTTPS as a ranking signal, and called it very lightweight, carrying less weight than high-quality content. Google has not published the current weight as a number, so nobody can honestly promise a ranking gain from switching.
The indirect effects that are real
- Visitor trust: Chrome has labelled HTTP pages "Not secure" since Chrome 68 in July 2018. The effect on conversion depends on the audience and the page type, and there is no reliable neutral figure to quote.
- Referrer data: when a visitor clicks from an HTTPS site to an HTTP site, browsers usually withhold the referrer, so the visit can show up as direct traffic in analytics. Moving to HTTPS removes that problem on your side.
- Browser features: several APIs, such as service workers and geolocation, work only in a secure context, meaning HTTPS or localhost.
- Third-party requirements: many payment providers and ad platforms expect checkout pages or landing pages to be HTTPS. Check each provider's current documentation.
The practical reading is that HTTPS is a floor, not an advantage. A site still on HTTP is behind the web's baseline. A site on HTTPS does not beat competitors for that reason alone, because rankings still depend mainly on content relevance, authority and page experience. Those are the areas a technical review such as an SEO audit examines.
How do you fix "Not secure" in Chrome?
There are only a handful of causes. Work through them in this order, from the most common and easiest to check.
- The page is still served over http://: the certificate may be installed but no redirect exists, so old links still open the HTTP version.
- The certificate has expired: browsers show a full-page warning. Renew it and confirm automatic renewal still works.
- The hostname does not match the certificate: for example, the certificate does not cover www or a subdomain in use.
- The certificate chain is incomplete: the server does not send the intermediate certificate. Some devices open the site and others warn, so it can look fine on your computer while some visitors cannot load it.
- Mixed content: the page is HTTPS but loads an image, script or stylesheet over HTTP. See the next section.
- The visitor's device clock is wrong: a wrong system date can make a valid certificate look expired or not yet valid. That is a visitor-side problem, not a site problem.
To see the exact reason, click the icon beside the URL in Chrome and open the connection details, or use the Security panel in DevTools. It says whether the problem is the certificate or a specific resource on the page.
What is mixed content?
Mixed content is an HTTPS page that requests some of its resources over HTTP, such as images, scripts, stylesheets, video or iframes. A resource fetched over HTTP can be altered in transit, which weakens the whole page. Browsers separate two kinds. Active mixed content, such as scripts, stylesheets and iframes, is blocked by default in modern browsers, so layouts break or features stop working. Passive mixed content, such as images, audio and video, may be upgraded to HTTPS automatically or flagged with a warning, depending on the browser and version. Because behaviour varies, check current browser documentation instead of guessing.
Where it usually hides
- Image links embedded in old content stored in the database, from the days when the site was HTTP.
- Themes or plugins with hard-coded http:// URLs in CSS or JavaScript.
- Background images in CSS, fonts, or third-party scripts that still point to HTTP.
- Videos or maps embedded with old iframe code.
- Canonical links, og:image and URLs inside structured data that are still HTTP.
To find it, open the Console in Chrome DevTools and look for mixed content warnings, or crawl the whole site and filter internal URLs that begin with http://. The fix belongs at the source: change the URL to HTTPS or to a relative path. Do not rely on the browser's automatic upgrade as the permanent solution.
What do you need to do to migrate from HTTP to HTTPS?
To Google, moving to HTTPS is a site move in which every URL changes protocol. The principle is that every old URL has a direct path to its equivalent new URL, and every signal points at the HTTPS version. The steps below are in the order to do them.
- Choose the preferred hostname first: decide between https://example.com and https://www.example.com and use it everywhere. Visitors can arrive in four ways (http or https, with or without www), and all four must end at the one preferred version.
- Install a certificate that covers every hostname, and test before switching: confirm the site opens over HTTPS without warnings on several real devices.
- Set page-to-page 301 redirects: http://example.com/page-name/ must go to https://example.com/page-name/ in a single hop. Do not send every URL to the homepage, and avoid redirect chains such as HTTP to HTTPS, then adding www, then adding a trailing slash. Combining the rules into one hop helps both speed and crawling.
- Update internal links to HTTPS directly: redirects are a safety net, not the main route. Menus, in-content links, images and CSS/JS files should be HTTPS at the source, and any mixed content you found should be fixed.
- Update canonical and hreflang: rel="canonical" must point to the HTTPS URL of the page itself. On a bilingual site, hreflang links must be HTTPS on both sides and reference each other.
- Update the XML sitemap and robots.txt: the sitemap should list only HTTPS URLs that return 200, the Sitemap: line in robots.txt must be HTTPS, and the HTTPS robots.txt must not block crawling by accident.
- Update structured data and meta tags that contain URLs: for example og:url, og:image and URLs inside JSON-LD.
- Add or check the Search Console property: a Domain property already covers both HTTP and HTTPS. A URL-prefix property needs a separate property for the HTTPS version. The Change of Address tool is for domain moves, not for protocol changes.
- Update every tool that stores URLs: the GA4 data stream, ad destination URLs, email template links, business profiles and social profiles. If you need the analytics side checked after the move, see the Google Analytics 4 migration service.
- Consider HSTS later: HTTP Strict Transport Security is a header telling browsers to use HTTPS for the domain, and browsers remember it for the period you set. If you set a long value on day one and then hit a certificate problem, visitors cannot reach the site at all, so start with a short value and extend it once you are confident.
Do not remove the redirects after a few weeks. Keep them permanently, because old URLs live on in external links, bookmarks and search engine indexes.
Post-migration check table
| Item | Correct state | How to check |
|---|---|---|
| Redirects | Every HTTP URL goes to its HTTPS equivalent with one 301 hop | Test sample URLs with curl -I or a crawler |
| Canonical | Points to the HTTPS URL of the same page | View page source or a crawl report |
| Sitemap | Only HTTPS URLs that return 200 | Resubmit in Search Console and read the status |
| Mixed content | No HTTP resources on HTTPS pages | DevTools Console and a crawl for internal http:// |
| Certificate | Covers every hostname, not expired, full chain | Chrome connection details and tests on several devices |
How do you read the HTTPS report in Search Console and check results?
Search Console has had an HTTPS report that shows how many URLs Google indexed as HTTPS and which are not, with reasons. Google reorganises its page experience reports from time to time, so open your own account to see where this report sits and whether it still exists. If you cannot find it, use these instead.
- URL Inspection: shows which URL Google chose as canonical and how a live test of the URL responds.
- Page indexing report: watch the categories related to redirects and canonicals. A rise after a migration is normal, but it should fall as Google updates its index.
- Crawl stats: shows whether Google is still requesting many HTTP URLs and which status codes your server returns.
- Your own crawl: crawl the whole site to find internal links still on HTTP, redirect chains and wrong canonicals.
Google needs weeks to months to process a protocol move depending on site size, and it does not publish a standard duration. Small fluctuations in the first period can happen. If organic traffic keeps falling, go back to redirects and canonicals first.
Mistakes that lose traffic
- Redirecting every page to the homepage, which strips relevance from pages that used to rank.
- Leaving canonicals on HTTP, so Google may pick the HTTP version as the main one.
- Keeping HTTP or redirecting URLs in the sitemap, which muddies reporting.
- A robots.txt on the HTTPS version that was set to block crawling during testing.
- A certificate that misses some subdomains or is not renewed, so visitors hit a full-page warning.
- Thai percent-encoded URLs that change shape during a redirect and land on pages that do not exist.
HTTPS in the Thai market: what needs extra care
Many Thai sites use Thai-language slugs, which are percent-encoded as %E0%B8... at protocol level. When you write redirect rules, make sure the rule matches both encoded and unencoded paths correctly and does not encode a path twice. The simplest test is to take ten to twenty real Thai URLs, run curl -I on each, confirm a 301 to the right page and a 200 at the destination, and only then call the migration finished.
Bilingual sites carry hreflang and canonical tags in several places, in the head and in the sitemap. If you fix one place and forget another, the signals conflict. Check both languages together instead of fixing English first and Thai later. For related Thai-market work, see SEO in Thailand.
On the legal side, Thailand's Personal Data Protection Act requires data controllers to maintain appropriate security measures. Encrypting data in transit is a basic measure that is commonly expected of sites that collect personal data through forms, but the Act does not name HTTPS as a requirement. Take legal advice if you have doubts. If you use a payment provider, check its current documentation for HTTPS requirements on the payment page.
Finally, sites spread across several hosts or developers often end up with nobody responsible for renewing the certificate. If it expires in the middle of an ad campaign, visitors see a full-page warning while ad spend continues. Assigning an owner and setting early alerts is not a step to skip. Ongoing upkeep like this is covered under website support and management.
Summary
HTTPS is the baseline standard for websites today, not a ranking accelerator. The SEO work is in a clean migration: page-to-page 301 redirects in one hop, canonicals and sitemaps that point at HTTPS, no mixed content, and a certificate that renews automatically. If you want a specialist to review redirects, canonicals, sitemaps and other technical issues across both language versions, the SEO audit from Relevant Audience is a place to start.
HTTPS FAQ: common questions
Are HTTPS and SSL the same thing?
Not exactly, but they are related. HTTPS is the protocol used to load the site, while SSL is the old name for the encryption layer that TLS has since replaced. People still say "SSL certificate" when the real thing is a TLS certificate, and "installing SSL" means installing a certificate so the site can load over HTTPS.
Will rankings rise after I switch to HTTPS?
You should not expect rankings to rise for this reason alone. Google calls HTTPS a very lightweight signal and has not published its current weight. The clearer benefits are no "Not secure" label, more complete referrer data, and access to browser features that need a secure context.
Is a traffic drop after moving to HTTPS normal?
Small swings in the first weeks can happen, but a sustained drop should not be left alone. Check page-to-page 301 redirects, canonicals pointing to HTTPS, a sitemap containing only the new URLs, and mixed content, in that order. Google does not publish a standard time for a move to finish, so compare against your own Search Console data rather than figures from elsewhere.
Do I need Change of Address in Search Console when moving to HTTPS?
No. The Change of Address tool is for moving to a new domain. A switch from HTTP to HTTPS relies mainly on 301 redirects, canonicals and sitemaps. The extra step is adding an HTTPS property if you use a URL-prefix property.
Is a free certificate enough for a business website?
Usually yes, on technical grounds, because the encryption is the same as in a paid certificate. Check automatic renewal, coverage of every hostname, and any requirement from your organisation or payment provider that might call for an OV certificate.







