For most brands, the Google Shopping grid has been somebody else's dashboard. The performance-marketing team owns the feed, the agency watches the disapprovals, and the brand team looks at organic rankings and social. The two conversations rarely meet in the same room.
The shelf stopped being a retail-only concern
For most brands, the Google Shopping grid has been somebody else's dashboard. The performance-marketing team owns the feed, the agency watches the disapprovals, and the brand team looks at organic rankings and social. The two conversations rarely meet in the same room.
That split made sense while the grid was only a paid shelf sitting above ten blue links. It stopped making sense once assistants started answering questions like "which sunscreen for oily skin", "best hatchback under a certain budget", or "what should I buy to replace this". Those are shopping questions, and the model answering them needs something more precise than prose.
We track this inside Ansyra as its own tab under AI Answers, called Shopping Visibility, with a single-line purpose: whether your products appear in the Google Shopping grid. It sits next to public reviews but is deliberately kept separate from them, because commerce presence is not reputation. Being on the shelf and being well spoken of are different facts, and a brand can have one without the other.
Why does a product answer lean on retail data?
Because a recommendation has to resolve to a thing you can buy. A general answer can hedge. A product answer cannot: it has to name a specific variant, at a price, from a seller, in a country. Free-flowing marketing text does not carry any of that reliably, and a model that guesses at a price is a model that gets corrected in public.
Retail structured data carries exactly the fields the answer needs, in a form nobody has to interpret. A product identifier resolves one variant rather than a family. An availability field says whether the thing can be bought today. A price field is a number rather than a claim. When a system has both a paragraph and a structured record available, it will lean on the record, because the record is the part it can act on.
There is a second reason, and it is the one brands underestimate. The shelf is also a destination. As assistants add buying and hand-off behaviour, the surface they push a shopper toward is a commerce surface. Being absent from it does not read as neutral. It reads as a shelf where other sellers are present and you are not.
A feed and a product page are different evidence
This is the distinction most teams collapse, and collapsing it is why the two drift apart for months without anyone noticing.
A product feed is an assertion you submit. It is per variant, it carries identifiers, price, availability, shipping and condition, and it is validated by the platform before it populates anything. It is private until it is accepted, and it fails silently: an item can be disapproved, or drop out on a stale availability value, without anything visible changing on your website.
A product page is a public artifact a crawler fetches. It carries markup that should agree with the feed, it can be quoted, and it can be cited with a link. It is the thing an answer engine can point at when it explains itself.
They prove different things, and they fail in opposite directions:
A feed can be fully approved while the product page has no structured markup at all, so the item sits in the grid but has nothing citable behind it.
A page can be immaculate, marked up correctly and ranking well, while the feed carries an old price or an out-of-stock flag, so the product simply is not on the shelf.
A feed proves the item is purchasable. A page proves the item is describable. A product recommendation usually wants both: the record to know what it is, and the page to cite.
The two are owned by different teams in most brands, which is precisely why they diverge and why nobody is accountable for the gap.
What Ansyra measures here, and what it does not
We would rather describe this capability narrowly and accurately than let it sound bigger than it is.
What the check does: for a brand, we read the Google Shopping grid for up to six of your tracked queries, using the market you set on the brand, through the platform's search-data connection. For each query we take the products at the top of the grid and record position, title, seller and price.
How we decide you are listed: a query counts as listed when a product in the grid links to your own domain (or a subdomain of it), or when the product title or the seller name contains your brand name or one of your registered aliases, matched on word boundaries. The first match becomes your rank for that query.
What you get back: listed or not listed per query, your position in the grid where you appear, the seller sitting at the top of that query's grid, and the sellers appearing across your checked queries ranked by how often they show up. Reads are cached for a day, returning to a cached result costs nothing, and a live re-check is restricted to an owner or admin because each query is a metered call.
What it is not:
It is a name and domain match, not proof of merchant-account ownership. A reseller or marketplace listing carrying your brand counts as listed. That is often the honest state of the shelf, but it is not the same as your own listing, and the top-seller column tells you who is winning the grid, not who is selling your item.
It is a sample, not an audit. Six queries, one market, the top of the grid, at one moment. It will not tell you what proportion of your catalogue is live.
It reads the grid, not your feed. We cannot see disapprovals, missing identifiers, or the reason an item is absent. Those live in your merchant account.
It does not grade Product or Offer markup on your pages today. Our readiness audit covers Organization and WebSite structured data and sameAs links, which is entity evidence, not product evidence.
Until the search-data connection is configured, the tab says so plainly. It does not show you a zero, because an unconfigured check and a genuine absence are different states and should never look alike.
What does absence from the grid actually tell you?
It tells you that you are absent. It does not tell you why, and the difference matters because the four common causes need four different teams.
Work through them in this order. The item may never have been submitted, which is a catalogue-coverage question. It may be submitted and disapproved, which is a feed-quality question. It may be approved but ineligible in that market or at that moment, which is an availability and shipping question. Or it may be present under a seller you do not control, which is a distribution question and often the most interesting of the four.
That last case is the one worth pausing on. If the grid for your own category query is owned by an aggregator and three marketplace sellers, and your brand appears only inside their listings, then every machine reading that shelf learns your product exists and learns that somebody else sells it. Your pricing, your imagery and your claims are then whatever those sellers uploaded.
What a brand should check first
A practical order of work, biased toward the checks that are cheap and reveal the most.
None of this requires our product. It requires somebody to sit with the feed and the page side by side, which is the part that rarely happens.
Run your own category queries, not just your brand name. Brand-name queries almost always show you something. Category queries are where an assistant's shopping question actually starts.
Read the seller column before the rank column. Who is on the shelf tells you more about your distribution than your position does.
Diff the feed against the page for a handful of hero products: title, price, availability, currency, image. Any mismatch is a signal one of the two is stale.
Confirm every variant carries stable identifiers. One shade, one size, one pack count, one trim level should each resolve to a distinct record. Beauty and FMCG lose the most here, because shade and pack size are exactly the axes a shopper asks about.
Add Product markup with price and availability to the page, and make it agree with the feed. Disagreement is worse than absence, because it makes both sources less trustworthy.
Check that ratings and reviews exist somewhere the surface can read them, on the retailer listing as well as your own site.
For auto, treat this as two feeds. Parts and accessories behave like ordinary retail. Vehicle inventory is a variant plus a dealer plus a location, and a recommendation that cannot resolve the dealer is not a recommendation.
Who owns this inside the brand
Almost every failure we see here is an ownership failure rather than a technical one. The feed sits with performance marketing or e-commerce operations. The product page sits with brand, web or SEO. Answer Engine Optimization work usually sits with a third group again, if it sits anywhere.
Three owners, no shared view, and the failure mode is quiet: nothing breaks visibly, an item just stops appearing, and the first person to notice is a shopper who does not tell you.
The fix is not a reorganisation. It is one recurring review where someone reads the shelf and the page together, and treats a mismatch as a defect with a name against it. Shopping visibility earns a place in the same conversation as AI answer visibility because it is the same conversation: what evidence about your products exists in a form a machine can use, and who is responsible when that evidence goes stale.