Proper HTTPS Migration: Preserving Traffic and Rankings

Even with the apparent simplicity of switching protocols — issuing a certificate and setting up a redirect — many projects see a drop in traffic after migration due to mixed content, redirect chains, and duplicate pages. We have performed over 200 migrations and know every pitfall. For example, on one project with 50,000 pages, the client lost 20% of traffic because the database still contained links to HTTP resources. Fixing the mixed content took only 4 hours — and traffic returned.

Why HTTPS Migration Is Critical for SEO

Search engines prioritize HTTPS sites. Browsers mark HTTP as insecure, reducing trust and increasing bounce rate. After migration, it is important to update data in Google Search Console and Yandex Webmaster immediately; otherwise, indexing may temporarily drop. Based on our experience, 90% of sites after proper migration achieve an A+ rating on SSL Labs, which positively impacts Core Web Vitals and rankings.

SSL Certificate: Free or Paid?

Let's Encrypt — free, automatically renewed, sufficient for most sites. The savings from using Let's Encrypt compared to paid certificates can amount to about $9–13 in savings per year. However, for e-commerce stores and corporate portals, an OV certificate from Sectigo or DigiCert is recommended.

# Certbot on Ubuntu sudo apt install certbot python3-certbot-nginx sudo certbot --nginx -d mysite.com -d www.mysite.com # Auto-renewal (already set up by Certbot) sudo systemctl enable certbot.timer 

Paid certificates (Sectigo, DigiCert) are needed for EV validation and wildcard for multiple levels.

Let's Encrypt is 10 times cheaper than paid certificates with comparable security, but requires automatic renewal every 90 days.

Nginx: HTTPS + HTTP→HTTPS Redirect

# HTTP → HTTPS redirect server { listen 80; server_name mysite.com www.mysite.com; return 301 https://mysite.com$request_uri; # without www } # HTTPS server { listen 443 ssl http2; server_name mysite.com; ssl_certificate /etc/letsencrypt/live/mysite.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mysite.com/privkey.pem; # Modern TLS configuration (Mozilla SSL Config Generator) ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384; ssl_prefer_server_ciphers off; # HSTS (only add after verifying HTTPS works!) add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; # ...rest of configuration... } 

What Is HSTS and Why Do You Need It?

HSTS (HTTP Strict Transport Security) is a header that forces the browser to always use HTTPS when visiting the site, even if the user enters http://. It prevents Man-in-the-Middle attacks and reduces the risk of mixed content. Configuring HSTS is one of the last steps after fully verifying HTTPS, because if an error remains, the browser will not allow HTTP access. Ensure all resources load over HTTPS, and only then add the header.

How to Fix Mixed Content After Migration

After migration, the browser blocks HTTP resources on an HTTPS page. Search for:

# Scan for mixed content npx mixed-content-scanner https://mysite.com # Or in Chrome DevTools: Console → filter "Mixed Content" 

For WordPress, use the Better Search Replace plugin to replace http:// with https:// in the database.

For other CMS:

-- PostgreSQL UPDATE posts SET content = replace(content, 'http://mysite.com', 'https://mysite.com'); UPDATE posts SET content = replace(content, 'http://old-cdn.com', 'https://new-cdn.com'); 

Typical Problems and Their Solutions

Migration Process: Step by Step

1. Audit current server and CMS configuration — check existing redirects, mixed content, duplicates.
2. Issue and install SSL certificate (free or paid) — with automatic renewal setup.
3. Configure 301 redirects from HTTP to HTTPS and from www to non-www (or vice versa).
4. Fix mixed content in the database and templates — using SQL queries or plugins.
5. Update sitemap and submit to search engines via Google Search Console and Yandex Webmaster.
6. Test on SSL Labs — rating A or A+ — and check for errors in Chrome DevTools.
7. Enable HSTS after verifying all pages.

Post-Migration Checklist

• [ ] All pages open over HTTPS
• [ ] HTTP redirects to HTTPS (301)
• [ ] www redirects to non-www (or vice versa)
• [ ] Canonical tags point to HTTPS
• [ ] Sitemap contains HTTPS URLs
• [ ] No mixed content warnings
• [ ] HSTS header is present
• [ ] SSL Labs rating A or A+

What's Included in the Work

• Audit of current server and CMS configuration
• SSL certificate issuance and installation
• 301 redirect setup
• Mixed content removal
• Sitemap update and submission to search engines
• Testing on SSL Labs and error checking
• Certificate maintenance instructions

Timeline and Pricing

HTTPS migration for a standard site takes 4–8 hours. Complex projects with custom CMS may require up to 2 days. Pricing is calculated individually based on the scope of work and certificates used. Contact us for a precise estimate. Our engineers are certified and work with Nginx, Apache, IIS, and all popular CMS. Get a consultation right now — we will suggest the optimal migration plan.