Applebot — Apple's ai search indexer

Applebot is a polite, well-identified crawler with published verification. Its search payoff is placement in Siri answers and Spotlight web suggestions across Apple's device base.

Applebot-Extended, like Google-Extended, never fetches anything — disallowing it simply withdraws training consent for content Applebot already crawls.

Applebot identifies itself with the following user-agent string:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko; compatible; Applebot/0.1; +http://www.apple.com/go/applebot)

Never trust the user-agent string alone. Scrapers routinely impersonate well-known crawlers to inherit their access. Genuine Applebot traffic originates from Apple's 17.0.0.0/8 address space and reverse-resolves to *.applebot.apple.com.

Note that most AI crawlers and fetchers, Applebot included, do not execute JavaScript — so this traffic is invisible to GA4 and every script-based analytics tool. Server logs, CDN analytics, or a dedicated bot-analytics layer are the only places you will see it. For the full picture of measuring AI-driven visits, see our guide on how to track AI traffic.

To refuse Applebot access to your entire site, add this to your robots.txt:

User-agent: Applebot
Disallow: /

To restrict it from specific sections only (for example, premium content) while leaving the rest open:

User-agent: Applebot
Disallow: /premium/
Disallow: /members/

The case for blocking: Blocking Applebot itself sacrifices Siri and Spotlight presence for little gain. The meaningful decision is the Extended token, where the free-training argument applies.

The case for allowing or monetizing: Keep the visibility, withhold the training consent — the standard two-token play. Apple has negotiated content licensing for training elsewhere, so consent has market value.