EEAT Mechanics

Crawl-Budget: How Google Decides How Often to Visit Your Site

The officially documented system that determines crawl frequency — and why it matters for large sites with thousands of URLs

By Thomas Wawra· Published · Version 1.0· Systems referenced: Crawl-Budget

What is Crawl-Budget?

Crawl-Budget is how often and how regularly Google visits and updates a website's pages. It is one of the few systems that Google has officially documented — making it an [O] evidence code, stronger than systems known only from the leak.

The budget is determined by two factors: capacity (how fast and error-free does the server respond) and demand (how much users and Google want the content). A site that responds quickly and has high-demand content gets a larger crawl budget. A site that is slow, returns errors, or has low-demand content gets a smaller budget.

For large sites with thousands or millions of URLs, Crawl-Budget is a strategic concern. If Google can only crawl 10,000 of your 100,000 pages per day, which 10,000 does it choose? The answer: the pages that are most important, most frequently updated, and most likely to be relevant to users.

Claim-level evidence (3)
O
Crawl-Budget = capacity (server speed) x demand (user/Google interest).
Source: Google official documentation on Crawl-Budget · Crawl-Budget
O
Crawl-Budget is officially documented by Google — [O] evidence code.
Source: Google Search Central documentation · Crawl-Budget
O
For large sites: Google chooses which pages to crawl based on importance and freshness.
Source: Google official documentation — crawl prioritization · Crawl-Budget

How Crawl-Budget works

Crawl-Budget has two components: crawl rate limit (how many connections Google will make simultaneously) and crawl demand (how much Google wants to crawl). The rate limit is determined by server health: if the server responds slowly or returns errors, Google reduces the rate. If the server is fast and healthy, Google increases it.

Crawl demand is determined by popularity and staleness. Popular pages (high search volume, many incoming links) are crawled more frequently. Stale pages (not updated recently, low search volume) are crawled less frequently. A page that was updated yesterday and gets 1000 visits/day will be crawled much more often than a page that was last updated a year ago and gets 10 visits/day.

The Google API leak confirmed a Crawl-Budget field. The connection to the leak architecture is important: Crawl-Budget determines which pages Google can evaluate. If a page is not crawled, it cannot be evaluated by chard, NavBoost, or any other system. Crawl-Budget is the gatekeeper — everything else depends on it.

Claim-level evidence (3)
O
Crawl-Budget = crawl rate limit (server health) x crawl demand (popularity + staleness).
Source: Google official documentation · Crawl-Budget
O
Server errors and slow responses reduce crawl rate.
Source: Google official documentation — server health factors · Crawl-Budget
C
If a page is not crawled, no other system can evaluate it — Crawl-Budget is the gatekeeper.
Source: Architectural inference from crawl dependency · Crawl-Budget

Implications for SEO practitioners

For large publishers, Crawl-Budget optimization means removing low-value URLs from the crawl path. If Google spends its daily budget crawling 50,000 thin tag pages, it has less budget for your 500 high-quality articles. Robots.txt, noindex directives, and URL parameter handling all help direct Google's crawler to the pages that matter.

Server health directly affects Crawl-Budget. A server that responds in 50ms gets a higher crawl rate than one that responds in 2000ms. This means performance optimization (CDN, caching, server upgrades) has a direct SEO benefit: faster responses → more crawling → more indexing → more ranking.

The demand component means that pages with no search demand and no incoming links will be crawled infrequently. This is not a penalty — it is a resource allocation decision. Google has limited resources and allocates them to where they create the most value. A page with no demand is low-value for crawling.

Claim-level evidence (3)
O
Remove low-value URLs from crawl path — robots.txt, noindex, parameter handling.
Source: Google official documentation — crawl budget optimization · Crawl-Budget
O
Server health affects crawl rate — 50ms response gets more crawling than 2000ms.
Source: Google official documentation — server response time · Crawl-Budget
O
No-demand pages are crawled infrequently — resource allocation, not penalty.
Source: Google official documentation — crawl demand · Crawl-Budget

This Deep Dive is Schicht 2 content — interpreted and referenced, but always pointing back to Schicht 1 (the reference layer). Every claim is mapped to a source with an evidence code: [A] DOJ/sworn material, [B] leak field, [P] patent, [O] official Google communication, [C] interpretation.

© Thomas Wawra · Senior SEO Manager · wetter.com — a Funke Digital company