resulthack

All AI crawlers /

Applebot-Extended

Apple · Training · robots.txt: Yes

A robots.txt control token, not a crawler: it decides whether pages Applebot has crawled may be used to train Apple's generative AI foundation models.

Block Applebot-Extended

User-agent: Applebot-Extended
Disallow: /

Disallowing Applebot-Extended opts out of training Apple's foundation models, but Apple says your pages can still appear in its search results and the rule is not a ranking factor. To keep content out of AI-generated "broad world knowledge" answers in Siri and Search, Apple points to the nosnippet robots meta tag instead.

Allow Applebot-Extended

User-agent: Applebot-Extended
Allow: /

An allow group only changes anything if a broader rule would block Applebot-Extended. 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.

Block or allow it at the server

No server rule for Applebot-Extended. Apple says: Applebot-Extended does not crawl webpages. Webpages that disallow Applebot-Extended can still be included in search results. Applebot-Extended is only used to determine how to use the data crawled by the Applebot user agent. (Apple Support: About Applebot, checked 2026-09-22). A server rule acts on requests, and Apple documents Applebot-Extended as a robots.txt control with no requests of its own to match, so the robots.txt lines above are the way to use it.

The fetching is done by Applebot, whose page has server rules. They refuse that crawler itself, with everything else it fetches for.

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 /. 59 block Applebot-Extended from the whole site by name, 26 block it through their User-agent: * group, and 17 name it with partial rules (some paths closed, the home page open). 6 more name it only to let it in.

59

block it by name 11.6%

26

block it through * 5.1%

17

name it, partial rules 3.3%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block Applebot-Extended by name

  1. fbcdn.net rank 12
  2. whatsapp.net rank 32
  3. whatsapp.com rank 57
  4. tiktok.com rank 58
  5. msn.com rank 72
  6. snapchat.com rank 134
  7. tumblr.com rank 156
  8. nytimes.com rank 157
  9. t-online.de rank 201
  10. medium.com rank 203

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
Model training
Obeys robots.txt
Yes. Applebot-Extended exists only as a robots.txt rule; Apple says it does not crawl webpages and is used only to decide how data crawled by Applebot is used.
In your server logs
None of its own: Apple says Applebot-Extended does not crawl webpages. The fetching is done by Applebot.
How to verify it
There is no Applebot-Extended traffic to verify. Applebot itself is identified by reverse DNS in the applebot.apple.com domain, 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-Extended 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.

“With Applebot-Extended, web publishers can choose to opt out of their website content being used to train Apple’s general purpose foundation models powering generative AI features across Apple products, including Apple Intelligence, Services, and Developer Tools.”

“Applebot-Extended does not crawl webpages. Webpages that disallow Applebot-Extended can still be included in search results. Applebot-Extended is only used to determine how to use the data crawled by the Applebot user agent.”

“Site rules for Applebot-Extended are not considered in ranking for Search.”

“Web publishers can opt out of their content being used in these broad world knowledge answers by applying the nosnippet meta tag to specific content.”

“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

Other crawlers from Apple

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy