GEO / AI search
Why 60% of your product catalog is invisible to AI search engines (and how to fix it)

Henri de Bouteiller
CEO & co-founder
5
read
Mar 19, 2026

Why 60% of your product catalog Is Invisible to AI search engines (and how to fix it)
Most brands assume their AI search problem is a visibility problem. It isn't. It's a content problem, and it's completely invisible in your analytics dashboard.
Here's what the data shows: most enterprise product catalogs extract just 5–7 product attributes per SKU. AI search engines, ChatGPT, Perplexity, Google AI Overviews. They need 15 to 20 to confidently recommend a product. The gap between those two numbers is where your catalog disappears.
This isn't a niche technical problem. As AI assistants become the default way shoppers discover products, especially on mobile, especially in fashion, home, and lifestyle categories. The brands with content-complete catalogs will compound their advantage. The rest will watch their organic discovery quietly erode.
This article explains why it happens, what specifically is broken, and what you can do about it, starting this week.
What does 'invisible to AI' actually mean?
Traditional search engines crawl your pages, count keywords, and rank based on signals you've spent years optimising. AI assistants work differently. They don't rank pages, they synthesise answers. And to synthesise an answer that includes your product, they need to understand it, not just find it.
Think of an AI assistant as a very well-read personal shopper. When a customer types "what's a good midi dress for a summer wedding, size 14, under £150" into ChatGPT, the model draws on every product description it has access to. It compares fit notes, occasion suitability, material breathability, and style compatibility, then names a product. If your description says "Beautiful midi dress in blue, available in multiple sizes," you're not in that conversation. If it says "Midi-length crepe dress in cobalt blue, tailored fit, suitable for weddings and garden parties, sizes 8–20, dry clean only", you are.
The channels at risk are growing fast: ChatGPT Shopping, Perplexity product search, Google AI Overviews, Bing Copilot, and voice assistants. These are not future problems. They are current traffic that your analytics almost certainly isn't attributing correctly.
What traditional search needs | What AI assistants need |
Keyword in title and meta | Semantic, factual description of the product |
Page indexed by Googlebot | Rich attribute data (material, occasion, fit, care) |
Internal links and anchor text | Structured data (Schema.org Product markup) |
Page speed and Core Web Vitals | Consistent terminology across the catalog |
Backlinks from authority domains | Native-language content per market |
Why most retail catalogs fail AI engines
The problem isn't your products. It's your content, and specifically, it breaks down in four distinct ways.
1. The attribute gap
Most enterprise catalogs publish the basics: name, price, SKU, category, one or two photos. AI engines need far more. For a fashion product, that means material composition, cut and fit, occasion suitability, size guide, style compatibility, sustainability credentials, care instructions, and social proof signals. For a homeware product: dimensions, compatible fixtures, installation requirements, material finish, weight. For food and beverage: ingredients, allergens, dietary flags, serving suggestions.
When we analyse retail catalogs at Newtone, we consistently find that brands are publishing 5–7 attributes per SKU when AI-driven discovery requires 15–20. That gap means 60–80% of their inventory is functionally invisible to AI assistants: not because it isn't indexed, but because there isn't enough information for an AI to confidently recommend it.
2. The description gap
Short, promotional copy was written for a human skimming a product page. It wasn't written for an AI reading thousands of descriptions to synthesise a recommendation.
Compare these two descriptions for the same product:
Beautiful silk blouse in ivory. Perfect for any occasion. Available in S, M, L.
Versus:
Ivory blouse in 100% washed silk with a relaxed oversized fit, point collar, and mother-of-pearl buttons. Suitable for business casual, evening, and smart-casual occasions. Falls to the hip; size up for a more relaxed drape. Dry clean only. Pairs well with tailored trousers or wide-leg denim.
The first description is invisible to AI. The second gets recommended. The difference is specificity and semantic richness, and it's replicable at scale.
3. The language gap
Here's one that almost no brand has fully addressed: AI assistants in each market use local-language content. A French customer asking Perplexity for a summer dress recommendation will be served by French-language sources. If your product descriptions exist only in English, or if your French translations are machine-literal rather than culturally adapted, you're invisible in that conversation.
This applies to every market you operate in. The brands winning at AI search in Germany have German-native content. The brands winning in Japan have Japanese-native content: not translated English. Most enterprise retailers have a multilingual strategy that stops at translation and never reaches localisation. That gap compounds directly into lost AI discovery.
4. The structure gap
AI systems don't just read prose, they parse structure. Content buried in PDFs, images, or JavaScript-rendered components often can't be processed at all. Inconsistent field names across a catalog ("colour" in one category, "hue" in another, "shade" in a third) confuse semantic parsing. Missing Schema.org markup means the product's key attributes, price, availability, rating, never reach AI comprehension in machine-readable form.
This is the most fixable of the four gaps, but it requires a systematic approach rather than a product-by-product fix.
Five things you can do right now
You don't need to fix 50,000 products overnight. You need a systematic approach that starts with the highest-value SKUs and scales from there.
Audit your attribute coverage. Run a quick count: how many data fields does your average product have populated? If you're below 10–12, you have a material gap. Most brands are surprised to find the number is closer to 6. Start with your top 20% by revenue: the products that drive 80% of your commercial results, and apply a richer attribute standard there first.
Rewrite descriptions for semantic richness. Move from promotional to informational. AI assistants cite the most complete, factual sources: not the most enthusiastic ones. This doesn't mean removing the brand voice; it means ensuring that the factual content is there alongside it. Occasion, material, fit, styling notes: these are the signals that tip a recommendation your way.
Implement Schema.org Product markup. Structured data is the bridge between your content and AI comprehension. At minimum, implement Product, Offer, and AggregateRating schemas. Add BreadcrumbList and FAQPage where relevant. If your platform is Shopify or a major CMS, plugins make this straightforward. On a custom stack, it's a development sprint, but one that pays back immediately in both traditional SEO and AI citation rates.
Localise, don't just translate. For every market you operate in, you need native-quality content: not a word-for-word translation of your English copy. This means culturally adapted product descriptions with market-specific terminology, local sizing conventions, and region-relevant styling references. A 'smart-casual' occasion note lands differently in France than in the US. AI assistants know this. Your content needs to reflect it.
Fix your structure and consistency. Standardise field names across your catalog. Make sure all content is crawlable: not locked in PDFs or JavaScript renders. Eliminate the terminological inconsistencies that prevent AI systems from building a coherent picture of your product range. This is infrastructure work, but it's the foundation that all other improvements sit on.
What this looks like in practice
A luxury fashion group operating across eight markets found that fewer than 30% of their product descriptions contained enough attribute data to be recommended by AI assistants. Their English content was strong; their multilingual content was thin; their structured data was almost entirely absent.
Over six weeks, working through Newtone's platform, they enriched 12,000 SKUs with richer attributes, rewrote core descriptions for semantic depth, and deployed Schema.org markup across their catalog. Within 60 days, they saw a measurable increase in AI-assisted product discovery and a 34% uplift in organic sessions driven by AI-referred traffic, traffic that previously had no attribution path in their analytics at all.
The work wasn't a redesign. It was a content infrastructure upgrade, the kind that compounds quietly and becomes a durable competitive advantage as AI search grows.
The window is open, but it won't stay open
The brands winning at AI search right now are not doing anything technically extraordinary. They have complete product data, semantically rich descriptions, structured markup, and native-language content in every market they operate. That's it.
The reason this matters urgently is compounding: AI systems learn to cite sources they've found useful. Once a competitor becomes the default recommendation for a product category in your market, displacing them requires not just matching their content quality but exceeding it, for long enough that the model updates its preferences.
The fix is available to every retail brand. It requires content infrastructure, not a technology overhaul. The question is whether you build it before your competitors do, or after.
See how AI infrastructure is
a growth engine
Get a Demo

