Anatomy of a Google Search Results Page
A Google search scraper has to read a page that Google assembles fresh for every query, country, language and device, so the same words can return a different page in the next city. Google's own documentation breaks the Google search results page into visual elements. The basic unit is the text result, which Google used to call a web result: a title link, a snippet, a byline date when Google estimates one, and an attribution line with favicon, site name and a visible URL made of domain and breadcrumb. Sitelinks and rich attributes such as review stars, price and availability can sit underneath.
Around those links Google stacks other blocks only when its systems expect them to help: sponsored results at the top and bottom, an AI Overview, a related questions group better known as People also ask, a featured snippet, a local pack with a map, product units, top stories, video results, discussions and forums, a knowledge panel for entities it recognizes, and related searches at the foot of the page. Their order changes from query to query, which is why a rank number means little without the layout above it.
Three platform changes decide how collection works today. Google answers traffic it does not recognize with a JavaScript challenge before it releases results. It no longer honors the parameter that once put 100 results on a single page. And its country domains now redirect to google.com, so the market a result belongs to is set by location and request parameters rather than by the address.
Get a Quote