Applebot
Applebot is a search-engine crawler operated by Apple. Its job is to find, fetch, and index web pages so they can be returned in organic search results.
Traffic is regular and bounded by your robots.txt. Allowing it is generally how your site stays discoverable through the corresponding search engine, blocking it almost always reduces visibility there.
For most sites, search-engine crawlers are still the largest source of bot traffic and the largest source of human visitors that follow.
See Applebot on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Known UA examples
example 1
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Continuous
Honors robots.txt
Yes
Honors Crawl-delay
Yes
Apple runs 7 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Link Unfurler
4Search Engine
1- ApplebotYou are here
Training Crawler
1Generic Crawler
1Share of AI bot traffic
3.3%
↑ 38% vs 12 mo ago
% of top sites blocking it
0.60%
↑ 100% vs 12 mo ago
Top page categories crawled
Search Engines as a category, share of all bot traffic
66%
↓ 6% vs 12 mo ago
Sum of every search engine we have public stats on. Compare to Applebot's individual trend above to see if it's pulling ahead of its category or falling behind.
Crawl-to-click ratio
95 : 1
For every 1,000 fetches, this agent sends ~11 human visits back. Cloudflare crawl-to-click data
Snapshot updated
2026-04
Connect Agent Analytics for daily, per-site numbers.
Should I let Applebot through?
In most cases, yes. Blocking traditional search crawlers reduces organic-search visibility. Allowing is the default for almost all sites. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Applebot affect my Google rankings?
Only on Apple Applebot feeds. Each search engine runs its own crawler, so blocking Applebot only removes you from that one index. Your visibility on Google, Bing, or anything else is untouched.
How do I confirm a request is really from Applebot?
Two checks. The User-Agent header should match a known Applebot string, and the request's source IP should fall inside Apple's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Apple publishes the ranges so you can validate at the CDN or edge.
What happens to my traffic if I block Applebot?
Your pages drop out of Apple's index, which means losing the organic share you get from that engine. Not catastrophic if Apple is a minor player, much more painful if it's a meaningful source of your traffic. Check your analytics for Apple's actual referral share before deciding.
How is Applebot different from Apple's other bots?
Apple splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Apple family above to see which ones actually matter for your site.
What's the cleanest way to control Applebot?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.