Skip to main content
Sign inStart free trial
Back to blog
AIe-commerceproduct discovery

From SEO to AI Product Discovery: Why Your Catalog Is Now Your Storefront

Sigourney8 min read

The last time a shopper typed ten blue links into their decision was longer ago than most store owners want to admit. In 2026 a growing share of purchase journeys never touch a search results page, never land on a homepage, and never see the hero banner a brand spent three weeks perfecting. Instead a person asks an assistant a question in plain language, and the assistant answers with a shortlist of specific products, pulled from data it could read, ranked by criteria the shopper never sees. If your catalog was legible to that assistant, you were in the answer. If it was not, you were invisible, and no amount of on-page keyword tuning changed that outcome.

This is the quiet but decisive shift underneath everything happening in retail right now. For two decades the discipline that decided who won online was search engine optimization, and its logic was human-centric. You wrote content for people, you earned links from people, you designed pages to persuade people, and Google's crawler tried to approximate what those people would find useful. The optimization target was a document, and the document was built to be read by eyes. That world is not gone, but it is no longer the only game, and for high-intent shopping queries it is increasingly not even the primary one.

The reason is the arrival of assistant-led discovery at genuine scale. OpenAI has reported that ChatGPT reaches roughly 800 million people each week, and that tens of millions of those interactions every day are shopping-related. Google has folded conversational answers directly into Search through AI Mode and into the Gemini app, and both now surface product recommendations inline. These are not experiments running in a corner of the product. They are the default surface a large population of buyers now reaches for first, and when they ask for the best running shoe under a hundred dollars or a gift for someone who loves ceramics, the assistant does not hand them a page of links to sift through. It hands them an answer, and that answer is a small number of concrete products.

Here is the part that reorganizes a merchant's priorities. An assistant cannot recommend what it cannot understand. When it assembles that shortlist it is not reading your beautifully designed product page the way a person would. It is consuming structured data about what you sell, what it costs, whether it is in stock, what it is made of, who it is for, and how it compares to alternatives. The homepage that a brand treats as its front door is close to irrelevant in this flow. The catalog, expressed as clean machine-readable data, is the storefront. The product that gets recommended is the product whose data was complete, accurate, and available at the moment the question was asked.

That inversion is uncomfortable because the catalog has traditionally been treated as back-office plumbing. Feeds were something the ads team maintained to keep shopping campaigns running, tolerated rather than loved, and rarely audited with the seriousness applied to the storefront itself. A missing material field or a stale stock status was an inconvenience, not a crisis, because a human shopper would forgive it or work around it. An assistant does not forgive it. If the field an agent needs to match a query is empty, the agent cannot infer it, and your product silently drops out of the consideration set. The shopper never learns you existed. There is no bounce rate to diagnose, no abandoned cart to recover, just an absence that leaves no trace in your analytics.

The strategic implication is that the center of gravity for winning shopping demand is moving from persuasion to legibility. Persuasion still matters once a person is comparing final options, but you do not get to persuade anyone if you were filtered out before the shortlist formed. Legibility is upstream of everything, and legibility is a data problem, not a design problem. The brands that internalize this early are quietly rebuilding their product data to be as rich and structured as possible, treating every attribute as a hook an assistant can grab onto, while their competitors keep polishing pages that a decreasing share of buyers will ever load.

It helps to be precise about what legibility means, because it is easy to nod along and then do nothing. It means your product titles describe the product clearly rather than stuffing keywords. It means your descriptions contain the specific facts an assistant needs, the exact material, the fit, the intended use, the dimensions, rather than atmospheric marketing copy. It means attributes that used to be optional, the pattern, the occasion, the compatibility, the care instructions, are now filled in, because when the entity is undefined the assistant cannot see it. It means the data your storefront shows and the data in your feed agree with each other, so an agent checking one against the other does not distrust you and move on.

There is a further layer that makes this more than a one-time cleanup. The infrastructure the industry is building around agentic commerce is standardizing how this data gets exposed. OpenAI and Stripe published the Agentic Commerce Protocol, an open standard for how agents and merchants exchange product and order information. Google introduced the Universal Commerce Protocol, co-developed with Shopify and endorsed across the retail ecosystem, to do something similar across its surfaces. Anthropic's Model Context Protocol provides the connective tissue that lets agents pull live data from external systems. The details differ, and the next articles in this series break them apart, but the common thread is unmistakable. All of them assume that a merchant can present a clean, current, structured view of its catalog on demand. A store that cannot do that is not merely behind on a marketing tactic. It is structurally excluded from the channel.

This is also why the old instinct to wait and see is more dangerous than it looks. In the keyword era a messy feed meant inefficient ad spend, a problem you could fix whenever you got around to it. In the assistant era a messy feed can mean you do not qualify to appear at all, and the cost is invisible, which makes it easy to ignore until a quarter of soft numbers forces the question. Worse, discovery advantages compound. When an assistant learns to trust the completeness of your data it surfaces you more, those recommendations generate signals, and the signals reinforce the surfacing. A brand that gets its catalog legible early does not just catch up. It accumulates a position that late movers have to fight to dislodge.

None of this requires abandoning what already works. Traditional search still drives volume, paid campaigns still convert, and a persuasive storefront still closes the sale once a shopper is looking. The point is narrower and more urgent. A new and fast-growing slice of demand is being decided one step earlier, in a place where only structured data speaks, and most stores have not yet moved their attention there. The homepage is not where that decision happens. The catalog is. The question every store owner should be asking is not whether their site looks good to a visitor, but whether their products are legible to the assistant that visitor is about to ask.

The practical starting point is unglamorous and entirely within reach. Look at your catalog the way an agent would, as a table of facts rather than a set of pages, and find the gaps. Every empty attribute is a query you cannot answer. Every inconsistency between your site and your feed is a reason to be distrusted. Every product with thin data is a product an assistant will pass over in favor of a competitor whose data was richer. Closing those gaps is not a rebrand or a redesign. It is the deliberate work of making what you already sell readable by the machines that increasingly decide what gets recommended. In a market where the catalog has become the storefront, that work is no longer optional maintenance. It is the storefront being open for business.

The organizational lesson underneath all of this is that product data needs an owner. In most stores the catalog is everyone's job and therefore no one's, maintained in fragments by whoever last touched a listing, which is exactly how gaps and inconsistencies accumulate. When the catalog was merely a set of pages for humans, that neglect was survivable. Now that the catalog is the surface assistants read to decide what to recommend, the absence of clear ownership shows up directly as lost visibility. The stores pulling ahead are assigning responsibility for catalog completeness and accuracy the way they long ago assigned responsibility for the storefront's look and the checkout's performance. It is not a glamorous mandate, but it is a decisive one. Someone has to own the answer to a simple question, asked product by product and attribute by attribute: if an assistant were deciding right now, would it be able to see and understand what we sell. Treat that question as a permanent operational discipline rather than a one-time project, and the catalog stays a storefront that is open rather than one that quietly closed.

From SEO to AI Product Discovery: Why Your Catalog Is Now Your Storefront | Sigourney