Crawl Delay

The crawl-delay robots.txt directive — what it does, why Google stopped honoring it in 2019 and Yandex dropped it in 2018, how Bing still interprets the value, which other crawlers respect it, and what to use instead.

First published: Jun 27, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #11 in Crawling#25 in How Search Works#142 in Technical SEO#194 on the site
1 evidence signal on this page

Crawl-delay is a non-standard robots.txt directive that asks bots to wait between fetches to ease server load. Google has ignored it since September 1, 2019; slow Googlebot with temporary 429/503 responses or by fixing server capacity. Bing's current Webmaster guidance documents values from 1–20 seconds. Yandex dropped support on February 22, 2018 and now uses a crawl-rate setting inside Yandex Webmaster. Check each crawler's own documentation before relying on this non-standard field.

TL;DR — Crawl-delay was an unofficial 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. directive for throttling botsA 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.; it was never in the formal standard (RFC 9309). Google retired it September 1, 2019 and explicitly doesn’t process it — 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. with 429/503 (1-2 days max) or by fixing the server, not crawl-delay. Bing’s current guidance documents values from 1–20 seconds. Yandex dropped support for it on February 22, 2018 — it’s not honored there either; Yandex now uses a crawl-rate setting inside Yandex WebmasterYandex Webmaster (webmaster.yandex.com) is Yandex's free search console — the Yandex equivalent of Google Search Console — for verifying a site, monitoring indexing and queries, requesting reindexing, running diagnostics, and setting a site region. It's essential for any site targeting Russia and the wider CIS, where Yandex, not Google, is the dominant search engine.. Many SEO crawlersA 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. (AhrefsBot, Semrush) and some AI botsAI crawlers are bots from AI companies that fetch web pages to train language models, build AI-search indexes, or answer live user questions. They come in three categories, each with its own user-agent tokens and its own robots.txt controls. (ClaudeBot) respect it too — which is the one real use case left: controlling non-Google, non-Bing, non-Yandex botsYandexBot is the main web crawler operated by Yandex, Russia's dominant search engine. It discovers and fetches pages for Yandex Search, is one of a family of Yandex robots, and supports a Yandex-only robots.txt directive (Clean-param) that Google and Bing don't have..

Why crawl-delay exists

Crawl-delay is a throttle. The idea is straightforward: an aggressive crawler fetching pages back-to-back can put real load on a server, especially a small or slow one. Crawl-delay was the courtesy lever — a way to ask a bot to pause a few seconds between requests so your server could keep up. It lives in robots.txt inside a User-agent group, the same place your disallow and allow lines go. (For the full file, see robots-txt.)

The catch is that it was never standardized. The Robots Exclusion Protocol was finally formalized as RFC 9309 in 2022, and crawl-delay isn’t in it. It was always an unofficial extension that different crawlers chose to implement — or not — and interpreted in their own way. That inconsistency is exactly why Google walked away from it.

Google retired it on September 1, 2019

On July 2, 2019, Gary Illyes published A note on unsupported rules in robots.txt on Google Search Central. Google was open-sourcing its 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. parser and, as part of that, retiring all code that handled rules that were never part of the internet draft — specifically noindex, nofollow, and crawl-delay. The retirement took effect September 1, 2019.

Google’s reasoning: these rules were undocumented, unofficial, and interpreted inconsistently across crawlers, which created ambiguity. The current robots.txt documentation is now explicit — Google supports four fields (user-agent, allow, disallow, and sitemap), and the docs say “other fields such as crawl-delay aren’t supported.” Google’s Myths and facts about crawling page repeats it: “The non-standard ‘crawl-delay’ robots.txt rule is not processed by Google’s crawlers.” Evidence for this claim Google does not support or process the non-standard crawl-delay robots.txt field. Scope: Google crawlers; other crawlers may support the field. Confidence: high · Verified: Google: robots.txt specifications

Worth being clear about the scope: it’s ignored no matter which user-agentA user agent is the HTTP request header a client (browser, crawler, or bot) sends to identify itself. For crawlers, a short user-agent token — a substring of that string — is what robots.txt rules actually target. group you put it in. A User-agent: Googlebot block with a Crawl-delay line is just as ignored as one under User-agent: *.

What to use instead for Google

Google’s 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 fully automatic now, tuned to your server’s health — and the old manual crawl-rate slider in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. was removed on January 8, 2024 (announced the prior November). So when you genuinely need 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. to back off, you have three levers:

  1. Fix the server. The real fix. If your server can take the load, you don’t need to throttle anything.
  2. Return 429, 500, or 503 for emergencies. Google’s Reduce the Googlebot crawl rate docs say to “return 500, 503, or 429 HTTP response status code instead of 200 to the crawl requests.” Googlebot reads these as “slow down” almost immediately. The hard rule: “We don’t recommend that you do this for a long period of time (meaning, longer than 1-2 days).” Sustained 5xx risks pages getting dropped (and Google Ads pausing). Evidence for this claim Google recommends temporarily returning 500, 503, or 429 to reduce crawl rate and warns against doing so for longer than one or two days. Scope: Temporary Googlebot overload response, not routine crawl management. Confidence: high · Verified: Google: Reduce Googlebot crawl rate
  3. File a crawl-rate reduction request through Search Console for a persistent problem. It’s slow, and it only reduces, never raises.

One trap to avoid: don’t use 401, 403, or 404 to throttle. Per Google’s HTTP status codes guide, “the 4xx status codes, except 429, have no effect on 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.,” and you should not “use 401 and 403 status codes for limiting the crawl rate.”

This is also why, in my crawl-rate guideCrawl 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., I treat crawl-delay as the thing not to use for Google — see that article for the full speed-up / slow-down playbook.

Bing documents a 1–20 second range

Current Bing Webmaster guidance documents crawl-delay values from 1–20 seconds. That does not make the field a portable standard: Google ignores it, and every other crawler needs its own documented confirmation.

Yandex dropped it in 2018

Yandex used to honor crawl-delay as a literal minimum number of seconds between requests — that’s the version of the fact you’ll still see repeated across most SEO blogs. It’s stale. Yandex’s own current documentation is explicit: “From February 22, 2018, Yandex doesn’t take into account the Crawl-delay directive.” Evidence for this claim Yandex stopped honoring the Crawl-delay directive on February 22, 2018, and now recommends setting crawl rate inside Yandex Webmaster instead. Scope: Yandex's crawler only; does not apply to Google, Bing, or other crawlers. Confidence: high · Verified: Yandex Webmaster: The Crawl-delay directive To set how fast Yandex’s bots crawl your site now, you use the crawl rate setting inside Yandex Webmaster directly — not robots.txt. So as of today, the honest scorecard is: Bing honors crawl-delay within its documented range, Google never did, and Yandex used to but stopped in 2018.

Other crawlers: SEO tools and AI bots

Plenty of well-behaved non-search-engine crawlers honor crawl-delay as a courtesy:

  • AhrefsBot and Semrush’s bot both respect it.
  • AI crawlersAI crawlers are bots from AI companies that fetch web pages to train language models, build AI-search indexes, or answer live user questions. They come in three categories, each with its own user-agent tokens and its own robots.txt controls. are a newer audience. Anthropic’s ClaudeBot is documented as supporting the non-standard crawl-delay directive. Others (GPTBot, Perplexity) should be checked against their own published docs rather than assumed.

The pattern: smaller, compliance-focused, or courtesy-minded crawlers tend to honor crawl-delay; the major search engines have largely moved to internal signals (Google) or richer manual tools (Bing). And none of this binds actual bad actors — scrapers that ignore robots.txt entirely will ignore your crawl-delay too.

The use case that’s left

So is crawl-delay dead? Not quite. It’s useless for Google, redundant-at-best for Bing (use Crawl Control), but it’s genuinely the simplest way to ask the broad middle — SEO tools, AI bots, and other minor crawlers that respect it — to ease off. If a specific tool’s bot is overrunning your server, a targeted User-agent: group with a crawl-delay is a reasonable first move:

User-agent: SomeBot
Crawl-delay: 10

Just remember it’s a request, not a guarantee, and it scopes per host and per user-agent group like everything else in robots.txt. For the broader efficiency picture — what bots actually cost you and who needs to care — see crawl-budget.

Add an expert note

Pin an expert quote

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