Crawl Rate

How fast search engines fetch your pages — what crawl rate is, why Google retired the Search Console rate slider, how to safely slow Googlebot down today, why you can't force an increase, and how Bing's manual Crawl Control differs.

First published: Jun 22, 2026 · Last updated: Jul 13, 2026 · Advanced
demand #11 in Crawling#25 in How Search Works#142 in Technical SEO#194 on the site

Crawl rate is how fast a crawler fetches pages from your server — the supply side of crawl budget (the demand side is how much the engine wants to crawl). Google now sets it automatically from your server's health: the manual Search Console rate slider was removed on January 8, 2024. To slow Googlebot today you signal through HTTP status codes — return 500/503/429 for a day or two, never 403/404, and crawl-delay is ignored by Google. You can't request a permanent increase; you improve it indirectly with a faster server, clean sitemaps, and fewer wasted URLs. Bing still gives you a manual Crawl Control grid. Crawl rate is not a ranking factor, and most sites never need to manage it.

TL;DR — Crawl rateCrawl rate is how fast a search engine crawler fetches pages from your site — the number of simultaneous requests it makes and the delay between them. Google sets it automatically based on your server's health; it's the supply side of crawl budget, not a ranking factor. is the supply side of crawl budgetThe number of URLs an engine will crawl in a timeframe. — how fast a crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. fetches, set by what Google calls the crawl capacity limit (parallel connections

  • delay between fetches). It’s automatic and reacts to server health; the manual GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. slider was removed Jan 8, 2024. To slow GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. now you signal via HTTP: 500/503/429 for 1–2 days max, never 401/403/404, and crawl-delay is ignored by Google (honored by Bing). You can’t request an increase — improve it indirectly. Bing still has a manual Crawl Control grid. Crawl rate is not a ranking factor, and most sites never need to touch it.

What crawl rate actually is

Crawl rate is how fast a crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. fetches pages from your server — the number of simultaneous requests it makes and the delay between them. Google’s name for it is the crawl capacity limit: “the maximum number of simultaneous parallel connections that Google can use to crawl a site, as well as the time delay between fetches.” Evidence for this claim Google defines crawl capacity using simultaneous connections and the delay between fetches, adjusted according to site responses. Scope: Google crawler capacity, not a ranking factor. Confidence: high · Verified: Google: Large site crawl budget guide

It’s one half of crawl budgetThe number of URLs an engine will crawl in a timeframe.. As I put it in my Ahrefs crawl-budget guide, crawl budget breaks into crawl demandCrawl demand is the 'want' side of crawl budget — how much a search engine wants to crawl a site or URL, driven by popularity, staleness, and perceived inventory (plus temporary spikes from site moves). It's distinct from crawl rate/capacity, the 'can' side. which is how many pages a search engine wants to crawl on your site and crawl rate which is how fast they can crawl.” Crawl rate is the supply side (how fast you’ll let them); crawl demand is the demand side (how much they want to). Crawl budget is where the two meet — and rankings sit outside that loop entirely.

In my How Search Works deck I frame the crawl rate limit as simply what your site can support — it’s driven by your server’s stability and crawl health, slow responses, 5xx (server) errors, and 429 (too many requests429 Too Many Requests is an HTTP client-error status code that means a client sent too many requests in a given time window — a mechanism called rate limiting. Unlike other 4xx codes, Google treats 429 as a server-overload signal and slows crawling instead of removing content.) responses. Google backs off when your server starts to struggle because it doesn’t want to crash your site. One detail people miss: all the GooglebotsGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. share a single crawl pool — the bots for search, images, ads, and so on all draw from the same rate. So a runaway crawl of one resource type eats into the crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. of everything else.

Crawl rate is the capacity gate. It can constrain demand, but increasing capacity does not manufacture demand or rankings. Source: Google Search Central

Crawl demand orders URLs using popularity, genuine change, and useful inventory. Crawl capacity is shaped by server response speed, stability, and errors. The capacity gate determines how far Googlebot proceeds through the ordered queue. A faster, healthier server can raise the ceiling, but it does not create crawl demand and is not a ranking signal.

© Patrick Stox LLC · CC BY 4.0 ·

What sets the crawl rate

The capacity limit is automatic and reacts to your server in real time. Google: “If the site responds quickly for a while, the limit goes up, meaning more connections can be used to crawl. If the site slows down or responds with server errors, the limit goes down and Google crawls less.”

There’s a second lever you don’t control: Google’s own resources. “Google has a lot of machines, but not infinite machines. We still need to make choices with the resources that we have.” So your server health sets the ceiling Google is willing to use, but Google’s own capacity and your site’s crawl demand decide how much of that ceiling actually gets used.

The myths doc confirms the server-health link works both ways: “A speedy site is a sign of healthy servers, so it can get more content over the same number of connections,” while “a significant number of 5xx HTTP response status codes (server errors) or connection timeouts signal the opposite, and crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. slows down.”

Does crawl rate affect rankings? No.

Bust this first, because it drives a lot of misguided effort. Crawling is required to appear in search, but it is not a ranking signal. Google is explicit: “Improving your crawl rate won’t necessarily lead to better positions in Google Search results.” Faster or more crawling buys you fresher discovery and indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., not higher positions. Crawl rate is an efficiency and server-health concern — full stop.

How to reduce Googlebot’s crawl rate

In order, from the real fix to the emergency lever:

1. Fix the server (the real fix). Speed it up or add resources. Because the capacity limit tracks response time and errors, a healthier server is the durable way to keep crawling in a comfortable range — and it’s the one that doesn’t risk your indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..

2. The emergency lever — 500/503/429. Google: “return 500, 503, or 429 HTTP response status code instead of 200 to the crawl requests.” Its crawlers “treat the 429 status code as a signal that the server is overloaded,” and 5xx and 429 server errors prompt Google’s crawlers to temporarily slow down with crawling.” Gary Illyes put the speed of this in concrete terms: “if the server persistently returns HTTP 500A 500 Internal Server Error is a generic HTTP status code — RFC 9110 defines it as an unexpected condition that stopped the server from fulfilling the request, and nothing more. The request may have been fine — something broke server-side while generating the response. For SEO, an isolated 500 is typically retried, but persistent, site-wide 500s get Google's documented response: slower crawling and, if the errors don't clear, eventual removal from the index. status codes for a range of URLs, Googlebot will automatically, and almost immediately slow down crawling.” Prefer 429 when you can — it explicitly means “too many requests” and can carry a Retry-After header.

The catch is that this is strictly temporary. Google: “We don’t recommend that you do this for a long period of time (meaning, longer than 1-2 days).” Leave it on and the cost is real — if those codes persist on the same URL for multiple days, “the URL may be dropped from Google’s index” and, for Google Ads, “your campaigns may be cancelled or paused, and your ads may not serve.”

3. What NOT to do. Don’t use 4xx to throttle. “The 4xx status codes, except 429, have no effect on crawl rate,” and Google says plainly “Don’t use 401 and 403 status codes for limiting the crawl rate.” In a dedicated 2023 post about people doing exactly this, Google wrote: “Over the last few months we noticed an uptick in website owners and some content delivery networks (CDNs) attempting to use 404 and other 4xx client errors (but not 429) to attempt to reduce Googlebot’s crawl rate. The short version of this blog post is: please don’t do that…” And don’t reach for robots.txt crawl-delay: “The non-standard ‘crawl-delay’ robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. rule is not processed by Google’s crawlers.”

4. The non-emergency request. For an ongoing problem that isn’t a fire, you can “file a special request to report a problem with unusually high crawl rate, mentioning the optimal rate for your site.” It’s slow, and it only goes one direction (see below).

Can you increase crawl rate? No — not directly.

There is no manual increase. Google: “You cannot request an increase in crawl rate, and it may take several days for the request to be evaluated and fulfilled.” What you can do is improve it indirectly. From my crawl-budget guide, the levers that actually move crawl efficiency: speed up your server / add resources; keep important pages in clean sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.; kill duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.; earn more links (external and internal); fix redirected links; use GET instead of POST where possible; and use the Indexing API where you’re eligible. Note that “a speedy site… can get more content over the same number of connections” — so server health is the lever that shows up on both the reduce and the increase side.

How to control Bingbot’s crawl rate

Here’s the sharp cross-engine contrast. Where Google retired manual control, Bing kept it. Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. has Crawl Control (under Configuration): an hour-by-hour grid where each hour shows bricks representing crawl speed — more bricks means faster crawling, fewer means slower. You can pick a preset built around your peak business hours, or choose “Custom” and draw your own pattern across the day. Bing also still honors crawl-delay in robots.txt — the exact directive Google ignores. So the two-engine rule of thumb: for Google you signal through server responses; for Bing you have an actual dial.

What happened to the Search Console crawl rate tool?

The timeline, because so much advice still references a tool that no longer exists:

  • Dec 2008 — Google introduces user crawl-rate control in Webmaster Tools.
  • Feb 2023 — Google publishes “don’t use 403s or 404s for rate limiting.”
  • Nov 24, 2023 — Google announces the deprecation of the Crawl Rate Limiter Tool. Illyes’ reasoning: “with the improvements we’ve made to our crawling logic and other tools available to publishers, its usefulness has dissipated.” The old tool was slow and barely used — it had “a much slower effect” and “would have taken over a day for the new limits to be applied on crawling,” and was used “rarely,” with those who did “in many cases set the crawling speed to the bare minimum.”
  • Jan 8, 2024 — the tool is removed. Evidence for this claim Google deprecated the Search Console crawl-rate limiter and removed it on January 8, 2024. Scope: Google Search Console's legacy crawl-rate limiter. Confidence: high · Verified: Google: Crawl rate limiter deprecation Google also lowered the floor: “With the deprecation of the crawl limiter tool, we’re also setting the minimum crawling speed to a lower rate, comparable to the old crawl rate limits.”

The practical upshot: the old manual slider had a >24-hour lag anyway; today’s server-signal approach (5xx/429) slows Googlebot almost immediately, which is strictly better for an actual emergency.

How to monitor crawl rate

The GSC Crawl Stats reportA Google Search Console report (under Settings) that shows how Google has crawled your site over the last 90 days — total requests, download size, and average response time, broken down by response code, file type, Googlebot type, and purpose. It's only available for root-level properties (a Domain property or a URL-prefix property verified at the site's root). is your window into what Google is actually doing: total crawl requests over time, total download size, average response time, and a host statusThe at-a-glance availability indicator at the top of Google Search Console's Crawl Stats report. It shows whether Googlebot hit significant problems reaching your site in the last 90 days across three checks — robots.txt fetching, DNS resolution, and server connectivity. view of your site’s availability to Google over the last ~90 days, plus a breakdown by response code, file type, crawl purpose, and Googlebot type. Watch average response time and the host-status signals — a climbing response time or a rash of 5xx is exactly what makes Googlebot throttle you, so this report is where you’ll see a self-inflicted slowdown before you go hunting for one. On Bing, Crawl Control and the crawl information in Bing Webmaster Tools are the equivalents.

Crawl rate vs crawl budget vs crawl frequency

Keep these straight:

  • Crawl rate = how fast (supply / capacity).
  • Crawl demand = how much they want to (popularity + staleness).
  • Crawl budget = the interaction of the two — “the amount of time and resources a search engine allows for crawling a website.”
  • Crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. = how often a given page gets re-crawled, which is mostly a crawl-demand question (popularity and how fresh/stale the page is).

And the reassuring part, which is my standing take: most sites don’t need to worry about any of this. “Most sites don’t need to worry about crawl budget, but there are few cases where you may want to take a look” — newer sites with a lot of pages, very large or rapidly changing sites, and sites with a pile of “Discovered – currently not indexed” URLs in GSC. If that’s not you, leave crawl rate alone and let Google’s automation do its job.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.