Applebot

What Applebot does

Applebot indexes public pages so Apple's ecosystem can surface them in Siri answers, Spotlight results, and Safari suggestions. Apple documents it and honors robots.txt. Content used for Apple's AI model training is controlled separately via the Applebot-Extended token.

Why it visits your site

Feeding search features across iOS and macOS.

The bigger picture: search engine crawlers

Search crawlers remain the one category with a decades-old, well-understood bargain: they consume crawl budget and return ranked visibility. Everything about them is comparatively mature - published IP ranges, verification methods, granular directives, webmaster consoles. Blocking them is almost always self-harm, which is precisely why they need to be cleanly separated from AI crawlers in your data: a blanket bot block that catches Googlebot costs you your organic channel.

The complication the AI era added is that search indexes now feed AI features too - AI Overviews draw on Google's index, Copilot on Bing's. Operators have answered with control tokens that split AI use from search use of the same crawl. The practical upshot: your lever for AI concerns is usually a token, not a block on the search crawler itself.

Should you block it?

Blocking Applebot removes you from Siri and Spotlight surfaces while saving you essentially nothing. If your concern is AI training, disallow Applebot-Extended instead and keep the search visibility.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask Applebot to stay away:

User-agent: Applebot
Disallow: /

Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.

How to see Applebot traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every Applebot request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because Applebot doesn't run scripts.

Viz's answer is the request log: filter to Applebot and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.