Short answer: HTTP/2 and HTTP/3 are newer versions of the protocol browsers use to load your pages. They load many files at once over one connection, so pages can arrive faster. Google says they give no ranking boost, but your visitors get the speed.
What changed from HTTP/1.1
| Version | Runs over | What it adds |
|---|---|---|
| HTTP/1.1 | TCP | The text protocol most of the web was built on |
| HTTP/2 | TCP | Binary format, many requests at once on one connection, compressed headers |
| HTTP/3 | QUIC over UDP | The same multiplexing, with a lost packet holding up only its own stream |
From MDN’s “Evolution of HTTP” and the abstracts of RFC 9113 and RFC 9114, read November 4, 2026.
HTTP/2 has been an official standard for more than ten years. MDN notes that it needed no changes to websites: an up to date server and a recent browser were enough.
HTTP/3 keeps the same semantics as earlier versions but uses QUIC instead of TCP. With HTTP/2 over TCP, a lost packet can block every stream on the connection; with QUIC, only the stream that lost data waits.
What HTTP/2 does for SEO
Google’s crawlers support HTTP/1.1 and HTTP/2, and HTTP/1.1 is their default. They use the version that gives the best crawling performance and may switch between crawling sessions.
Google says crawling over HTTP/2 may save computing resources for your site and for Googlebot, but brings no ranking boost in Google Search. A site that doesn’t want it can answer with a 421 status code.
The benefit is for people: faster loading. Our TTFB guide covers the first wait before a page starts to arrive.
How to check which HTTP version your site uses
- Open your site in Chrome, then open DevTools.
- Go to the Network tab and reload the page.
- Right-click the column headers and turn on Protocol.
- Read the row of the page itself: h2 is HTTP/2, h3 is HTTP/3.
- Reload once more: a browser often switches to HTTP/3 only after the server has announced it in an Alt-Svc header.
- If you only see http/1.1, ask your host whether HTTP/2 and HTTP/3 can be turned on.
- Then measure the page in PageSpeed Insights, before and after.
Our PageSpeed Insights guide explains how to read that test.
What our site and the crawlers use
On November 4, 2026, our site answered over HTTP/2 and announced HTTP/3 in its Alt-Svc header. In Chromium, the first visit used HTTP/2 and the next two used HTTP/3.
Our server logs from October 24 to November 4 show the crawlers differ. Googlebot fetched our pages mostly over HTTP/1.1, its default, while Bingbot, OAI-SearchBot and ClaudeBot used HTTP/2 almost every time.
That matches Google’s own description, and Google says the version brings no ranking boost.
Before you call your site up to date
- In the Network tab, the page itself shows h2 or h3.
- The server announces HTTP/3, and a second visit uses it.
- Your host keeps the server software current.
- You measured speed before and after any change.
- You don’t expect a ranking change from the version alone.
- Nothing blocks crawlers from reaching the site over HTTP/1.1.
RememberThe HTTP version is about speed for visitors, not about rankings. Turn it on, measure, and move on.
Server and crawl settings are part of our technical SEO service.
Quick answers about HTTP/2 and HTTP/3
What is HTTP/2?
The version of HTTP that sends many requests over one connection at the same time and compresses headers. It has been an official standard for more than ten years, and RFC 9113 defines it, replacing the earlier documents.
What is HTTP/3?
HTTP with the same semantics as before, but carried over QUIC instead of TCP. QUIC runs each stream separately, so a lost packet only holds up the stream it belongs to. It is defined in RFC 9114.
Does HTTP/2 help SEO?
Not directly. Google says crawling over HTTP/2 may save computing resources for your site and for Googlebot, but brings no ranking boost in Google Search. The speed it gives visitors is the real benefit.
Do I need to change my website to use HTTP/2?
Usually not. MDN notes that HTTP/2 didn’t require changes to websites and applications: an up to date server and a recent browser were enough. Ask your host whether it is on.
Why does Googlebot still use HTTP/1.1?
Because HTTP/1.1 is the default for Google’s crawlers. Google says they use the version that gives the best crawling performance and may switch between crawling sessions, based on previous crawling statistics.
Sources
Read on November 4, 2026. Google: Google Crawler (User Agent) Overview. MDN: Evolution of HTTP. IETF: RFC 9113: HTTP/2 and RFC 9114: HTTP/3. Our case: our own site in a browser and our server logs from October 24 to November 4, 2026.