Applebot robots.txt Rules for Siri, Spotlight, and Safari

Applebot is Apple’s search crawler for experiences including Siri, Spotlight, and Safari. It follows Applebot-specific robots.txt rules, falls back to Googlebot rules when no Applebot group exists, and does not support Crawl-delay.

Public website content available to Apple search experiences while selected private paths remain blocked

Copy-paste robots.txt example

User-agent: Applebot
Allow: /
Disallow: /private/
Disallow: /account/

What Applebot does

Applebot crawls public web pages for search and discovery features across Apple products, including Siri, Spotlight, and Safari. Allowing it can help eligible pages appear when Apple users search or request current web information. Blocking Applebot affects this Apple discovery path, but it does not directly block Googlebot, Bingbot, or other crawlers with separate robots.txt groups.

How Applebot reads robots.txt

Applebot respects standard robots.txt directives addressed to Applebot. A specific Applebot group is the clearest way to express your policy. Apple also documents an important fallback: when robots.txt does not mention Applebot but does contain rules for Googlebot, Applebot follows the Googlebot instructions. That means an old Googlebot restriction can influence Applebot even when no Applebot token appears in the file.

Applebot does not support the non-standard Crawl-delay directive. If request volume becomes a concern, avoid relying on Crawl-delay for this agent. Apple says its crawler adjusts automatically when a server slows down or returns errors.

Allow public pages and exclude private sections

The example below keeps general Apple search discovery open while excluding two non-public directories. Replace the paths with real sections from your site. For confidential content, robots.txt is not enough: use authentication, authorization, and server-side access controls because the file is only an instruction to compliant crawlers.

Publish robots.txt at the root of each host, such as https://example.com/robots.txt. A rule on the main domain does not automatically apply to docs.example.com or another subdomain.

Rendering and indexing controls

Applebot may render pages in a browser. Blocking required JavaScript, CSS, images, or XHR endpoints can prevent correct rendering even when the HTML page itself is allowed. Use the robots.txt checker to catch broad resource restrictions before publishing them.

Robots.txt controls crawling, not every indexing or presentation decision. Applebot also supports page-level robots meta directives such as noindex. Apple separately documents nosnippet and paywall structured data for specific content-use and display scenarios.

Applebot versus Applebot-Extended

Do not treat these tokens as interchangeable. Applebot performs the actual search crawl. Applebot-Extended is a separate control for whether data crawled by Applebot may be used to train Apple’s general-purpose foundation models. You can allow Applebot for search while disallowing Applebot-Extended for training use.

Verification checklist

  1. Place robots.txt at the host root.
  2. Add an explicit Applebot group instead of relying unintentionally on Googlebot fallback.
  3. Keep render-critical assets accessible.
  4. Check each subdomain separately.
  5. Run the published file through the checker.

FAQ

What products use Applebot data?

Apple says Applebot supports search technology across experiences including Siri, Spotlight, and Safari.

Does Applebot follow Googlebot rules?

Yes, when robots.txt does not mention Applebot but does contain Googlebot instructions, Applebot follows the Googlebot rules.

Does Applebot support Crawl-delay?

No. Apple states that Applebot does not follow Crawl-delay and instead adjusts its crawl rate automatically when a site slows down or returns errors.

Can I allow Applebot but block Apple AI training use?

Yes. Keep Applebot allowed for search and add a separate Disallow rule for Applebot-Extended.

Will robots.txt protect private content from Applebot?

It can instruct Applebot not to crawl a path, but it is not security. Private content still needs authentication and server-side authorization.

Related tools

Related pages

Applebot-crawled content remaining available for search while a separate model-training route is blocked Applebot-Extended robots.txt Opt-Out

Applebot-Extended is not a crawler. It is a robots.txt control that tells Apple not to use Applebot-crawled content to train its general-purpose foundation models. Blocking it does not remove pages from Apple search results.

Robots.txt checker inspecting a website and reporting allowed and blocked crawler access Robots.txt Checker for AI Crawlers

Enter a domain, choose a crawler, and test a path. The checker downloads the live robots.txt file, finds the applicable User-agent group and most specific rule, then explains whether access is allowed or blocked.

Public pages moving through AI search discovery and technical access toward possible source citation robots.txt for AI Search Visibility and Citations

To support AI search visibility, allow each provider’s documented search crawler—such as OAI-SearchBot, Claude-SearchBot, and PerplexityBot—while keeping Googlebot and Bingbot accessible. Robots.txt only permits crawling; it does not guarantee indexing, citation, ranking, or access through a firewall.

Diagnostic flow checking a crawler token, URL rule match, server response, and access logs How to Check Whether AI Crawlers Are Blocked

Fetch the live robots.txt file, select the crawler’s exact product token, and test the specific URL against the matching group and longest Allow or Disallow rule. Then check HTTP responses, caching, firewall rules, and logs, because a crawler may be allowed by robots.txt yet blocked by the server—or disallowed by robots.txt while an unidentified scraper still reaches the page.

Crawler requests reaching a server at measured intervals while a separate lane shows that Crawl-delay support varies Crawl-delay in robots.txt: Meaning and Crawler Support

Crawl-delay asks a crawler to wait between requests, but it is a non-standard robots.txt extension and support varies by crawler. Use it only for a documented user-agent and only when server logs show that crawl rate is a real problem.