Shopify AI Referrals Grew 197%. Is Your Store Ready?

On 11 August 2026 Shopify published its Q2 commerce data. AI-referred sessions to Shopify storefronts grew 197% year over year — roughly 3× — and orders from them grew 3× as well.

Read the next sentence of that post before you act on the first one. Over the same period organic search sessions grew 12% on a much larger base, and organic still referred more sessions to Shopify merchants than all tracked AI platforms combined.

That split is the actual story. Shoppers are not leaving Google. They are adding a second door — a smaller one that is growing faster and arriving with the research already done. If that door cannot reach your products, or cannot tell two similar products apart, you miss the faster-growing half of it.

What the numbers say about shopper behaviour

Shopify’s reading is that people use the two surfaces for different jobs, and its category data supports that better than the headline growth figure does.

Picture the watch buyer asking an assistant which automatic under $400 has a sapphire crystal and a 40mm case. By the time they land, the comparison is finished — they are not browsing, they are verifying. The plain-t-shirt shopper still types a brand into Google, which is why organic remains the bigger pipe.

The three “2×” figures, and which one you can actually quote

This is where write-ups about that Shopify post go wrong, and it is worth slowing down for. The same page carries three separate conversion comparisons that all round to “about twice”. They have different baselines and they are not interchangeable.

If you quote only the spec-led 2× as though it described AI traffic generally, you are inflating a subset into a headline. The number that generalises is the first row: across all categories, AI-referred shoppers who reached a product page converted about 80% better than organic-referred shoppers. Still a large gap. Still worth acting on. Just not 2×.

The third row is the one merchants should care about most, because it is the only one that describes something you control. Both sides of that comparison are AI traffic. The difference is whether the assistant had clean structured product data to work from, or was piecing your catalogue together from scraped and third-party feeds. Same channel, same intent, twice the conversion — and the variable is your data quality.

That is a reported association, not a controlled experiment. Shopify did not randomise anything. The likely mechanism is unglamorous: structured fields give an assistant real attributes — size, material, compatibility, use case — so it sends shoppers who already fit.

Nobody types “blue sneakers” into a chat window. They type “waterproof trail shoe for a wide foot, under $150, good on rocky paths.” An assistant can only match that sentence to your SKU if those facts exist as data rather than as prose under a lifestyle photo.

The gap those numbers cannot show you

Shopify’s Q2 data describes merchants whose products AI could already find. It says nothing about whether your store is reachable — and that is the failure we see first on Shopify audits, ahead of missing product data.

The pattern is consistent: the theme is fast, Google is fine, the SEO app is green, and a “block AI bots” toggle or a CDN rule is stopping the search crawlers. Nothing in a rankings report will ever mention it, because nothing in a rankings report looks at those agents.

Blocking one bot is not blocking the vendor

Neither OpenAI nor Anthropic sends a single all-purpose robot, and this is where blanket rules do their damage. OpenAI documents its agents separately, and so does Anthropic.

Note which name does what at Anthropic, because it is easy to get backwards: ClaudeBot is the training crawler, collecting “web content that could potentially contribute to their training”. The one that matters for being found is Claude-SearchBot, which “navigates the web to improve search result quality for users”. A rule aimed at “ClaudeBot” to keep your content out of training does not touch search — and a rule that catches everything starting with “Claude” takes out both.

The two vendors also disagree about IP-level blocking, in opposite directions. OpenAI asks you to let its published IP addresses through your host or CDN in addition to robots.txt. Anthropic warns the opposite: blocking its IP addresses “may not work correctly or persistently guarantee an opt-out”, because it stops them reading your robots.txt in the first place. One vendor needs your firewall to cooperate; the other needs you not to use the firewall at all.

Our own logs show why treating these as one channel misleads: across four weeks we measured 15 named AI crawlers, and their weekly volumes swung 5.7× — driven by individual bots spiking, not by any site-wide trend.

Why an assistant would pick you over an equally readable product

Access and Catalog answer two questions: can AI reach the store, and can AI understand the SKU. Neither answers the third — why this product rather than another one it understands just as well.

Shopify’s own GEO guidance points off-site for that: assistants weigh reviews, press, community discussion and mentions you do not control. Technical accessibility gets a product into consideration; corroboration is what earns the recommendation. That is a different job from any authority score in an SEO tool — those barely predict AI citations, and in the research they can point the wrong way at the top of the scale.

Reviews on the product page, honest editorial coverage, and specs that agree across your store and your marketplace listings do more here than another keyword article. We do not replace PR or a review programme. We remove the technical blockers so those signals have a store an assistant can actually read.

What to fix, in order

You do not need a separate playbook per assistant. You need a sequence, and most stores are doing it backwards.

1. Confirm AI can reach the store. Check robots.txt and your CDN together — allow the search agents you want to support, keep refusing scrapers and, if you prefer, training-only crawlers. A locked door makes every hour of Catalog work invisible.
2. Make product facts machine-readable. Titles, specs, compatibility, shipping and reviews as text and structured labels, not trapped in images or accordions that never render for a crawler. This is what the Catalog-versus-feeds gap is pointing at.
3. Treat the product page as the first impression. Half of AI visits skip the homepage, so the SKU page has to confirm the research the shopper already did: who it is for, what is included, why it is trustworthy, how to buy.
4. Measure AI separately from Google. Group ChatGPT, Perplexity, Gemini and Claude in your analytics. Google’s AI summaries usually still count as organic, so whatever number you have for AI is probably an undercount.

An optional llms.txt file can point assistants at your key pages. It is a supporting signal, not a substitute for crawl access or product data.

These are not substitutes for one another:

GEO Fix works on that readiness layer. A free audit first, then Starter $39/mo or Pro $89/mo — we generate the robots instructions and structured data plus copy-paste steps for Shopify, rather than only scoring the gap. Larger catalogue work sits behind a consultation. We do not promise an assistant will pick your SKU; we remove the technical reasons it cannot.

What to do next

Key takeaways:

• Shopify reported AI-referred sessions to its storefronts up 197% year over year in Q2, while organic grew 12% and stayed the larger channel — both matter.
• Three different “about 2×” conversion figures sit on that page. The one that generalises is about 80% better, all categories, once the shopper reached a product page.
• The comparison you control is structured Catalog data versus scraped feeds — both AI traffic, 2× apart.
• Half of AI-referred sessions land straight on a product page, so that page carries the whole first impression.
• ClaudeBot is the training crawler; Claude-SearchBot is the one that affects being found. Blocking by prefix takes out both.