What Google Says About HTTPS in 2026: Real SEO Impact

We analyzed 21 Google statements on 'HTTPS' (from 2016 to 2026), from spokespersons like Gary Illyes and John Mueller.

Is the HTTPS protocol really a major ranking criterion for Google?

Since Google's initial announcement in 2014, the HTTPS protocol has been the subject of much speculation in the SEO community. Many present it as an essential ranking factor, while others downplay its real impact on search result positions.

Official Google statements over the years reveal a more nuanced reality: HTTPS is indeed taken into account in the algorithm, but its weight remains modest. Spokespersons have evolved their messaging, particularly regarding the speed of HTTPS migrations and the technical best practices to adopt.

How has Google's position on HTTPS evolved since 2016?

In 2016, Google established the foundations of its HTTPS policy: the ranking signal exists but remains intentionally weak. Gary Illyes reveals that the 'boost' works even with a dubious quality certificate, as long as the URL starts with 'https'. A pragmatic approach that favors mass adoption over technical perfection.

Between 2017 and 2018, the messaging becomes more precise. Google representatives emphasize that HTTPS acts as a 'tie breaker', a criterion that separates pages with very similar relevance scores. They also stress the improvement of the migration process: whereas a transition previously took 3 to 4 weeks with traffic drops, it becomes virtually transparent in 2017.

What new technical problems emerge with HTTPS after 2020?

From 2020 onwards, statements focus on practical aspects: HTTP outbound links don't impact SEO, and HTTPS is not an absolute requirement for ranking well. The tone becomes more educational than prescriptive.

In 2026, an unexpected technical problem emerges: an old hidden HTTP page can cause malfunctions in site name display. Chrome now automatically hides these HTTP versions, but Googlebot continues to index them. John Mueller also reveals that HTTPS migrations cause temporary ranking losses, contrary to the transparency promises of 2017.

Has Google been consistent about HTTPS impact on ranking?

The central message remains stable over 10 years: HTTPS is a weak ranking signal, never presented as major. Gary Illyes states in 2017 that Google has 'no plans' to increase its weight, a position maintained until 2022 when John Mueller reiterates that HTTPS is not mandatory to rank well.

However, a nuance appears in 2019: Gary Illyes suddenly declares that this signal should 'not be ignored' because it 'affects enough queries'. This statement contrasts with the minimalist messaging of previous years, without formally contradicting the status of secondary criterion.

Have recommendations on HTTPS migrations changed?

Here, a major contradiction emerges. In 2017, Google promises nearly instantaneous migrations without traffic drops. Yet, in March 2026, John Mueller explains that an HTTPS migration equals a complete site migration, requiring each URL to be recognized, recrawled and reprocessed individually. He explicitly qualifies temporary ranking losses as 'normal'.

This evolution suggests either insufficient technical improvement or overly optimistic initial communication. Webmasters must now anticipate temporary fluctuations when moving to HTTPS, contrary to initial promises.

Should you really prioritize HTTPS to improve your SEO in 2026?

The answer is nuanced. HTTPS provides a real but modest SEO advantage, functioning primarily as an arbiter between pages of equivalent quality. Don't expect spectacular gains: a well-optimized HTTP site will always outperform a mediocre HTTPS site.

The main argument for migrating remains user trust and browser warnings, not pure ranking. Google clearly prioritizes overall user experience over the ranking signal.

What technical precautions should you take during an HTTPS migration?

Contrary to initial promises, plan for a transition period with fluctuations. Implement permanent 301 redirects, not temporary 302s. Absolutely avoid changing your URL structure simultaneously: modifying paths significantly slows down recognition.

Verify with curl or the Search Console inspection tool that Googlebot accesses your HTTPS pages, not potential default HTTP versions from the server. These ghost pages can corrupt your SERP display without you noticing it in your browser.

Do SSL certificates and HTTPS quality really matter?

Paradoxically, no for direct ranking. Google grants the same boost whether a certificate is valid or expired, as long as the URL starts with 'https'. This surprising technical approach aims to encourage mass adoption.

However, an invalid certificate can indirectly affect other factors (trust, bounce rate). Therefore prioritize quality, but don't panic if your certificate temporarily expires: your ranking won't immediately collapse.

What are the definitive best practices for HTTPS in 2026?

Consolidate these recommendations for a successful migration and optimal use of the secure protocol:

• Migrate to HTTPS for user experience above all, the SEO gain is a secondary bonus
• Only use permanent 301 redirects, never 302 or 303 during migration
• Anticipate temporary ranking losses while Google reprocesses your URLs one by one
• Don't modify your URL structure simultaneously, keep the same paths to accelerate the transition
• Verify that no default HTTP page is accessible by testing with curl or Search Console
• HTTP outbound links don't impact your SEO, you can freely link to non-HTTPS resources