HTTP/2 and HTTP/3 for SEO: What Google Says
Hosting companies love to advertise HTTP/2 and HTTP/3 as SEO boosters. Google’s statements are more modest: it supports HTTP/1.1 and HTTP/2 for crawling, and says there is no ranking benefit from being crawled over HTTP/2. This guide explains what the protocols do, what Google says, and when upgrading is still worth it.
- What Google says
- What actually improves
- Check your protocol
- Opt-out facts
HTTP/1.1 supported by Googlebot HTTP/2 supported by Googlebot ranking benefit none stated benefit: server and visitor efficiency, not rankings
Google’s 2020 announcement says there is no ranking benefit for a site being crawled over HTTP/2, and that crawling over HTTP/1.1 stays the same in quality and quantity. A news report on Google’s updated crawler documentation says Google’s crawlers support HTTP/1.1 and HTTP/2, with possible resource savings but no Search benefit. HTTP/2 and HTTP/3 may still make pages load faster for visitors, which is a user benefit, not a documented ranking factor.
What HTTP/1.1, HTTP/2 and HTTP/3 are
They are versions of the protocol browsers and servers use to exchange pages. HTTP/2 allows many requests over one connection (multiplexing) and compresses headers. HTTP/3 runs over QUIC instead of TCP and handles lossy networks better. Most CDNs and many hosts support HTTP/2, and many support HTTP/3.
What Google says
Google’s Search Central post “Googlebot will soon speak HTTP/2” (September 2020) says Googlebot decides which sites to crawl over HTTP/2 based on whether the site supports it and whether the site and Googlebot would benefit. It says there is no explicit drawback for a server that only talks HTTP/1.1, and that crawling remains the same in quality and quantity. It also says there is no ranking benefit for a site in being crawled over HTTP/2. To opt out, a server can respond with a 421 status when Googlebot tries HTTP/2.
A later news report on Google’s crawler documentation update (November 2025) says Google’s crawlers support HTTP/1.1 and HTTP/2, that HTTP/2 crawling may save computing resources, and that there is no Google-specific product benefit such as a ranking improvement. Google’s Googlebot page itself, as I read it, does not discuss protocol versions, so check the current crawler documentation before relying on the detail.
What can genuinely improve
| Area | Possible effect (my own explanation) |
|---|---|
| Visitor load time | Multiplexing helps pages with many small files |
| Server resources | Fewer connections to handle |
| Mobile on poor networks | HTTP/3 may help with packet loss |
| Core Web Vitals | Indirect, through faster delivery |
| Rankings | No direct benefit stated by Google |
Page experience and speed matter for users. See Core Web Vitals on WordPress and TTFB for the metrics that matter more than protocol version.
Protocol comparison
| Feature | HTTP/1.1 | HTTP/2 | HTTP/3 |
|---|---|---|---|
| Googlebot support | Yes | Yes | Not stated in sources I read |
| Multiplexing | No | Yes | Yes |
| Transport | TCP | TCP | QUIC (UDP) |
| Ranking benefit | None | None stated | None stated |
Opting out of HTTP/2 crawling
Google says you can opt out by having your server respond with a 421 status when Googlebot attempts to crawl over HTTP/2. You cannot force Google to use HTTP/2. Most small sites have no reason to opt out. Only discuss this with your host if you have specific server problems.
Step by step: check and decide
Check your protocol
Open DevTools → Network, add the Protocol column, reload. Values like h2 or h3 show the version used.
Ask your host or CDN
Find out whether HTTP/2 and HTTP/3 are available and how to enable them.
Enable at the CDN or server
On Cloudflare the options are in the network settings. On servers, follow your host’s guide.
Measure before and after
Run speed tests on the same pages and compare load times.
Prioritise bigger wins
Fix images, caching and plugins before chasing protocol versions.
Examples (illustrative)
| Situation | Verdict |
|---|---|
| Host offers HTTP/2 by default | Fine; nothing to do |
| Site still on HTTP/1.1 only | No SEO penalty; consider upgrading for speed |
| Host claims “HTTP/3 boosts rankings” | Not supported by Google’s statements |
| Server errors after enabling | Revert or fix; check logs |
Notes for WordPress sites
- Protocol support lives at the host, server or CDN, not in WordPress.
- HTTP/2 reduces the need to bundle every file; avoid over-optimising with aggressive concatenation.
- Test your site after enabling a CDN, since caching rules also change behaviour.
- Combine protocol upgrades with caching, image compression and fewer plugins.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Action |
|---|---|---|
| Network tab shows http/1.1 | Not enabled or old stack | Ask host or enable at CDN |
| Site slower after change | Misconfiguration or cache issue | Test and revert |
| Crawl errors rise | Server problem, not protocol | Check logs and hosting |
| No ranking change | Expected | Judge by speed metrics |
Checklist
Check
- Protocol column
- Host support
- CDN support
- Baseline speed
Enable
- HTTP/2 first
- HTTP/3 if available
- Test pages
- Keep a rollback
Measure
- Same pages
- Same tool
- Compare load time
- Check errors
Prioritise
- Images
- Caching
- Plugins
- Server response time
What is and is not established
Google’s 2020 post states there is no ranking benefit from HTTP/2 crawling and describes the opt-out. A later news report describes updated crawler documentation. Google’s pages I read do not say anything about HTTP/3 crawling or ranking. Treat claims about HTTP/3 helping SEO as unsupported. Examples, steps and WordPress notes are my own practice.
Key terms
- HTTP/2
- Protocol version with multiplexing.
- HTTP/3
- Protocol version over QUIC.
- Multiplexing
- Many requests over one connection.
- 421
- Status used to refuse HTTP/2 crawling.
Common mistakes
Believing HTTP/2 boosts rankings
Google says no.
Opting out without need
No benefit.
Ignoring bigger speed wins
Images matter more.
Not measuring
No proof of gain.
Changing hosts for it
Risk without return.
Trusting marketing claims
Unverified.
Related guides
HTTP/2 and HTTP/3 questions
Does HTTP/2 improve rankings?
Google says there is no ranking benefit from being crawled over HTTP/2.
Do I need HTTP/2 to be indexed?
No. Googlebot supports HTTP/1.1 and crawling stays the same in quality and quantity.
Can I force Googlebot to use HTTP/2?
No. Google decides.
How do I opt out?
Respond with a 421 status when Googlebot tries HTTP/2.
Is HTTP/3 an SEO factor?
Not according to the Google sources I read.
How do I see my protocol?
Add the Protocol column in DevTools Network and reload.
Will it make my site faster?
Sometimes, especially on pages with many files. Measure it.
Should I switch hosts for it?
Rarely. Check hosting quality and TTFB first.
- Google Search Central Blog: Googlebot will soon speak HTTP/2 (2020)
- PPC Land: Google updates crawling infrastructure documentation (Nov 2025)
- Google Search Central: Googlebot overview
The 2020 statements come from search results quoting Google’s post, since the page body did not load when I fetched it. The 2025 detail comes from a news report. The protocol explanations, steps and WordPress notes are my own.
