Applebot: Robots.txt & Crawl Policy Reference

AI Summary: Applebot is Apple's primary web crawler, used to power search features like Siri, Spotlight suggestions, and Safari. It is distinct from Applebot-Extended, which is specifically used for training Apple's generative AI models.

Role and policy boundary

Applebot indexes the web to provide search results across the Apple ecosystem. Allowing Applebot ensures your content is discoverable by users on iOS and macOS devices. If you want to appear in Siri and Spotlight but opt out of Apple's AI training, you should allow Applebot but block Applebot-Extended.

A robots rule is a declaration of intent; it does not replace authentication, authorization, or rate limiting. Start with a dedicated group:

User-agent: Applebot
Allow: /
Disallow: /staging/
Disallow: /internal/

To stop access for the entire site, use:

User-agent: Applebot
Disallow: /

Avoid assuming that User-agent: * expresses the same business intent. A wildcard can affect assistant and training crawlers too, and it makes later audits harder because the source of the decision is less specific.

Layered verification

Verify the same URL through each control plane instead of assuming that one green signal represents the whole request path. Compare the bot-specific robots group, the page-level metadata, and the response headers captured at the public edge.

Applebot strictly respects robots.txt and page-level meta tags. If Applebot is not explicitly mentioned in your robots.txt, it will follow instructions meant for Googlebot as a fallback. It also supports the crawl-delay directive.

The Policy Engine evaluates the selected user-agent, path scope, and the other supplied layers independently. It can therefore explain why a bot is allowed while another is blocked, rather than returning one blended website score.

Page-level directives can still override the intended outcome for indexing:

<meta name="robots" content="noindex, nofollow">

X-Robots-Tag: noindex, nofollow

If a response uses these tags, the report marks the result as blocked or conflicting even if the crawler-specific robots group is permissive. This is especially important for canonical pages served through an edge cache where headers may differ from the origin response.

WAF and Nginx remediation examples

{
  "description": "Observe applebot candidates",
  "expression": "lower(http.user_agent) contains \"applebot\"",
  "action": "log"
}

If you wish to log Applebot traffic for observability without blocking it, you can configure an Nginx rule:

if ($http_user_agent ~* "Applebot") {
    # Log Applebot access
    access_log /var/log/nginx/applebot.log;
}

Use your platform's actual middleware response pattern rather than copying this simplified example without review. Never place a secret, verification token, or internal policy identifier in a public response header.

Review checklist

Use this checklist after every policy change and after a CDN or WAF migration. Record the request URL, User-Agent, HTTP status, final redirect, and the exact evidence used to reach the decision.

Verify that the dedicated group appears before relying on a wildcard, test a representative public and private path, and compare live response headers with robots.txt. Keep the policy close to the content owner's intent and record whether the site wants discovery, citation, or no access at all.

Need to optimize your entire site for AI search visibility? Run a comprehensive audit with Geolify.ai.