Apple updated its Applebot documentation on June 8, 2026, and almost nobody noticed. The update added a single sentence that changes the competitive landscape for B2B visibility. Applebot crawled data, the documentation now reads, is used for “answering broad world knowledge questions in Siri and Search.”
That sentence describes a retrieval-augmented generation pipeline. Applebot crawls the web, feeds content into Apple’s foundation models, and Siri generates answers with links to source websites. The Siri that used to set timers and mishear you now reads the open web and replies.
At WWDC 2026, Apple confirmed Siri AI runs on Apple Foundation Models built through what they called a “deep collaboration” with Google, using the technology behind Gemini. Siri is the face. Gemini is a large part of the engine. And the distribution behind that face is unlike anything in consumer AI.
The Surface Most Companies Haven’t Indexed For
The AI visibility conversation has focused on five platforms: ChatGPT, Google Gemini, Perplexity, Claude, and Grok. Combined, those platforms account for roughly 87% of US AI chatbot market share, according to Statcounter data from June 2026.
Microsoft Copilot holds another 12.6%. No consumer API exists to probe how it answers brand queries.
Siri AI is the new entry. And it doesn’t show up in chatbot market share data because it isn’t a chatbot. It’s a voice and text assistant embedded across 2.5 billion active Apple devices. Counterpoint Research puts the active iPhone installed base above one billion worldwide. Pew Research found that 73% of US adults are open to AI assisting with everyday tasks, even though far fewer use standalone AI tools regularly.
The user never has to choose Siri. It ships switched on. A large share of the questions that used to become a Google search and a click to somebody’s website will resolve inside a Siri card without the browser ever opening. If you’re tracking AI-referred traffic in your analytics, expect Siri as a referrer to start appearing in the next few months.
What Applebot Actually Does Now
The June 8 documentation update formalized three distinct functions for Applebot:
1. Search indexing (existing). Applebot crawls pages for Spotlight, Safari suggestions, and Siri suggestions. This has been in place since Applebot first surfaced in 2015.
2. AI training (new). Apple states that crawled data is “also used to help train Apple foundation models powering generative AI features across Apple products, including Apple Intelligence, Services, and Developer Tools.” Apple added a separate crawler user-agent, Applebot-Extended, that publishers can disallow to opt out of training. Disallowing Applebot-Extended does not affect search indexing.
3. Real-time AI retrieval (new). Apple states that crawled data is “used to provide additional context and up-to-date content when AI models are used to generate output for display in Apple products and services.” This is the RAG pipeline. Siri pulls current web content, feeds it to the model, and generates answers with source links. Publishers can opt out using the nosnippet meta tag, which prevents Apple from using page content as AI context.
These three functions are governed by independent controls. Blocking AI training does not block AI retrieval. Blocking AI retrieval does not block search indexing. Each lever operates without overriding the others.
The nosnippet Problem
Apple’s opt-out architecture gives publishers two choices: allow Siri to use your content for AI answers, or use nosnippet and disappear from Siri’s generated responses entirely.
There is no middle ground. The documentation explicitly states that nosnippet operates at the page level only. Section-level markup using schema.org’s hasPart property is not supported. You cannot selectively exclude a sidebar or a paragraph while keeping the rest of the page eligible.
For companies that want to be cited in Siri’s answers, this means the entire page is in. For companies that don’t, the entire page is out.
This mirrors the context gap problem we see across every AI surface. The companies that win are the ones whose content is structured, extractable, and legible to a crawler that reads for context, not keywords. Applebot renders JavaScript, respects schema.org structured data, and follows standard robots directives. It behaves like a modern web crawler. Most company websites were not built for modern web crawlers.
How Applebot Differs from Googlebot and GPTBot
Applebot shares characteristics with both Googlebot and OpenAI’s GPTBot, but the differences matter for visibility work.
| Behavior | Googlebot | GPTBot | Applebot |
|---|---|---|---|
| Renders JavaScript | Yes | No | Yes |
| Respects crawl-delay | Yes | No | No |
| Follows Googlebot rules if no Applebot rules | N/A | No | Yes |
| Separate user-agent for AI training | N/A | N/A | Yes (Applebot-Extended) |
| Supports nosnippet for AI answers | N/A | N/A | Yes |
| Supports X-Robots-Tag header | Yes | Unknown | Yes |
The Googlebot fallback is notable. If your robots.txt doesn’t mention Applebot but does mention Googlebot, Apple follows the Googlebot rules. For sites that have invested in Google crawl optimization, Applebot is already reading your content. The question is whether your content is structured well enough for AI to trust it.
Applebot Crawling Is Already Significant
A Reddit user in r/webdev reported that Applebot was crawling their site three times more than Googlebot. Apple uses two distinct crawlers: Applebot (for Siri, Spotlight, and Safari search) and Applebot-Extended (for evaluating content suitability for AI model training). Both operate at scale.
Apple’s documentation notes that Applebot automatically adjusts crawl rate based on server response. It caches crawled content to reduce redundant requests. It renders pages within a browser context, meaning JavaScript-rendered content is visible if the resources aren’t blocked.
The practical implication: if your site’s core content requires JavaScript to render and your robots.txt blocks JS/CSS resources, Applebot sees a blank page. The same problem that hurts Google indexing hurts Apple indexing. But unlike Google, Apple is now feeding that content into a generative model that composes answers.
What Integration Looks Like for CKI Labs Clients
Siri AI doesn’t have a consumer API. You can’t send a probe query the way you can with ChatGPT, Claude, Gemini, Perplexity, or Grok. There’s no endpoint that returns how Siri answers a given question.
But you can prepare for it. The preparation looks identical to the clarity work that drives visibility across every other AI surface:
Structured data. Applebot respects schema.org markup, including isAccessibleForFree for paywalled content. Pages with proper structured data give Apple’s models the context they need to cite your brand in generated answers. Run a structured data audit before doing anything else.
Technical accessibility. Applebot renders JavaScript but needs access to CSS, JS, and XHR resources. If robots.txt blocks these, Applebot can’t render the page. Check your robots.txt against Applebot’s requirements.
Content extractability. H2 headers should function as standalone claims. Definitions should be direct and extractable in one sentence. Key facts should appear near the start of their section. This is the same structural extractability standard we apply to every evidence strength audit.
Robots.txt review. If you haven’t updated robots.txt since before June 2026, review it. Decide explicitly whether to allow Applebot-Extended for training and whether to use nosnippet for AI retrieval. The default (allow everything) means Apple can use your content for both training and real-time AI answers.
Monitor Applebot crawl activity. Check server logs for Applebot user-agent strings. Verify reverse DNS against *.applebot.apple.com or use Apple’s published CIDR ranges. If Applebot isn’t crawling your site, that’s the first problem to fix.
The Platform Fragmentation Problem
The Statcounter data tells the fragmentation story clearly. Over the past 12 months, ChatGPT dropped from 76.6% to 64.3% of US AI chatbot share. Google Gemini rose from 2.9% to 10.4%. Claude climbed from 1.7% to 7.6%.
Siri AI isn’t in that dataset. It lives in a different category, voice and device-native assistants, with a distribution channel that none of the chatbot platforms can match. Add Siri’s device surface to the chatbot share data, and the fragmentation curve steepens.
For B2B companies, this means six AI surfaces now compete for buyer attention: ChatGPT, Gemini, Claude, Perplexity, Grok, and Siri. Microsoft Copilot makes seven if you count its 12.6% share. No single platform controls enough of the audience to ignore the others. This is why AI visibility is not SEO. It’s a multi-surface infrastructure problem.
The companies that appear consistently across all surfaces share a common pattern: their websites are technically legible, structurally extractable, and semantically clear. That’s not an SEO tactic. It’s infrastructure.
What to Do This Week
- Check your robots.txt. Make sure Applebot isn’t blocked. Decide explicitly about Applebot-Extended.
- Audit structured data. Run schema.org validation on your key pages. Fix errors.
- Test JavaScript rendering. Disable JS in your browser and load your homepage and top product pages. If the content disappears, Applebot can’t see it either.
- Review nosnippet strategy. Decide page-by-page whether you want Siri using your content for AI answers. Most B2B companies should opt in. The citation value exceeds the risk.
- Monitor crawl logs. Look for Applebot activity. If it’s absent, your site has a technical access issue.
Apple opened a new AI surface with 2.5 billion devices behind it. The companies that get indexed first will have a head start that compounds. The ones that wait will wonder why Siri never mentions them.
