{"id":53731,"date":"2015-09-09T14:00:33","date_gmt":"2015-09-09T12:00:33","guid":{"rendered":"https:\/\/www.humanlevel.com\/diccionario-marketing-digital\/analisis-de-cabeceras-http-del-servidor"},"modified":"2020-11-03T12:34:00","modified_gmt":"2020-11-03T11:34:00","slug":"http-headers-analysis","status":"publish","type":"dicmarketing","link":"https:\/\/www.humanlevel.com\/en\/digital-marketing-dictionary\/http-headers-analysis","title":{"rendered":"HTTP headers analysis"},"content":{"rendered":"

The analysis of the server’s http\/https headers makes it possible to discover suspicious redirects<\/strong> likely to be identified as cloaking (showing the search engine an over-optimized content, different from the one shown to users) by the search engines. They also allow you to detect other problems such as cache checks, improper programming of error pages, etc.<\/p>\n\n

Tools for the analysis of server HTTP headers<\/h2>\n

If we have access to Google Search Console, we can analyze the http headers of any URL of our Web from the menu option Crawl>Explore like Google<\/strong><\/span>. <\/strong>We will get something like this:<\/p>\n

\"Header<\/p>\n

Where we can see the server response code (200 OK), as well as the rest of the server http headers.<\/p>\n

When we do not have access to Google Search Console or for more complex situations, the analysis of the server headers can be performed using the toolbar of the Web Developer extension for Firefox<\/a>. It is located in the menu Information>View Headers<\/strong><\/span>\u00a0of the tool. However, our recommendation is to use one of the online tools available for this purpose. The reason is that Web Developer parses the server headers on request of the resource defined in the URL, i.e. of the page currently displayed by the browser. But it is unable to detect a redirect if it occurs immediately before the page request, since these redirects occur at the server level, not at the browser level. If, for example, we analyze the http headers of http:\/\/humanlevel.com\/, we obtain this result:<\/p>\n

\"Analysis<\/p>\n

This result is not<\/strong> correct (or, at least, not complete), since in the analyzed URL there is a permanent 301 redirect to https:\/\/www.humanlevel.com\/, which is the URL we actually use. We can see that the Web Developer plug-in does not warn us of this situation, but simply shows us the result of the analysis of the redirection destination URL.<\/p>\n

Therefore, if we want to analyze everything that happens on a URL (including redirects), we recommend using tools such as Site Info from WMTips<\/a>. If we analyze the same URL with this tool, we obtain the following result:<\/p>\n

\"Header<\/p>\n

We see that this tool shows us the 301 redirection<\/a> that occurs at http:\/\/humanlevel.com\/, tells us where this redirect points to, and then shows us all the http headers of the second URL. Site info is able to identify and follow multiple chained redirects, so it is very useful to understand this kind of more complex situations.<\/p>\n\n

Another recommended tool for an even deeper level of analysis of server headers is Live HTTP Headers<\/a>with which we can analyze the http headers returned by the server not only at the page level, but also at the level of each http request (for each image, external CSS or JS files, etc.) Very interesting, although a bit more complex to use.<\/p>\n

Some more reference: Web Sniffer<\/a>.<\/p>\n

Relevant SEO aspects in the analysis of HTTP headers<\/h2>\n

The most relevant aspects from a search engine optimization point of view are:<\/p>\n