New researchTechnical SEO & AI Search · 2027Explore the framework

HTTP to HTTPS migration SEO: redirect every URL and verify the move

A focused HTTP-to-HTTPS SEO migration plan: certificates, one-hop redirects, canonical and sitemap updates, mixed content and post-launch checks.

Part of the Site Migrations series. For the full picture, start with Site migration SEO checklist: crawl before, during and after launch.

Switching on a certificate is not the whole move. Search engines have to replace HTTP URLs with their HTTPS equivalents, while users, links and assets continue to work. A protocol migration is simpler than a domain move, but it still needs URL-level verification.

What is an HTTP to HTTPS migration for SEO?

It is a site move in which the protocol of each affected URL changes from http:// to https://. Google’s site-move guide explicitly includes this case. The general site migration checklist covers all move types; this guide focuses on protocol-only failures.

What should you prepare before launch?

Inventory the HTTP pages, sitemaps, canonical tags, internal links, image and script URLs. Test an HTTPS version of representative pages with a valid certificate and no blocked resources. Keep the page content, metadata and URL paths stable where possible so the protocol is the main variable.

Item Before launch test Common failure
Certificate Valid on every host and subdomain in scope Redirect target has a certificate warning
HTTPS page 200 and same useful content Staging noindex or blocked CSS
Canonical Points to the HTTPS URL Still names the HTTP page
Assets Load over HTTPS Mixed-content errors
Sitemap Lists HTTPS canonical URLs Old protocol persists in generated feeds

The HTTPS and mixed content guide covers resource-level debugging. Do not launch with broken forms, checkout scripts or media just because the main document returns 200.

How should HTTP URLs redirect?

Use server-side permanent redirects, normally 301 or 308, from each old URL to the corresponding HTTPS URL. Preserve the path and meaningful query parameters unless the URL map says otherwise. Avoid an HTTP-to-HTTPS hop followed by another www or path redirect when a direct final target is possible. Google’s guide recommends direct targets and keeping chains low.

Do not send every HTTP URL to the HTTPS homepage. Pages with genuine replacements need relevant destinations; pages removed without replacements should be handled according to the site’s retirement plan. The redirect mapping guide explains those cases.

What changes after the redirect is live?

Update internal links, canonical URLs, hreflang pairs, structured-data URLs and XML sitemaps to HTTPS. Submit the new sitemap and verify the correct properties or domain property in Search Console. Google says a Change of Address request is not required for an HTTP-to-HTTPS move on the same domain.

Crawl the old HTTP URL inventory to check every redirect, then crawl the HTTPS destination set to check 200 responses, indexability, internal links and resources. In Search Console, watch whether HTTPS pages replace HTTP pages over time. Rankings may fluctuate while Google recrawls; an error spike or a missing section needs investigation, not patience alone.

HTTP-to-HTTPS launch checklist

  • Certificate valid for every destination host
  • HTTPS pages return 200 with intended content and tags
  • Each HTTP URL redirects permanently to the matching final URL
  • No loops, unnecessary chains or homepage catch-all
  • Canonicals, internal links, hreflang and sitemaps use HTTPS
  • Images, scripts, fonts and forms have no mixed-content failures
  • Old and new URL inventories are checked after launch (monitoring redirects after a migration)

The success condition is not just a padlock in the browser. It is a clean, one-to-one URL move that both visitors and crawlers can follow.

Frequently asked questions

Do I need Change of Address for HTTP to HTTPS?

No. Google's site-move guidance says the Change of Address tool is not needed for an HTTP-to-HTTPS move on the same domain. Permanent redirects and updated URLs do the work.

Should all HTTP pages redirect to the HTTPS homepage?

No. Each old URL should redirect to its matching HTTPS page or a genuinely relevant replacement. Redirecting unrelated pages to one destination can look like a soft 404.

How long should HTTP redirects remain?

Google recommends keeping site-move redirects for as long as possible, generally at least one year. Keeping them longer also helps visitors who follow old links.

Why do I still see HTTP URLs after launch?

Google must recrawl the old and new URLs to process the move. Check redirects, internal links, canonicals and sitemaps first, then monitor indexing rather than assuming an immediate switch.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows