Google has recently announced that its Googlebot ‘spider’ (which indexes web pages) will start crawling some sites over the new HTTP/2 protocol from November 2020.
HTTP/2 (aka h2) is the next major version of HTTP, the protocol the internet primarily uses for transferring data. It’s much more robust, efficient, and faster than its predecessor, due to its architecture and the features it implements for clients (for example, your browser) and servers.
Efficient websites minimize the number of requests required to render an entire page by minifying (reducing the amount of code and packing smaller pieces of code into bundles, without reducing its ability to function) resources such as images and scripts. However, minification is not necessarily convenient nor efficient and may still require separate HTTP connections to get the page and the minified resources.
HTTP/2 allows the server to “push” content, that is, to respond with data for more queries than the client requested. This allows the server to supply data it knows a web browser will need to render a web page, without waiting for the browser to examine the first response, and without the overhead of an additional request cycle.(You can read more about HTTP/2 here.)
Googlebot will now decide which sites to crawl over h2, based on whether the site supports h2 and if the site and Googlebot would benefit from crawling over HTTP/2. If your server supports h2 and Googlebot already crawls a lot from your site, you may be already eligible for the connection upgrade, and you don’t have to do anything.
If your server still only talks HTTP/1.1, that’s also fine. There’s no explicit drawback for crawling over this protocol, so that crawling will remain the same, quality and quantity wise. Also there is no benefit or otherwise from an SEO perspective – it’s mostly about the efficiency of collecting data.
When a server is upgraded and becomes eligible for crawling over h2, the owners of that site registered in Search Console will get a message saying that some of the crawling traffic may be over h2 going forward. You can also check in the server logs (for example, in the access.log file if the site runs on Apache).
The primary benefit of h2 is resource savings, both on the server side, and on Googlebot side. Whether Google crawls using h1 or h2 does not affect how a site is indexed, and hence it does not affect how much, or how fast Google plans to crawl pages from your site.
If you want more information about how we can help the management of your website’s indexing with Google and its SEO, please get in touch.