Crawl-delay in robots.txt: Meaning and Crawler Support
Crawl-delay asks a crawler to wait between requests, but it is a non-standard robots.txt extension and support varies by crawler. Use it only for a documented user-agent and only when server logs show that crawl rate is a real problem.
Crawl-delay is a robots.txt extension intended to reduce how frequently a crawler requests pages from a host. A typical value represents a delay in seconds, but the exact interpretation and allowed range depend on the crawler. It is not part of the core Robots Exclusion Protocol standardized by RFC 9309, so there is no universal behavior.
This makes support the first question to answer. Bing documents that Bingbot honors Crawl-delay. Some AI crawler operators also document support for their own agents. Other crawlers ignore it, and Googlebot is not configured through this directive. Always consult the current documentation for the exact user-agent you are targeting.
How to scope the rule
Place the directive inside the relevant User-agent group. Do not add it under User-agent: * unless you intentionally want every crawler that recognizes the extension to inherit the delay.
User-agent: Bingbot
Crawl-delay: 5
A targeted group is safer because search crawlers, SEO audit bots, archive crawlers, and AI crawlers can have different traffic patterns and different support rules.
Why a large delay can be harmful
An aggressive value can slow discovery of new pages, price changes, corrections, deleted URLs, canonical updates, and sitemap changes. On a large site, a crawler may need days or weeks longer to revisit important content. That can be more damaging than a short temporary increase in server load.
Use access rules for URLs that should not be crawled at all. Use Crawl-delay only for a crawler that should retain access but needs to request pages more slowly. These are separate policy decisions.
Better first checks
Before adding a delay, inspect server logs. Confirm the crawler identity, request volume, response times, status codes, and the paths causing load. Many crawl problems are actually caused by infinite URL spaces, faceted navigation, session parameters, slow templates, redirect chains, or error responses.
For Googlebot, use Google’s documented crawl-rate and host-load guidance rather than relying on Crawl-delay. For Bingbot, Bing Webmaster Tools provides crawl controls in addition to robots.txt. If the traffic is malicious or ignores robots.txt, use rate limiting, authentication, firewall rules, or application-level controls instead.
Common mistakes
Assuming every crawler supports the directive.
Applying a large delay to User-agent: *.
Using Crawl-delay instead of fixing duplicate or infinite URLs.
Trusting a claimed User-Agent without verifying the source.
Expecting a polite crawl instruction to stop abusive traffic.
How to verify the effect
Check the operator’s current crawler documentation.
Publish the directive in the correct user-agent group.
Measure request spacing in server logs after the crawler revisits robots.txt.
Remove or reduce the value if important pages are being discovered too slowly.
FAQ
Is Crawl-delay part of the official robots.txt standard?
No. RFC 9309 standardizes core robots.txt behavior, while Crawl-delay is a non-standard extension. Support and interpretation vary by crawler.
Does Googlebot support Crawl-delay?
Googlebot is not controlled through the Crawl-delay directive. Use Google’s documented crawl-rate and host-load guidance instead.
Does Bingbot support Crawl-delay?
Yes. Bing documents support for Crawl-delay, but a high value can significantly slow discovery and recrawling.
Should Crawl-delay be placed under User-agent: *?
Usually not. A crawler-specific group is safer because wildcard placement may affect several crawlers that recognize the extension.
Can Crawl-delay stop abusive scraping?
No. It is a voluntary instruction for compliant crawlers. Use server-side rate limiting, authentication, firewall controls, or blocking for abusive traffic.
We use essential storage for security and core features. With your permission, we may also use analytics and advertising technologies. Rejecting optional technologies does not block access to the site.
Non-essential categories are off unless you choose to enable them. You can return to these settings at any time from the footer.
Global Privacy Control is active.Your browser has requested an opt-out from sale, sharing, and targeted advertising. Advertising remains disabled.
Strictly necessary
Supports security, server sessions, form protection, administrator sign-in, and remembering your privacy choice.
Analytics
Allows Google Analytics to measure visits and interactions so the site can be improved. It is not loaded before permission.
Advertising and cross-site measurement
Allows advertising technologies when they are configured. This may involve ad delivery, fraud prevention, measurement, personalization, or cross-context advertising.
Your choice is stored for 180 days using a first-party preference cookie. A material policy change can ask you to choose again.