Verify Applebot IP Address

Verify if an IP address truly belongs to Apple, using official verification methods. Enter both IP address and User-Agent from your logs for the most accurate bot verification.

Applebot is Apple's official web crawler used to power search and content features across Apple services such as Siri, Spotlight Suggestions, and Safari. It crawls webpages to discover content, metadata, and structured information that enhance on-device and cloud-based search experiences. Crawl activity is generally moderate and focused on high-quality, publicly accessible content. Its purpose is to improve search relevance, answers, and suggestions across Apple’s ecosystem without operating a standalone public web search engine. Data crawled by Applebot may be utilized by Apple for foundational model training. Apple allows site owners to opt-out of having their content used for generative model training by disallowing Applebot-Extended in the robots.txt file. RobotSense.io verifies Applebot using Apple's official validation methods, ensuring only genuine Applebot traffic is identified.

This bot officially honors Crawl-Delay rule.

User Agent Examples

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15(KHTML, like Gecko) Version/17.4 Safari/605.1.15 (Applebot/0.1; +http://www.apple.com/go/applebot)

Mozilla/5.0 (iPhone; CPU iPhone OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4.1 Mobile/15E148 Safari/604.1 (Applebot/0.1; +http://www.apple.com/go/applebot)
Example user agent strings for Applebot

Robots.txt Configuration for Applebot

Robots.txt User-Agent:Applebot

Use this identifier in your robots.txt User-agent directive to target Applebot.

Recommended Configuration

Our recommended robots.txt configuration for Applebot:

User-agent: Applebot
Allow: /
User-agent: Applebot-Extended
Allow: /

Completely Block Applebot

Prevent this bot from crawling your entire site:

User-agent: Applebot
Disallow: /

Completely Allow Applebot

Allow this bot to crawl your entire site:

User-agent: Applebot
Allow: /

Block Specific Paths

Block this bot from specific directories or pages:

User-agent: Applebot
Disallow: /private/
Disallow: /admin/
Disallow: /api/

Allow Only Specific Paths

Block everything but allow specific directories:

User-agent: Applebot
Disallow: /
Allow: /public/
Allow: /blog/

Set Crawl Delay

Limit how frequently Applebot can request pages (in seconds):

User-agent: Applebot
Allow: /
Crawl-delay: 10

Note: This bot officially honors the Crawl-delay directive.

Frequently Asked Questions

What is Applebot, and why is it visiting my website?
Applebot is Apple's official web crawler, operated by Apple to discover and index web content for services such as Siri, Spotlight Suggestions, Safari search features, and other search experiences across Apple's ecosystem. It visits public websites to retrieve page content, metadata, and structured data that can improve search relevance and answer generation. Crawl activity is typically triggered by content discovery, link following, content updates, and ongoing index maintenance. For publicly accessible websites, Applebot traffic is generally expected and legitimate.
Is Applebot a legitimate bot, or is it commonly spoofed?
Applebot is a legitimate crawler officially operated by Apple. Like other well-known crawlers, its User-Agent string can be spoofed by attackers, scrapers, or automated tools attempting to bypass security controls or gain access to restricted content. Because User-Agent strings are easy to forge, they should never be used as the sole method of verification. Authenticity should be confirmed using DNS validation, IP ownership checks, or other operator-published verification methods. You can use Apple's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify Applebot visits.
How can I verify that a request is really coming from Applebot?
You can use Apple's recommended official methods to verify Applebot visits, these include: - IP range checks - Reverse DNS → forward DNS Do not use User-Agent based detection as that can be easily spoofed. Alternatively, you can use RobotSense.io API to easily verify Applebot and all other bots from Apple.
Should I allow or block Applebot on my website?
For most public websites, allowing Applebot is beneficial because it enables content to appear in Apple-powered search and discovery features. Websites that want visibility in Siri, Spotlight, and related Apple services generally allow crawling. Blocking may be appropriate when: - Crawl traffic creates unwanted server load. - Content is proprietary or sensitive. - The site contains private applications or internal APIs. - The website does not want participation in Apple's content discovery ecosystem. For most informational, business, and publisher websites, Applebot is considered a useful and low-risk crawler.
How can I control or block Applebot using robots.txt or other methods?
You can add a rule in your robots.txt, as given above to control (crawl-delay) or disallow Applebot. Applebot honors robots.txt directives. Also, you can use further controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.
How often does Applebot crawl websites, and can it impact server performance?
Applebot performs ongoing crawling rather than operating on a fixed public schedule. Crawl frequency depends on factors such as site popularity, content freshness, crawl history, and the rate at which content changes. Typical effects include: - Modest bandwidth consumption - Moderate request rates - Occasional bursts during discovery or recrawling For most websites, performance impact is minimal. Large websites, news publishers, and frequently updated platforms may observe more noticeable crawl activity in their server logs.
What happens if I block Applebot? SEO, visibility, and feature impact explained.
Blocking Applebot can reduce or eliminate your content's visibility within Apple-powered search experiences. Potential impacts include: - Reduced visibility in Siri results - Reduced visibility in Spotlight Suggestions - Less participation in Safari search-related features - Fewer opportunities for Apple services to discover updated content Blocking Applebot does not directly affect rankings in major search engines such as Google or Bing. However, it may limit how Apple users discover your content through Apple's ecosystem.
Does Applebot collect, scrape, or use my content for training or reuse?
Yes. Applebot retrieves publicly accessible page content, metadata, and structured information to support search and content discovery features across Apple products. Apple states that data crawled by Applebot may also be used to help train Apple's foundation models that power generative AI features. Website owners should be aware that: - Applebot indexes publicly available content. - Metadata and page content may be stored and processed. - Content may contribute to search and answer-generation systems. - Apple provides an opt-out mechanism for AI model training through the separate Applebot-Extended robots.txt directive. User-agent: Applebot-Extended Disallow: / Blocking Applebot-Extended prevents eligible crawled content from being used for Apple's generative AI model training while allowing normal Applebot indexing and search visibility to continue.

Other Apple Bots

Apple operates other crawlers you may also need to configure.

Similar Bots

Other Search bots from different operators.

Amzn-SearchBot

Search

by Amazon

[Amazon Bots can take upto 30 days to read your Robots.txt updates.] Amzn-SearchBot is Amazon’s web crawler used to discover and retrieve publicly available content for Amazon search and AI-related services. It fetches webpages to analyze text, metadata, and structured information that can support Amazon’s search features and machine learning systems. Crawl activity is typically moderate and focused on publicly accessible pages. Its purpose is to help Amazon improve content discovery, relevance, and information retrieval across its ecosystem. It ignores the global user agent (*) rule. RobotSense.io verifies Amzn-SearchBot using Amazon’s official validation methods, ensuring only genuine Amzn-SearchBot traffic is identified.

Bingbot

Search

by Microsoft

Bingbot is Microsoft’s primary web crawler, responsible for discovering and indexing content for Bing Search and other Microsoft services. The crawler fetches HTML, structured data, images, and metadata to understand page relevance and ranking signals. Crawl activity varies based on site authority, update frequency, and sitemap signals. Its purpose is to keep Bing’s search index fresh, accurate, and aligned with user search intent across Microsoft platforms. RobotSense.io verifies Bingbot using Microsoft’s official validation methods, ensuring only genuine Bingbot traffic is identified.

BingVideoPreview

Search

by Microsoft

BingVideoPreview is Microsoft’s crawler for fetching video-related content to generate previews, thumbnails, and metadata for Bing’s video search experiences. It retrieves video files, poster images, structured data, captions, and surrounding context. This crawler does not perform full-site indexing; instead, it focuses specifically on video assets and the information required to power Bing’s video carousels and preview interfaces. Activity is targeted and relatively low-volume, driven by pages that contain or reference video content. RobotSense.io verifies BingVideoPreview using Microsoft’s official validation methods, ensuring only genuine BingVideoPreview traffic is identified.

Google Favicon

Search

by Google

[This crawler is officially retired as per Google] Google Favicon is a specialized Google crawler that retrieves website favicons for use across Google Search, Chrome, and other Google products. It fetches small icon files such as favicon.ico or declared alternative icons in HTML. This bot does not index page content or affect Search rankings; its role is purely to collect icons that visually represent sites in SERPs and browser surfaces. Most sites allow it since its requests are lightweight. Crawl activity is minimal and typically occurs when Google detects new or updated favicon assets. RobotSense.io verifies Google Favicon using Google’s official validation methods, ensuring only genuine Google Favicon traffic is identified.

Google Publisher Center / GoogleProducer

Search

by Google

Google Publisher Center is a platform that allows news publishers to manage how their content appears across Google News surfaces. When publishers submit feeds, sections, or site updates, Google may fetch associated URLs using Publisher Center–related user-agents to verify content, metadata, and feed accuracy. These fetches are not broad crawls; they are targeted checks tied to publisher actions such as updating feeds, article structures, or publication settings. Blocking it can disrupt feed validation or delay updates in Google News. Activity is typically light, triggered by publisher configuration changes or system refresh cycles. It ignores robots.txt rules. RobotSense.io verifies Google Publisher Center / GoogleProducer using Google’s official validation methods, ensuring only genuine Google Publisher Center / GoogleProducer traffic is identified.

Google StoreBot

Search

by Google

Google StoreBot is Google’s crawler responsible for fetching and validating data related to product listings, merchant feeds, and eCommerce pages used across Google Shopping surfaces. It helps Google evaluate product availability, pricing, structured data, and landing page quality. StoreBot works alongside Merchant Center systems to ensure product information is accurate, up-to-date, and compliant with Google’s listing requirements. Crawl behavior is focused, lightweight, and typically triggered by updates to product feeds or changes detected on merchant landing pages. RobotSense.io verifies Google StoreBot using Google’s official validation methods, ensuring only genuine Google StoreBot traffic is identified.