Web pages are constantly crawled by bots, gathering data and adding that to their indexed. This is a little test to find out a bit more about how the bots make those requests.

The idea is simple. I gather all the data in the request and place pertinent information from it into the title tag, meta description and content of the page. This information will get indexed and used by each bot. Ince the information is shown by the bot owner, I can see that information. e.g. Google may use the information in their search result snippets or the cached version of the page.

Note that you will see the request header information below in relation to your browser making the request.

Request Headers

Url /Request-HTTP-Header-Info
Method GET
IsSecureConnection True
IsAuthenticated False
Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding x-gzip, gzip, deflate
User-Agent CCBot/2.0 (
X-Original-URL /Request-HTTP-Header-Info
Max-Forwards 10
X-ARR-SSL 2048|128|C=GB, S=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA|OU=Domain Control Validated, OU=PositiveSSL,
X-ARR-LOG-ID 6e6aad8e-3ce4-4952-804d-45c896d56b94

Googlebot HTTP Headers

I performed a Fetch As Google in the search console to test the idea. As expected, the UserAgent was
Mozilla/5.0 (compatible; Googlebot/2.1; +
Google also includes a header value for From set to googlebot(at) I wonder if the bot answers emails ;-)

Googlebots Request Headers

Google Mobile: Smartphone User-Agent:
Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +

Google Mobile: XHTML/WML User-Agent:
SAMSUNG-SGH-E250/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Browser/ (GUI) MMP/2.0 (compatible; Googlebot-Mobile/2.1; +

Google Mobile: cHTML User-Agent:
DoCoMo/2.0 N905i(c100;TB;W24H16) (compatible; Googlebot-Mobile/2.1; +