Crawl-Budget
How often and how regularly Google visits and updates a website's pages (crawling — Google 'reading in' the content).
01What it measures
How often and how regularly Google visits and updates a website's pages (crawling — Google 'reading in' the content). The budget is determined by two factors: capacity (how fast and error-free does the server respond?) and demand (how important does Google find these URLs?). For a dynamic weather site this is highly relevant: if Google doesn't crawl a page in time, the weather data in search results is outdated.
02Derived from
Server response times and error rates (capacity side), plus popularity and freshness data (demand side).
03How it's measured
Not a leak field but an official concept: capacity (what the server can handle — response time, error rate) × demand (how much Google wants to fetch the URLs — popularity, change frequency). [O]
04Why it counts here
Authority is indirect — crawl budget is a demand correlate and the earliest gate in the entire chain: pages that aren't crawled aren't indexed and can't rank.
05What to do about it
For sites with many thousands of URLs, crawl budget is a real bottleneck. Technical measures like fast server response times, clean sitemap structures and removing unimportant or duplicate URLs free up budget — for pages that really need it: same-day reports, real-time data and frequently updated forecasts.