Google’s web crawler for discovering and retrieving content for Google Search.
Googlebot is the name used for Google Search’s principal web crawlers. Google documents smartphone and desktop variants, which retrieve pages using different device profiles. A request from Googlebot is a step in discovering and processing information; it is not itself evidence that a page has been indexed or assigned a particular position.
When a page is missing or outdated in search, it helps to ask what the crawler could retrieve. A server error, an unintended crawl restriction or missing resources may need attention before changes to the page’s wording. Inspect the actual response and the relevant search reports rather than assuming a bot visit means the page was fully understood.
The name in a server log needs care too. Software can claim to be Googlebot by sending that text in its user-agent header. Google provides verification methods using its published IP ranges or DNS checks. A website should not grant privileged access merely because a request contains a familiar crawler name.
Takeaway: Knowing what Googlebot successfully retrieves helps separate access problems from content or ranking questions. Check important public pages, and verify crawler identity before changing security rules.
Example
After a website release, a service page still opens for staff but returns an error to some anonymous requests. The owner asks the developer to inspect the response and recent crawler evidence. The team fixes the access problem first rather than interpreting the old search result as proof that the new copy was rejected.
What to check
Keep the main information available in the mobile experience as well as on desktop. Neither a mobile crawler visit nor a mobile-friendly layout guarantees a ranking. Use the current Googlebot documentation instead of copying an old full user-agent string into permanent rules.
For more detail, see Googlebot.