Googlebot
Googlebot is the name of Google's web crawler — the automated program that continuously traverses the web, visits pages, fetches their content and hands it to the search index. It is thanks to Googlebot's visits that a website can appear in search results at all. It runs in two main variants — Googlebot Smartphone (the primary one, aligned with mobile-first indexing) and Googlebot Desktop — alongside specialized crawlers for images, video and news.
How Googlebot works
The crawler's work unfolds in three connected stages:
- Crawling — Googlebot downloads a page and extracts its links, which join a queue of URLs to visit. It starts from known URLs, sitemaps (XML sitemaps) and links found on other pages.
- Rendering — the fetched HTML, CSS and JavaScript are executed in a Chromium-based engine, so the bot sees a page close to what a real user would.
- Indexing — the processed content enters the index, from which Google's algorithms can surface it in response to queries.
Visit frequency and volume are capped by the so-called crawl budget — Google tunes crawl intensity to a site's size, server speed and how often content changes. A slow or overloaded server makes the bot back off, so fast hosting and a low time to first byte genuinely help indexing.
Googlebot in practice
Deliberately managing Googlebot's access is the foundation of technical SEO:
- Access control — the robots.txt file states which paths the bot may crawl, while meta noindex tags decide whether a page enters the index.
- Diagnostics — the URL Inspection tool in Google Search Console shows exactly how Googlebot sees a given address and whether it hit any errors.
- Performance — don't block CSS and JS, return correct status codes, and avoid redirect chains that waste crawl budget.
Verifying the bot's identity via reverse DNS also protects against scrapers that impersonate Googlebot to harvest content.
Powiązane pojęcia
Najczęstsze pytania
How can I verify that a visitor is really Googlebot?
Don't rely on the User-Agent string alone, since it can be spoofed. Run a reverse DNS lookup on the visitor's IP — it should resolve to a hostname on googlebot.com or google.com — then a forward lookup to confirm that hostname points back to the same IP address.
Does Googlebot render JavaScript?
Yes. Googlebot uses an engine based on an up-to-date version of Chromium, so it can execute JavaScript and see client-rendered content. However, rendering happens in a second wave and is more resource-intensive, so critical content is best delivered in the initial HTML.
