google-chrome-logo

Did Google Develop a Native Browser Spider?

Search drives Google’s success Why would Google even bother to get involved in the browser wars? The browser market is fiercely competitive, and not particularly lucrative. Building a browser also comes with the burden of supporting users, maintaining standards compliance, and mitigating privacy or regulatory concerns. Feasibility of a Native Browser Spider The first question […]

Search drives Google’s success

Why would Google even bother to get involved in the browser wars? The browser market is fiercely competitive, and not particularly lucrative. Building a browser also comes with the burden of supporting users, maintaining standards compliance, and mitigating privacy or regulatory concerns.

Feasibility of a Native Browser Spider

The first question we should probably ask ourselves, is “Can a browser even be used as a Spider?” Fundamentally, a browser is just software that provides an implementation of the W3C DOM Specification via a Rendering Engine, and a scripting engine to enable any additional scripting resources.

If the source code is available, it’s absolutely possible to edit the Rendering Engine to perform feature extraction tasks such as returning the Page TITLE element, or returning all ANCHOR elements on the page.

[Source: iPullRank]