Does HTTP/2 help SEO? The short answer from Google’s own crawler documentation: no ranking boost, no extra crawling, and Googlebot’s default protocol is still HTTP/1.1 in 2026. That last part surprises almost everyone I say it to, because the advice floating around treats HTTP/2 as something Google rewards. It is not. It is a resource saving that Google decides to take or not take, per site, per session. Here is what is actually documented, and the one check most sites cannot currently run.
Does HTTP/2 improve your Google rankings?
No, and this is not an inference. The current crawler infrastructure doc says Google’s crawlers support HTTP/1.1 and HTTP/2, that crawling over HTTP/2 “may save computing resources (for example, CPU, RAM) for your site and Googlebot, but otherwise there’s no Google-product specific benefit to the site (for example, no ranking boost in Google Search)”. When Google announced HTTP/2 crawling in September 2020, Gary Illyes and Jin Liang were just as blunt about the other direction: not supporting it has “no explicit drawback”, and crawling “will remain the same, quality and quantity wise”.
What HTTP/2 changes is plumbing. Googlebot can open a single TCP connection and transfer multiple files over it in parallel, instead of one connection per fetch. Fewer connections means less CPU and RAM spent on both ends. That is the entire documented benefit.
Does Googlebot crawl over HTTP/2 or HTTP/1.1 by default?
HTTP/1.1. The same doc states “the default protocol version used by Google’s crawlers is HTTP/1.1”, and that crawlers “may switch protocols between crawling sessions depending on previous crawling statistics”. Googlebot started crawling over HTTP/2 in mid November 2020 for selected sites, and by May 2021 John Mueller said more than half of all URLs were being crawled over it. But it never became the default, and Google decides which sessions use it based on whether the saving is worth it. Your server supporting HTTP/2 is an invitation, not a switch.
This also explains a pattern that confuses people who do look at their logs: the protocol Googlebot uses can flip between months on the same site. Nothing broke. Google re-evaluates per session.
How do I check if Googlebot is crawling my site over HTTP/2?
Not in Search Console. The Crawl Stats report breaks requests down by response, file type, purpose and Googlebot type, and protocol is not a dimension in any of them, including the per-URL drawer. I keep seeing posts imply there is an HTTP version breakdown in there; there is not, and if Crawl Stats is already thin for you, missing Crawl Stats data covers why.
Server logs are the only place this question gets answered, and here is the catch I hit in audits: the default log formats on most hosts do not record the protocol at all. Apache’s common and combined formats include it inside the request line (“GET / HTTP/1.1”), so grep for Googlebot and look at the trailing token. On nginx, $request includes it too, but if the config logs a custom format without $server_protocol or the full request line, the information was never written. That is the real reason most people cannot say which protocol Googlebot uses on their site: the evidence was thrown away at logging time. Fix the log format first, then bucket Googlebot hits by protocol and by month, and expect it to wander.
Does HTTP/2 increase your crawl budget?
Google says no, in the 2020 announcement itself: whether crawling happens over h1 or h2 “does not affect how your site is indexed, and hence it does not affect how much we plan to crawl from your site”. The saving is per connection, not a bigger allowance. If your crawl request count in Crawl Stats jumps after enabling HTTP/2, something else changed. What actually moves crawl demand is covered in crawl budget in Search Console, and the levers are content and server health, not protocol.
The honest before and after test for an HTTP/2 rollout is flat requests with the same or better average response time. Also worth knowing: Googlebot’s fetch behavior has other hard edges that matter more than protocol, like the file size limits Googlebot applies.
Does Googlebot support HTTP/3 yet?
No. The 2026 crawler documentation lists HTTP/1.1 and HTTP/2 only, plus FTP and FTPS for rare fetches. Mueller confirmed back in December 2021 that Google was not crawling over HTTP/3, while pointing out that HTTP/3 still helps real users, and that is still where it stands. Serve HTTP/3 for visitors and Core Web Vitals, where LCP is usually the metric worth the work on WordPress; just do not expect Googlebot on it.
One last documented oddity: if you need Googlebot off HTTP/2 (usually a broken h2 termination proxy), respond with status 421 to its h2 requests and it falls back. In six years I have needed that exactly never, but it is the supported switch.
Sources
- Google Search Central, Googlebot will soon speak HTTP/2, September 2020, for the resource-saving rationale, the no-drawback and no-crawl-change statements and the 421 opt-out
- Google crawler documentation, overview of Google crawlers and fetchers, for the HTTP/1.1 default, the per-session protocol switching, the no-ranking-boost wording and the supported protocol list, checked 15 September 2026
- Search Console Help, Crawl Stats report, for the report’s actual breakdown dimensions
- Search Engine Roundtable, Google crawling half of URLs over HTTP/2 and Google not crawling on HTTP/3, for Mueller’s May 2021 and December 2021 statements
- My own audit practice for the log-format failure mode; the protocol check procedure is what I run on client servers