Decision guide
Applebot vs. Applebot-Extended: Search/Siri vs. Apple Intelligence
Apple separates its long-standing search crawler from a newer, generative-AI-specific opt-out token. A decision guide for telling them apart.
Apple operates Applebot, a long-established crawler for Siri and Spotlight Suggestions, and a
newer, separate token specifically for generative AI training opt-out.
The two tokens
Applebot— Apple’s general-purpose crawler, used since well before the current wave of generative AI products, for features like Siri and Spotlight Suggestions. Apple’s own documentation additionally states that data it crawls “may be used to provide additional context and up-to-date content when AI models are used to generate output for display in Apple products and services” — a narrower, context-supplying role, distinct from model training.Applebot-Extended— controls use of website content for training Apple Intelligence and other Apple generative AI models, independent of the baseApplebotcrawl.
The decision
- Disallow
Applebot-Extendedif you want to opt content out of Apple’s generative AI training specifically, while keeping Siri/Spotlight functionality intact. - Disallowing
Applebotitself affects both the older Search/Siri features it was built for and the AI-generated-output context-supplying role described above — a broader decision than an AI-training-specific opt-out, and not one that leaves AI-adjacent uses entirely untouched. - If your goal is narrowly “opt out of AI model training, keep everything else,”
Applebot- Extendedis the correct, narrower token — the same pattern as Google’sGoogle-Extendednext toGooglebot. It does not, however, opt out of the base crawler’s separate context-supplying use described above; there is currently no narrower token for that specific use, only the broaderApplebotdisallow.
Common mistake CrawlPact flags
Because Applebot-Extended is the newer of the two tokens, some robots.txt files only contain
a rule for Applebot and assume it also covers the newer AI-training opt-out. It doesn’t — the
two tokens are matched independently, so an AI-training opt-out intent requires an explicit
Applebot-Extended rule.
Check which of the two your own robots.txt actually covers with the
AI crawler checker.
Related guides
- Amazonbot vs. Amzn-SearchBot vs. Amzn-User: which should you block?Amazon runs three crawler tokens with different purposes and different robots.txt compliance. How to configure Amazonbot, Amzn-SearchBot and Amzn-User.
- Blocking AI training while staying visible in AI searchChoosing between CrawlPact's presets when the goal is opting out of model training without losing AI-search discoverability.
- ClaudeBot vs. Claude-User vs. Claude-SearchBot: which should you block?Anthropic operates three separate crawler tokens for training, user-triggered retrieval, and search. A decision guide for configuring each independently.
See how this applies to your own site
Run a free audit to check your declared AI crawler policy against your own domain.