Crawl Stats in Search Console: The Complete 2026 Guide

Crawl Stats is a report inside Google Search Console showing how Googlebot interacts with your site over time. It displays total crawl requests, total download size, and average response time, grouped by day. Google's 2025 Search Console documentation describes it as the primary tool for monitoring bot activity.

The report covers the last 90 days by default, with daily refreshes. A 2025 Search Engine Land guide recommended checking Crawl Stats weekly for sites over 10,000 pages.

Total crawl requests counts HTTP requests Googlebot made to your site. A rising trend indicates increased crawl activity; a falling trend may signal server access problems.

Total download size is the sum of all bytes Googlebot downloaded. Optimize images, CSS, and JavaScript to reduce this metric. Average response time is the median wait time — above 500 ms correlates with reduced crawl frequency. Google's 2025 guidance sets 200 ms as the target for sustained high crawl rates.

Host Status shows historical site availability from Google's perspective, displayed as a percentage of successful requests. A rate below 99 percent requires investigation. Google's 2025 help documentation says any sustained drop below 95 percent triggers automatic crawl rate reduction.

The chart is a line graph over time. A flat line at 100 percent is ideal; a zigzag pattern suggests intermittent server problems. Use this to correlate crawl issues with deployments or configuration changes.

Google breaks down crawl requests by purpose: discovery crawls (new or updated URLs), refresh crawls (recheck indexed pages), sitemap fetches, and robots.txt checks. Google's 2025 crawl stats documentation introduced this breakdown for deeper diagnostic insight.

A high ratio of refresh to discovery crawls indicates Google is recrawling old content instead of finding new content. A 2025 Ahrefs analysis showed sites publishing daily had a 60:40 discovery-to-refresh ratio; weekly publishers had the inverse.

The crawl response breakdown groups URLs by HTTP status code: 2xx (success), 3xx (redirects), 4xx (client errors), and 5xx (server errors). A high number of 3xx responses means Googlebot follows too many redirects. A spike in 4xx responses indicates broken links or misconfigured redirects. A spike in 5xx responses indicates server load problems. Google's 2025 crawl budget documentation recommends keeping non-2xx responses below 5 percent of total crawl requests.

Crawl Stats breaks down requests by file type: HTML, CSS, JavaScript, images, and other resources. Googlebot must download CSS and JavaScript to render pages for indexing. Google's 2025 JavaScript SEO documentation says heavy JavaScript files increase crawl demand per page.

A site with 500 KB of JavaScript per page consumes more crawl budget than one with 50 KB. Reduce JavaScript file size through code splitting and deferring non-critical scripts. A 2026 Moz analysis found that sites reducing JavaScript payload by 40 percent saw a 25 percent increase in pages crawled per day.

You open Crawl Stats in Search Console and export the last 90 days of data. You check the total crawl requests trend for sharp drops or spikes. You review average response time against the 200 ms target. You note the discovery-to-refresh crawl ratio. You check host status for availability dips below 99 percent. You inspect the crawl-by-response breakdown for non-2xx percentages. You review crawl by file type to see how much budget goes to JavaScript and CSS. You compare stats before and after the most recent site deployment.

Note the gap. This post synthesizes 2025 and 2026 data from 5 sources: Google Search Central Crawl Stats documentation, Search Engine Land Search Console guide 2025, Ahrefs crawl ratio analysis 2025, Moz JavaScript payload study 2026, and Google crawl budget documentation 2025. 4 non-public Search Console audits from agency work informed the response time patterns. Replication required.

Audit monthly.