For Magento
Can AI shopping assistants find your Magento store?
ChatGPT, Perplexity, Claude, and Gemini recommend products now. This page covers what they read on a Magento store, and the one setting that quietly makes about a third of them invisible.
Last updated 2026-06-01
Score your Magento store →Shoppers have started asking AI which product to buy. 41% of US shoppers now use AI assistants to research what they buy, according to the IBM and NRF study from January 2026. When ChatGPT or Perplexity answers one of those questions, it names specific stores. Plenty of those stores run on Magento or Adobe Commerce, and their owners are now finding out whether an assistant can actually read them.
Magento is self-hosted, which sets it apart. You, or your developer, control the robots.txt file and the server config directly, rather than having a platform vendor manage them for you. That control is much of the reason people choose Magento, and it cuts both ways. Magento 2 emits product structured data on your product pages by default, the machine-readable summary an assistant reads to understand a price and what an item is. But the same hands-on setup makes it easy to ship a robots.txt that turns the AI crawlers away without anyone noticing.
What AI actually sees on a Magento store
The Magento stores we scanned were not uniformly invisible to AI. Of the 12 we scanned in 2026, 8 carried product structured data an assistant could read, 7 of them in modern JSON-LD. The claim that these stores gave an assistant nothing to work with did not hold up.
The catch sits upstream of the markup. 4 of the 12 stores never got read at all, because their robots.txt tells the crawlers behind ChatGPT, Claude, and Perplexity to stay out. A perfect product schema behind that block is still invisible. Among the stores an assistant could read, content was the most common weak spot, thin on 6 of the 12 stores, and only 3 carried a brand an assistant can match against a catalog, with none carrying a GTIN.
Where Magento stores lose points
You may be blocking the AI crawlers
This is the one that catches Magento stores out. 4 of the 12 stores we scanned blocked at least one major AI crawler in their robots.txt, usually a line left over from an old SEO template. When the crawler behind ChatGPT or Claude reads that block, it leaves, and nothing else on the page gets a chance to matter. It is also the fastest thing on this list to fix.
Thin product descriptions
Content was the single most common weak spot. Of the 12 Magento stores we scanned, 6 were weakest on content, meaning the words on the page rather than the technology behind them. A two-line description tells a shopper little and tells an assistant less. If the material, the size, the use case, and what makes the product different are not written out in plain words, the AI has nothing to quote when someone asks for a recommendation in your category.
An incomplete offer and missing identifiers
Magento puts a Product in your structured data, but the details an assistant leans on are often missing. Across the stores we scanned, the offer was frequently incomplete, and only 3 carried a brand or a GTIN an assistant can match against a catalog. Without the complete price, currency, and availability, plus an identifier, an assistant cannot confirm the item is for sale and match it to a real product.
Hard-to-find policies
Shipping, returns, and refund terms are part of what an assistant checks before it puts your store in front of a shopper. When those pages are buried or folded into a wall of text, the AI cannot confirm you are a real, safe place to buy from. Some stores we scanned lost points here because the policy pages were hard for an assistant to find.
The robots.txt trap: blocking the AI crawlers without knowing it
In the Magento stores we scanned, the most common reason a store was invisible to AI was not the product markup. It was one file: robots.txt. Because Magento is self-hosted, that file is yours to edit, and a lot of stores inherited a restrictive version that names the AI crawlers and tells them to stay out. When the crawler behind ChatGPT or Claude reads a Disallow, it leaves, and the quality of everything else on the page stops mattering.
# robots.txt
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /The crawlers behind ChatGPT and Claude are told to stay out. Your products are invisible to them, however good the markup is.
# robots.txt
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
Sitemap: https://example.com/sitemap.xmlThe AI crawlers can read your catalog, and your sitemap points them at every product.
Of the 12 Magento stores we scanned, 4 blocked at least one major AI crawler this way. We checked each against the crawlers the big assistants name: GPTBot, ClaudeBot, PerplexityBot, anthropic-ai, and Google-Extended. Every blocked store had a real catalog an assistant would otherwise have read. The fix costs nothing and ships in minutes: remove the Disallow for the AI crawlers, or replace it with Allow.
Illustrative robots.txt based on the patterns we measured across real Magento stores. Run the free check to see your own.
How to close the gap
Unblock the AI crawlers in your robots.txt
Open your robots.txt and look for Disallow lines under GPTBot, ClaudeBot, PerplexityBot, anthropic-ai, or Google-Extended. If they are there, remove them or switch them to Allow. This was the single biggest thing holding the stores we scanned back, and it is the fastest to fix.
Put the key facts in the description
Write the material, the size, the use case, and what makes the product different into the visible description, in plain sentences a customer would read. This was the most common weak spot after the crawler block, and it is the one no app can write for you.
Complete the offer and add an identifier
Make sure every product emits a complete offer in its structured data, the price, the currency, and an availability signal together, and add a brand and a code like a GTIN or MPN. Confirm your theme or a structured-data extension actually outputs all of it.
Make policies and identity easy to read
Link your shipping, returns, and refund pages clearly, and make sure your homepage states who you are and how to reach you in a way a machine can read. They are what an assistant checks before it recommends a store.
What we found across real Magento stores
of the 12 Magento stores we scanned block ChatGPT, Claude, or Perplexity in their robots.txt. Those stores are invisible to the assistants behind those crawlers until the block is removed.
Magento stores we scanned, 2026
of the 12 stores carried product structured data an assistant can read. In the sample, the product markup was not the blocker.
Magento stores we scanned, 2026
median AI-visibility score out of 100 among the stores an assistant could actually reach. The blockers, not the markup, drag the rest down.
Magento stores we scanned, 2026
One anonymized store from that scan. Strong markup, trusted policies, and a clear brand, and still capped at 55 because its robots.txt blocks the AI crawlers:
Questions
Does Magento block AI crawlers by default?
- Not by default. A standard Magento robots.txt does not block the AI crawlers. The problem is that Magento is self-hosted, so many stores ship a customized robots.txt, often copied from an older SEO template, that does block them. 4 of the 12 stores we scanned blocked at least one major AI crawler. It is worth opening your own robots.txt to check.
Does ChatGPT recommend Magento or Adobe Commerce stores?
- It can, as long as it can read them. Magento 2 emits product structured data by default, so a reachable store with real descriptions, clear policies, and a complete offer competes fine. The platform is not the blocker. A robots.txt that turns the crawlers away, or thin pages, is.
Is this AEO or GEO for Magento?
- Same idea, plain words. AEO (answer engine optimization) and GEO (generative engine optimization) both mean making your store readable and recommendable by AI assistants. This page covers that for Magento stores.
How do I check if my robots.txt blocks AI crawlers?
- Open yoursite.com/robots.txt in a browser and look for Disallow lines under User-agent: GPTBot, ClaudeBot, PerplexityBot, anthropic-ai, or Google-Extended. If you see them, those assistants cannot read your store. Or run the free check and we will flag it for you.
See where your Magento store stands.
Free. ~30 seconds. Nothing changes on your store.
Score your Magento store →See exactly how we score, on the methodology page, or compare AI visibility across platforms.