Applebot-Extended
Operated by Apple
Quick Facts
- User-Agent:
- Applebot-Extended
- Category:
- Search Engines
- Operator:
- Apple
- Safety:
- Caution
- Blocking Impact:
- Critical - Blocking removes you from search results
- SEO Impact Score:
- 10/10
- Official docs:
- support.apple.com
What is Applebot-Extended?
Applebot-Extended is a secondary user-agent used by Apple. It allows web publishers to control how their content is used for training Apple's generative AI models while still remaining in search results.
Applebot-Extended is a secondary user-agent used by Apple. It allows web publishers to control how their content is used for training Apple's generative AI models while still remaining in search results.
Applebot-Extended is a production-grade search engine crawler operated by Apple. It uses a distributed crawl infrastructure that respects crawl-delay directives, follows RFC 9309 (robots.txt) spec, and processes Sitemaps to prioritise fresh content. The user-agent string Applebot-Extended must be whitelisted if your site uses rate-limiting or WAF rules. Blocking impact is Critical - Blocking removes you from search results.
What happens if you block Applebot-Extended?
How to block Applebot-Extended with robots.txt
<code>User-agent: Applebot-Extended</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Applebot-Extended safe to allow?
What does Applebot-Extended do?
Understanding Applebot-Extended's purpose helps you decide whether to allow or block it.
- Crawls and indexes web pages for search results
- Discovers new and updated content on your website
- Analyzes page structure, content, and links for ranking
- Renders JavaScript to understand dynamic content
- Checks for mobile-friendliness and page speed
Frequently Asked Questions
What is the official user-agent string for Applebot-Extended?
Applebot-Extended. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Applebot-Extended by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.Is Applebot-Extended safe?
Will blocking Applebot-Extended hurt my SEO?
How do I block Applebot-Extended in robots.txt?
/robots.txt file:
User-agent: Applebot-Extended Disallow: /This instructs Applebot-Extended not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g.,
Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.Does Applebot-Extended respect robots.txt?
How do I verify if Applebot-Extended is crawling my site?
Applebot-Extended (case-insensitive grep: grep -i "Applebot-Extended" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Applebot-Extended specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).What is the crawl frequency of Applebot-Extended?
Can I block Applebot-Extended from specific pages only?
Disallow: / you can restrict Applebot-Extended to specific paths:
User-agent: Applebot-Extended Disallow: /private/ Disallow: /staging/ Allow: /This allows Applebot-Extended everywhere except the listed paths. Path matching in robots.txt uses prefix matching -
Disallow: /private/ blocks /private/page.html but NOT /public/private/.How do I check if Applebot-Extended is blocked by my robots.txt?
https://aicrawlercheck.com/robots.txt and scanning for Applebot-Extended entries. If a block exists, immediately test it against your most important URLs using the Google Search Console URL Inspection tool.My site is blocked by Applebot-Extended in Search Console - what do I do?
yourdomain.com/robots.txt and look for any User-agent: Applebot-Extended or User-agent: * Disallow rules covering your key pages.
2. Remove or restrict the blocking rules.
3. Validate via Google Search Console → robots.txt Tester.
4. Request re-indexing using the URL Inspection tool.
5. Wait 1-2 weeks for re-crawl. Monitor Coverage report for recovery.