In this blog, I will try my best explain the anatomy of a Google (web) search result page from a programmer’s perspective (not from a user’s perspective). Why is this even necessary for programmers? For one thing, it is educational to study the seemingly simple, yet highly successful (Sullivan 2006), search page layout. For another thing, you may want to parse the search result page for your own ad-hoc uses. On this point, you may be wondering, but what about the Google SOAP Search API (no longer available) or Google AJAX Search API? If you are happy with those APIs, please, by all means, keep using them. But my concern is with anonymity (how anonymous are you with an API key required?). Following, I will illustrate the anatomy of a Google search result page with a simple example.