Tech
Apple agent readiness report
apple.com · re-scanned every Monday
Most agents will fail to read or trust this site.
#6 of 15 in the library
Scanned 2026-07-09
Score history
Apple sets the tone for how much of the tech industry thinks about product experience, and that reputation now extends to how well a site works for the AI agents shopping, researching, and comparing on a person's behalf. When an assistant is asked about a MacBook, an iPhone plan, or an AppleCare policy, whether it can read apple.com directly, or has to fall back on secondhand summaries from forums and review sites, shapes what gets said and how accurately.
The scan shows a site that is fundamentally open and well-built by conventional web standards: HTTPS with a forced redirect, a reachable sitemap, structured JSON-LD data on the homepage, solid meta tags, and a text-to-markup ratio that clears the readability threshold. Bots are not blocked. But none of the agent-specific files exist. There is no agents.md, no llms.txt, no llms-full.txt, and the homepage ignores requests for a markdown version of the page. There is also no MCP server card and no .well-known/verified.md, so nothing formally identifies the site to an agent or offers a machine-readable summary of what it does.
The gap is not that apple.com is hard to crawl. It is that nothing on the site was built with an agent as the reader. A human visitor gets a polished, fast, well-marked-up page. An agent gets the same HTML and has to work out the rest on its own.
What Apple gets right
- Clean HTTPS with forced HTTP-to-HTTPS redirect
- Reachable, well-formed sitemap.xml
- Structured data: three valid JSON-LD blocks on the homepage
- Full meta hygiene: title, description, and Open Graph tags present
- Content readability clears the text-to-markup threshold
- robots.txt does not block AI crawlers
What is missing
- No agents.md: assistants cannot read how apple.com wants to be used, so they default to guesswork
- No llms.txt or llms-full.txt: agents that want a clean summary or the full content in one file have to crawl page by page instead
- No content negotiation: requesting a markdown version of the homepage still returns raw HTML, which burns an agent's limited attention on navigation and scripts
- No MCP server card: agents can read the site but cannot interact with it as a service
- No .well-known/verified.md: nothing proves apple.com is who it says it is, so an agent has no way to rule out an impersonator
- No x402 payment signals: agents that are able to pay for content or services have no way to pay Apple directly
7 of 14 checks passing
Same category
Market context
Cloudflare measured AI crawlers fetching up to tens of thousands of pages for every visit they refer back (ClaudeBot about 38,000 to 1, July 2025 data). Assistants read constantly; they cite what they can parse. Source: Cloudflare, Aug 2025.
Your site can outscore Apple in 5 days.
95 or higher, guaranteed, or your money back.