Applebot
Apple · AI search Training · robots.txt: Yes
Crawls and renders web pages for search in Apple's products such as Spotlight, Siri and Safari; the same crawl may also feed Apple's AI features.
Block Applebot
User-agent: Applebot
Disallow: /
Blocking Applebot removes your pages from search in Spotlight, Siri and Safari. If you only want to opt out of AI training, Apple's documented route is to disallow Applebot-Extended and keep Applebot allowed.
Allow Applebot
User-agent: Applebot
Allow: /
An allow group only changes anything if a broader rule would block Applebot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks Applebot on a given path, and which line decides.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches Applebot, spelled as in the User-Agent Apple documents (“Applebot/”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake Applebot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Apple's published addresses.
Addresses in the “only the real one” rules: Apple's list search.developer.apple.com/applebot.json, 24 ranges, fetched 8 Oct 2026, list dated 15 Sep 2026. Operators change their lists; compare the date with the live list before you rely on it.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 7 block Applebot from the whole site by name, 20 block it through their User-agent: * group, and 25 name it with partial rules (some paths closed, the home page open). 5 more name it only to let it in.
7
block it by name 1.4%
20
block it through * 3.9%
25
name it, partial rules 4.9%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block Applebot by name
- fbcdn.net rank 12
- msn.com rank 72
- uol.com.br rank 556
- usatoday.com rank 603
- cnet.com rank 734
- repubblica.it rank 965
- corriere.it rank 969
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Apple
- Purpose
- AI search index + Model training
Apple says Applebot's data powers search in Spotlight, Siri and Safari, may help train Apple's foundation models (opt out with Applebot-Extended), and may be used as context for AI-generated answers (opt out with nosnippet).
- Obeys robots.txt
- Yes. Apple says Applebot respects robots.txt in general search crawls aimed at it. If your robots.txt does not mention Applebot but does mention Googlebot, Applebot follows the Googlebot rules. It does not follow Crawl-delay. The separate iTMS user agent (Apple Podcasts) does not follow robots.txt.
- In your server logs
- The user-agent string contains "Applebot/" followed by a version (for example Applebot/0.1).
- How to verify it
- Apple says Applebot traffic is identified by reverse DNS in the applebot.apple.com domain (check with the host command both ways), or by matching the IP against Apple's published CIDR list.
Published list: search.developer.apple.com/applebot.json — 24 IPv4 ranges when we fetched it, list dated 15 Sep 2026. Always match against the live list; operators update them. To count real and fake Applebot requests in your own server log against this list, drop the log into the log reader.
What Apple says
Quoted word for word from the operator's documentation.
“The data crawled by Applebot is used to power various features, such as the search technology integrated into many user experiences in Appleʼs ecosystem including Spotlight, Siri, and Safari. Enabling Applebot in robots.txt allows website content to appear in search results for Apple users around the world in these products.”
“The data crawled by Applebot may also be used to help train Apple foundation models powering generative AI features across Apple products, including Apple Intelligence, Services, and Developer Tools. Web publishers can opt-out from having their content used to train generative foundation models by disallowing Applebot-Extended in the robots.txt file.”
“Applebot crawled data 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.”
“Applebot respects standard robots.txt directives in general search crawls that are targeted at Applebot.”
“If robots instructions don't mention Applebot but mention Googlebot, the Apple robot will follow Googlebot instructions. Applebot does not follow crawl-delay.”
“The iTMS user agent does not follow robots.txt, as it is not a general search crawler.”
“The user-agent string contains ”Applebot” and other information.”
“Traffic coming from Applebot is generally identified by using reverse DNS in the *. applebot.apple.com domain.”
“Another way is to match the IP address with a CIDR prefix contained in the following JSON file: Applebot IP CIDRs.”
Sources
- Apple Support: About Applebot — fetched and checked 2026-09-22
- Apple: Applebot IP CIDRs (applebot.json) — fetched and checked 2026-09-22