> ChatGPT never mentions your store? Four checks explain most cases - crawler access, llms.txt, product schema and feed. 15 questions answered, shortest first. Source: https://angeo.dev/magento-chatgpt-visibility-questions/ Updated: 2026-10-09 # Why Is My Magento Store Invisible in ChatGPT? 15 Questions Store Owners Actually Ask If ChatGPT, Gemini, or Perplexity never mention your store, the cause is almost always one of four things: AI crawlers are blocked, there is no machine-readable content map, your product schema is incomplete, or you have no product feed. This page answers the questions merchants ask most often, shortest answer first, and points to the detailed fix for each. Updated July 2026 *AI platform behaviour changes frequently - crawler names, feed specifications, and shopping surfaces may have evolved since publication.* ## Start here: the 60-second diagnosis Four checks explain the large majority of "my store is invisible" cases: 1. Does `robots.txt` allow search-time AI agents such as OAI-SearchBot, PerplexityBot, and Claude-SearchBot? 2. Is there a valid `llms.txt` at your domain root, served without a redirect? 3. Do product pages output JSON-LD `Product` schema with a populated `offers.availability`? 4. Do you have a product feed submitted to the AI shopping surface you care about? If any answer is "no" or "not sure", that is your starting point. Score all four automatically with the [free AEO self-assessment](https://angeo.dev/ai-magento-audit/). ## Why can't I find my store in ChatGPT? In most cases because ChatGPT was never able to read it. A default Magento 2 install commonly blocks AI crawlers in `robots.txt` and ships no machine-readable content map, so the store is absent from the sources the model draws on rather than ranked poorly within them. This is a access problem, not a ranking problem - which is why it can be fixed quickly once identified. ## My products aren't showing up in ChatGPT shopping results - why? Product results and general answers work differently. ChatGPT does not crawl your catalogue for shopping surfaces the way Google does; merchants push a structured product feed to OpenAI rather than waiting to be indexed. Without a submitted feed, products can still surface from crawled pages, but they miss the richer product treatment. See [preparing your Magento 2 store for ChatGPT Shopping](https://angeo.dev/magento-2-chatgpt-shopping-registration/). ## Why is my brand invisible when customers ask ChatGPT for recommendations? AI assistants typically name one or two stores instead of listing ten links, so being "somewhere in the results" is not enough - you either get selected or you do not appear at all. Selection depends on machine-readable signals most Magento stores have never configured. The underlying mechanics are explained in [why your store ranks in Google but disappears in ChatGPT](https://angeo.dev/magento-ranks-google-invisible-chatgpt/). ## I rank well on Google - why doesn't that carry over to AI search? Because AI systems evaluate an additional layer that Google rankings do not require. Fast pages, clean structure, and good rankings satisfy classic SEO while leaving the machine-readable layer - crawler access, content map, complete schema, feed - entirely unconfigured. Strong SEO helps, but it does not substitute for those signals. ## How do I know if ChatGPT can even see my store? Check whether AI crawler user-agents appear in your server logs, and validate that your `robots.txt` permits them. For a scored answer across all the signals at once, run `bin/magento angeo:aeo:audit` or the [2-minute self-assessment](https://angeo.dev/ai-magento-audit/). ## Common blockers ### Does robots.txt really block ChatGPT by default? Many Magento installations run a `robots.txt` written years ago for Googlebot that never gained rules for AI crawlers, and some actively disallow them. Blocking the search-time agents removes you from generated answers entirely. The fix is documented in [how to fix robots.txt for ChatGPT and Gemini in Magento 2](https://angeo.dev/magento-2-robots-txt-chatgpt-gemini-ai-bots/). ### Can I allow AI search but block AI training? Yes - training crawlers and search crawlers are separate user-agents, so you can allow the agents that make you citable while disallowing those that feed model training. Allowing search-time agents is what preserves your eligibility to be cited in AI answers. ### I added llms.txt but nothing changed - what went wrong? Three frequent causes: the file is served through a redirect rather than directly at the root, it lists pages that AI crawlers are still blocked from fetching, or it is the only signal you added while schema and feed remain incomplete. `llms.txt` is one signal among several, not a switch. ### Why does my product schema pass Google's test but still fail for AI? Google's rich-results validation tolerates gaps that AI shopping surfaces do not. The most common one is a missing or empty `offers.availability`, which causes products to be skipped. Default Magento also outputs microdata rather than the JSON-LD that AI engines prefer - see the [Product JSON-LD schema guide](https://angeo.dev/magento-2-product-schema-json-ld-ai-search/). ### Does schema added through Google Tag Manager work for AI crawlers? No. AI crawlers generally do not execute JavaScript, so structured data injected client-side through a tag manager is invisible to them. Schema must be rendered server-side in the page source. ### I'm on Hyvä - does that change anything? Partly. Hyvä emits Product microdata - name, image, price, availability - but no JSON-LD, and no sku, brand, GTIN, shipping or return-policy fields. Adding complete server-rendered JSON-LD closes the gap. See [what Hyvä emits as product schema](https://angeo.dev/hyva-theme-product-schema-gap/). ## Measuring and fixing ### How do I track whether AI engines send me traffic? Analytics under-reports it: many AI referrals arrive without an intact referrer and land in Direct. Server-side log analysis alongside analytics gives a fuller picture - the method is in [how to track AI search traffic in Magento 2](https://angeo.dev/track-ai-search-traffic-magento-2/). ### How long until I see results after fixing these signals? Crawler access and schema changes take effect as soon as the relevant agents re-crawl, which is typically days rather than months. Being cited in answers is not guaranteed by fixing the signals - it becomes possible, where before it was not. ### Who fixes this - my SEO agency or a developer? It is an engineering task more than a marketing one: the work happens in `robots.txt`, templates, schema output, and feed generation. Traditional SEO agencies often do not cover this layer. The evaluation criteria for choosing a partner are in [how to choose a Magento AI agency](https://angeo.dev/magento-ai-agency/). ### Can I fix this myself for free? Yes, for the core signals. Free MIT-licensed Composer modules cover llms.txt generation, schema output, crawler access, and auditing - the trade-off is your engineering time. The routes are compared in [AEO options for Magento](https://angeo.dev/aeo-options-for-magento/). ## Next step Run the [free AEO self-assessment](https://angeo.dev/ai-magento-audit/) to see which of the four signals your store is missing, then work through the [Magento 2 AEO guide](https://angeo.dev/magento-2-aeo-guide/). ## More on this topic - [Magento 2 Audit 2026: Technical, SEO, Performance, AEO](https://angeo.dev/magento-2-audit/) - [Why Your Store Is Invisible to ChatGPT - and Who Fixes It](https://angeo.dev/why-your-store-is-invisible-to-chatgpt-and-how-to-fix-it/) - [Magento AEO Checklist 2026](https://angeo.dev/magento-aeo-checklist/) - [AEO Score - Definition](https://angeo.dev/aeo-score-definition/) - [Magento SEO Audit 2026: 4-Layer Checklist with AI Search](https://angeo.dev/magento-2-audit/) - [AI Commerce Audit - Full AI Visibility Audit for Stores](https://angeo.dev/ai-commerce-audit/)