Does doordash.com block ChatGPT?
doordash.com permits all 30 tracked AI crawlers. Nothing in its robots.txt restricts training, search indexing or on-demand fetching by the operators tracked here.
That is exactly the median across the 1671 sites in this dataset. Resolved from https://doordash.com/robots.txt on 11 November 2026.
Does doordash.com block each AI product?
| AI product | Position in robots.txt | Crawlers checked |
|---|---|---|
| ChatGPT | Allows | 3 |
| Claude | Allows | 3 |
| Perplexity | Allows | 2 |
| Gemini and Google AI | Allows | 3 |
| Microsoft Copilot | Allows | 1 |
| Apple Intelligence | Allows | 1 |
| Meta AI | Allows | 2 |
Has doordash.com changed its AI crawler rules?
We read this file every week. Between 17 August 2026 and 11 November 2026 we recorded no lasting change in which AI crawlers it blocks. See which sites did change their rules.
What doordash.com's robots.txt says about each AI crawler
A crawler named directly in its own group is governed by that group. One not named falls back to the wildcard group. Where neither exists the crawler is reported as not listed — no policy has been expressed, and in practice most crawlers will proceed.
| User-agent | Operator | Purpose | Access | Decided by |
|---|---|---|---|---|
OAI-SearchBot | OpenAI | search indexing | Allowed | wildcard policy |
GPTBot | OpenAI | model training | Allowed | wildcard policy |
ChatGPT-User | OpenAI | on-demand fetch | Allowed | wildcard policy |
Claude-SearchBot | Anthropic | search indexing | Allowed | wildcard policy |
ClaudeBot | Anthropic | model training | Allowed | wildcard policy |
Claude-User | Anthropic | on-demand fetch | Allowed | wildcard policy |
PerplexityBot | Perplexity | search indexing | Allowed | wildcard policy |
Perplexity-User | Perplexity | on-demand fetch | Allowed | wildcard policy |
Google-Extended | Gemini training control | Allowed | wildcard policy | |
Bingbot | Microsoft | Copilot search index | Allowed | wildcard policy |
Applebot-Extended | Apple | Apple Intelligence control | Allowed | wildcard policy |
Meta-ExternalAgent | Meta | model training | Allowed | wildcard policy |
Amazonbot | Amazon | model training | Allowed | wildcard policy |
Bytespider | ByteDance | model training | Allowed | wildcard policy |
CCBot | Common Crawl | training dataset | Allowed | wildcard policy |
GoogleOther | research and development fetch | Allowed | wildcard policy | |
Google-CloudVertexBot | Vertex AI on-demand fetch | Allowed | wildcard policy | |
Meta-ExternalFetcher | Meta | on-demand fetch | Allowed | wildcard policy |
MistralAI-User | Mistral AI | on-demand fetch | Allowed | wildcard policy |
cohere-ai | Cohere | model training | Allowed | wildcard policy |
DuckAssistBot | DuckDuckGo | on-demand fetch | Allowed | wildcard policy |
YouBot | You.com | search indexing | Allowed | wildcard policy |
Timpibot | Timpi | training dataset | Allowed | wildcard policy |
AI2Bot | Allen Institute for AI | model training | Allowed | wildcard policy |
Diffbot | Diffbot | structured-data extraction | Allowed | wildcard policy |
ImagesiftBot | ImageSift | training dataset | Allowed | wildcard policy |
PetalBot | Huawei | search indexing | Allowed | wildcard policy |
Omgilibot | Webz.io | training dataset | Allowed | wildcard policy |
ElevenlabsCrawler | ElevenLabs | model training | Allowed | wildcard policy |
ElevenlabsBot | ElevenLabs | on-demand fetch | Allowed | wildcard policy |
Does doordash.com allow AI training?
For each AI company with both kinds of crawler: whether this robots.txt lets its training crawlers in, and whether it lets in the crawlers behind its answers.
| AI company | Training | Answers |
|---|---|---|
| OpenAI | Allowed GPTBot | Allowed OAI-SearchBot, ChatGPT-User |
| Anthropic | Allowed ClaudeBot | Allowed Claude-SearchBot, Claude-User |
| Meta | Allowed Meta-ExternalAgent | Allowed Meta-ExternalFetcher |
| ElevenLabs | Allowed ElevenlabsCrawler | Allowed ElevenlabsBot |
Google is not in this table: its AI answers read what Googlebot may read, and its training control is Google-Extended, in the full list.
The shared AI-training signal
On 11 November 2026 this file had no group for __usage_ai-training, so it expresses no preference with the shared signal. A rule under User-agent: * is not read as one, and each company's own crawler rules above keep their meaning.
Google announced this signal on 30 October 2026 and plans to support it with other AI companies in 2027. It is a draft standard and no company has confirmed it reads it yet, so this is what the file says, not what happens to the content.
What this does and does not tell you
It tells you what doordash.com states in its robots.txt, which is the file every well-behaved AI crawler consults before fetching. It is a stated preference and a voluntary protocol — not an access control, and not evidence about what any crawler actually did.
It also says nothing about whether the content is useful to an answer engine once fetched. Access is the precondition; extractable passages, visible dates, named authorship and sourced claims decide whether a reachable page is actually cited. Sign up for a free AI visibility report to see the original answers and which pages they cite.
Finally, robots.txt changes. This page reflects doordash.com as it was on 11 November 2026. To see the current position, inspect the domain’s live robots.txt file and its matching rules.
Check your own site
Run the free AI crawler checker on your own site for the same verdict on every crawler, and the robots.txt lines to change if one is blocked by mistake. The ChatGPT citation guide explains the distinction between training and search access.
Browse the full study of 1671 measured domains, or the e-commerce and retail category, to see how this compares.
Embed this result
A live badge for doordash.com, updated whenever this report refreshes. Paste it into a README or site footer:
<a href="https://www.indexhalo.com/ai-crawler-report/doordash.com/">
<img src="https://www.indexhalo.com/badge/ai-crawler-access/doordash.com.svg"
alt="AI crawler access for doordash.com: 100%" height="20">
</a>