Everyone's telling you to add llms.txt for AI search. The 2026 data says it gets 0.1% of crawler tra

Question

I'll save you the suspense: yes, you should still ship llms.txt on your Magento store. But not for the reason every "AEO guide" is selling you — and if you're shipping it instead of fixing the things that actually get you cited in ChatGPT, you've optimized the wrong file.

This is the contrarian version of the AEO conversation, with the numbers attached. I've been measuring this across real Magento 2 stores, and the gap between the marketing and the server logs is wide.

The claim being sold

The pitch goes: AI is the new search, llms.txt is the new robots.txt, add one and ChatGPT/Claude/Perplexity will start recommending you. Vendors are charging for modules that generate it. Plugins are auto-shipping it.

What the logs actually show

The independent 2026 data is blunt:

• A 300,000-domain study found roughly a 10% adoption rate for llms.txt. Among the 50 most AI-cited domains, exactly one had the file.
• One vendor instrumented a domain for 90 days: 62,100 AI bot visits, 84 of them hit llms.txt. That's 0.1%. They removed it from their GEO audit checklist afterward.
• Another monitoring 500M+ AI bot events found the same pattern — GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, and Google-Extended overwhelmingly skip the file and crawl your HTML directly.
• OpenAI, Anthropic, and Perplexity have not committed to reading it automatically. Google's John Mueller has said major crawlers don't prioritize it over standard HTML.

If your goal is "get cited more in AI answers," llms.txt is not the lever. Full stop.

So why ship it anyway?

Because it's a Business-to-Agent (B2A) play, not an SEO play — and on that framing it's worth the half-day:

1. Agentic and IDE-style tooling already fetches it. The agent ecosystem is where this pattern is mature, and agentic commerce is heading the same way.
2. Cheap insurance. Conventions like this routinely get published before platforms formally commit — robots.txt itself predated official search-engine support. Being already-correct when adoption crosses the threshold costs almost nothing now.
3. The exercise is clarifying. Writing one authoritative paragraph about your store forces the question "what would I want a model to say about us?" — which most catalogs have never answered.

Ship it. Then stop touching it. A stale llms.txt is worse than none — wrong stock or dead policy links train models to distrust your feed.

Where the citations actually come from

Here's the part the llms.txt hype distracts from. On Magento specifically, two things move the needle far more, and both ship off by default:

1. robots.txt — you're probably blocking the AI fleet by accident. A robots.txt written for Google in 2019 says nothing about ~10 distinct AI bots, and hardening configs that block "unknown" bots now block the crawlers feeding ChatGPT and Claude. Note: Google-Extended is not Googlebot — many sites blocked it in the 2023–24 anti-scraper panic and killed their Google-AI visibility without touching their ranking.

User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: Google-Extended
Allow: /

2. JSON-LD with a live offers.availability. Default Magento 2 emits microdata, not JSON-LD — the format AI extraction is worst at. And the killer omission: offers.availability is frequently missing, and ChatGPT Shopping skips a product with no availability signal entirely. It's assembling a purchasable recommendation; an item it can't confirm is in stock is a liability, so it drops you silently.

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Cast Iron Skillet 12\"",
  "sku": "CAST-SKILLET-12",
  "offers": {
    "@type": "Offer",
    "price": "59.00",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Two Magento traps that waste people's time:

• Schema injected via GTM is invisible — AI crawlers generally don't run JavaScript, so it validates in DevTools and is unreadable to the bot. Server-render it.
• Hyvä ships zero product schema by default. Migrated for performance? You may have silently dropped your structured data.

Confirm it's in the raw HTML, not just the rendered DOM:

curl -s https://yourstore.com/your-product | grep -A20 'application/ld+json'

Empty output = the AI layer sees nothing, no matter how green your audit looks.

And the part that's actually about revenue: ACP vs UCP

While everyone argues about llms.txt, the real 2026 shift is AI moving from discovery to transaction. Two protocols:

• ACP (OpenAI + Stripe) — live in ChatGPT since late 2025, now a discovery-and-feed role with delegated payment tokens and a transaction fee on Instant Checkout orders.
• UCP (Google + Shopify + 20-plus partners) — NRF Jan 2026, expanded May 2026; protocol-agnostic, spans discovery → checkout → post-purchase across Google AI Mode, Gemini, YouTube, Gmail.

The take that matters: it's not "pick one." They hit different agent ecosystems and dual-protocol merchants reportedly see meaningfully more agentic traffic. Most groundwork — clean schema, accurate live feed, defined policies — is shared and survives spec churn. Shopify gets this by partnership default; Magento merchants own the stack and configure it themselves.

The actual priority order

1. Fix robots.txt. (~20 min, highest leverage)
2. Server-rendered JSON-LD with live offers.availability.
3. curl verify — not in raw HTML = invisible.
4. Then ship llms.txt as B2A insurance, and leave it.
5. Build the shared feed/policy substrate, attach ACP then UCP.

The headline stands: llms.txt is the most over-marketed item in AEO right now. Ship it cheaply, ignore the hype, and spend your real hours on the bots-can-crawl-you and schema-is-server-rendered problems. That's where the citations live.

---

Measured across Magento 2 stores at angeo.dev; open-source AEO audit CLI + llms.txt generator on Packagist. The adoption/crawler figures are from independent 2026 studies — verify current spec versions as you go, this moves monthly.

Have you pulled your own AI-bot logs on a Magento store? I'd love to see whether your llms.txt hit-rate matches the 0.1% — post your numbers below.