usdigitalmarketingindex.com SEO
Which SEO checks matter when converting a website from HTTP to HTTPS?
Updated November 15, 2026
Four groups: that every HTTP URL redirects permanently, in one hop, to its HTTPS equivalent on a valid certificate; that pages load no resources over HTTP; that canonical tags, sitemaps, internal links, and other annotations all name the HTTPS URLs; and that the HTTPS site is verified and watched in Search Console during the transition. Google’s documentation classes a change from HTTP to HTTPS as a site move with URL changes, since every address on the site changes even though the domain does not (Google’s guidance on site moves with URL changes). It is a contained kind of move, because each URL maps to itself with a different scheme. The checks exist to confirm that the mapping is exact and that no signal still points at the old scheme.
Certificate and redirect correctness
Certificate:
| Check | Pass condition |
|---|---|
| Valid and trusted | Issued by a recognized authority; not expired |
| Covers every hostname | The bare domain, www, and each subdomain in use |
| Complete chain | Intermediate certificates served |
| Renewal | Automated, or scheduled with an owner |
| Protocol support | Current TLS versions enabled |
Redirects: every HTTP URL answers with a permanent redirect to the same path and query on HTTPS. The guidance recommends “HTTP permanent redirects if possible, such as 301 and 308”.
A site that answers on both the bare domain and www has four host and scheme variants, and three of them should redirect to the fourth in a single hop.
A protocol-transition test table, for a site whose preferred form is https with www:
| Request | Expected status | Expected location | Final status |
|---|---|---|---|
| http://example.com/page/ | 301 | https://www.example.com/page/ | 200 |
| http://www.example.com/page/ | 301 | https://www.example.com/page/ | 200 |
| https://example.com/page/ | 301 | https://www.example.com/page/ | 200 |
| https://www.example.com/page/ | 200 | None | 200 |
| http://example.com/page/?id=5 | 301 | https://www.example.com/page/?id=5 | 200 |
| http://example.com/missing/ | 301, then 404 | https://www.example.com/missing/ | 404 |
Faults this table catches:
- two hops, where HTTP goes to HTTPS on the bare domain and then to www;
- a temporary redirect, 302, in place of a permanent one;
- query strings dropped;
- every HTTP URL sent to the HTTPS home page;
- a missing page returning 200 after the redirect.
Test a sample of every page type, plus images, documents, and feeds. The guidance advises against chains and in favor of redirecting to the final destination directly.
HSTS, the header that tells browsers to use HTTPS only, is a security measure to add once the HTTPS site is confirmed stable, since it is hard to reverse.
Mixed resources
A page served over HTTPS that loads images, scripts, styles, fonts, or frames over HTTP has mixed content. Browsers block or warn about such resources, and blocked scripts and styles can break the page.
| Resource | Where references hide |
|---|---|
| Images | Content bodies, CSS backgrounds, old articles |
| Scripts and styles | Templates, plugins, hard-coded tags |
| Fonts | Stylesheets |
| Embedded media and frames | Old embeds |
| Third-party tags | Analytics, advertising, widgets |
| Form actions | Forms posting to HTTP |
Find them by crawling the HTTPS site with a tool that reports insecure resources, by checking the browser console on each template, and by searching the database and templates for the http scheme. Fix at the source: update stored URLs in content, and update templates. Third parties that offer no HTTPS version need replacing.
Canonical and sitemap changes
Every signal the site sends about its own URLs should name HTTPS.
| Signal | Change |
|---|---|
| Canonical tags | HTTPS URLs; the guidance says to ensure canonical annotations on the new site use the new URLs |
| Internal links | HTTPS, or relative; the guidance says to change internal links from the old URLs to the new |
| XML sitemaps | HTTPS URLs only; submit the new sitemap |
| hreflang annotations | HTTPS URLs |
| Structured data URLs | HTTPS |
| Open Graph and other social tags | HTTPS |
| Pagination and alternate links | HTTPS |
| robots.txt | Served on HTTPS; sitemap line points to HTTPS |
| Redirect targets elsewhere on the site | Updated so they do not pass through HTTP |
| Canonical HTTP headers, for PDFs and similar | HTTPS |
A page reached over HTTPS whose canonical tag still names HTTP is telling search engines that the old address is preferred. That conflict is the one to hunt for after launch.
Outside the site: update the URLs in advertising campaigns, email templates, social profiles, business listings, and partner links where they can be changed. The redirects cover the rest.
Search Console monitoring
Search Console treats the two schemes as separate URL-prefix properties. The guidance says to “Verify data for each property separately”. A Domain property covers both schemes together.
| Action | Note |
|---|---|
| Verify the HTTPS property, or use a Domain property | Before launch |
| Submit the HTTPS sitemap | At launch |
| Change of Address tool | Not used: the guidance says "You don't need it for HTTP to HTTPS moves" |
| Check settings | Recreate any property-level settings on the HTTPS property |
What to watch:
| Indicator | Where | Expectation |
|---|---|---|
| HTTPS pages indexed | Page indexing report | Rising |
| HTTP pages | Same report, HTTP property | Moving to redirected status |
| Crawl errors | Page indexing and crawl stats | No spike in server errors or not-found |
| Clicks and impressions | Performance report, both properties together | HTTP declines as HTTPS rises; compare the sum |
| Canonical chosen by Google | URL Inspection on samples | The HTTPS URL |
Set expectations with the guidance’s own words: “Expect temporary fluctuation in site ranking during the move”. It gives a general indication that for medium-sized sites it can take a few weeks or more for Google to show the new URLs in place of the old, and longer for larger sites.
A checklist in order:
- Install and test the certificate on all hostnames.
- Make the site work fully on HTTPS, with no mixed content.
- Update canonicals, internal links, sitemaps, and annotations.
- Verify the HTTPS property.
- Enable permanent redirects from every HTTP URL.
- Run the test table across page types.
- Submit the HTTPS sitemap.
- Monitor both properties.
- Update external references.
- Keep the redirects permanently.
A move to a different domain name involves all of this and more, including the Change of Address tool, and is covered in the guide to how a domain migration can preserve organic value from backlinks to the old domain.
The order of work: certificate, clean HTTPS pages, updated signals, then one-hop permanent redirects, verified by request and watched in Search Console.
Add your comment to this answer