The Answer Layer Names the Need

Google’s AI now states what a buyer wants down to the model number, and on the four queries below, the commerce layer could not sell a single one of them.

Three cameras, named, purchasable nowhere

Search “best camera for low light video.” The AI Overview names the Sony FX3, the Sony Alpha a7S III, and the Canon EOS R6 Mark II, and it explains the reason: large full-frame sensors and dual native ISO.

That is a shortlist with the reasoning attached, the answer a specialist retailer used to give in the shop.

None of the three were purchasable in a Google commercial module on the page.

The same shape, four times

“Office chair for lower back pain.” The AI names the X-Chair X4 Leather Executive, the Herman Miller Sayl, and the Branch Verve Chair. None of the three appear in the six paid slots.

Look at what those paid slots do carry. Titles reading Active Lumbar. Ergonomic. Massage. Not one says “back pain.”

The buyer typed the symptom because that is what they feel. You wrote the clinical term because that is what the chair is. Both descriptions are accurate. The right product. They share no words yet, and that page is open to whoever writes the sentence first.

“Headphones that do not hurt ears.” The AI names the Shokz OpenRun Pro 2, Bose QuietComfort, and the Sony WH-1000XM6. None appeared in a Google commercial module.

“What do I wear to an outdoor wedding.” The AI names wedge sandals or block heels specifically so the buyer does not sink into grass or sand. A wrap or jacket for cooler weather. Linen or cotton suits with loafers for men. Google’s own “Find related products & services” module returned six slots. All six of them were dress queries.

Four parts of the need, named on the page. Dresses offered against all four.

Buyers search in one language. Products are listed in another. What changed is that the buyer’s language is now printed at the top of the page, in public, by Google, before a single product loads.

This does not happen everywhere. Search “best generator to run a whole house” and the AI’s named product is purchasable, because every generator publishes its wattage and shopping carries a power output facet in kilowatts. Where an industry standardized a number, retrieval has an axis to match on.

The query where the AI explains the absence

Search “lipstick with spf.” Google’s AI Overview states:

“Traditional full-coverage wax lipsticks rarely contain SPF, so most lip sunscreens come as tinted balms, glosses, or treatments.”

Read that as a merchant, not as a shopper. The answer layer did not report a retrieval miss. It reported an absence in the market, and an independent count of the attribute layer points the same way.

The demand behind that query is documented and long-running. People Also Ask on the same page carries the question “Do any lipsticks have SPF?” An r/AsianBeauty thread titled “Anyone else wishing for SPF Lipsticks?” is nine years old.

An independent count of a large corpus of product listings points the same way. Across 7,250 lipstick products from 1,314 brands, the recorded modifiers are matte with 2,261 products, long with 211, and waterproof with 207. No SPF segment is present in the attribute layer at all.

Two sources with no shared method pointing the same way. One is a sentence written by Google’s AI. The other is a count of what is listed.

Now the part that matters, and it is one documented case rather than a general law. When a product is absent from the attribute layer, an answer layer that explains the absence is teaching every future buyer that it does not exist. The nine-year-old thread asks whether the thing is out there. The AI now answers that question, at scale, for everyone who asks it, in a single confident sentence. Demand that used to sit in a forum waiting for a merchant to notice it is now named in public at the top of the results page, and nobody has answered it yet.

One case. It is enough to show the mechanism.

Why this is timely rather than interesting

On several situation queries in this study, products were observed appearing inside the AI Overview itself, rather than in a separate shopping module below it.

That was observed on the page. It was not announced, and nothing here should be read as a stable property of Google. The answer layer is beginning to carry commerce directly, which means the sentence that names the buyer’s need and the slot that sells against it are converging into one surface.

Every number in this article has a short shelf life. The behavior underneath it does not.

One merchant already worked this out

On “running shoes for flat feet,” Orthofeet holds three of the six paid slots, and a fourth belongs to KURU Footwear on the same mechanism. The Orthofeet titles read “Best Running Shoes For Flat Feet.”

They are not a major running brand. They won that page on language, by writing the words the buyer typed into the place the buyer’s words get matched.

And on that exact same page, the AI Overview recommends the ASICS Gel-Kayano, the Brooks Adrenaline GTS, and the HOKA Arahi. None of the three are in the paid slots.

Both things are true at once, which is the whole finding in one screenshot. A merchant who supplies the buyer’s vocabulary can own the commercial surface of a need query. The named products can still be unbuyable on the same page. Winning the page and being the AI’s recommendation are two separate races.

What this means for your catalog

The answer layer is now describing your buyer’s need in your buyer’s words, in public, at scale. It names the models. It names the wedge heel and the reason for the wedge heel.

You did not miss a memo. This surface did not exist in its current form two years ago, and nothing asked your catalog to be ready for it.

None of that requires you to guess what buyers want. It is written down. The question is whether your catalog can be matched to it, and your catalog speaks the language of what the product is: brand, model, material, mechanism. That is not a flaw. It is simply not the language the answer layer is using.

The gap between the two is where the new sales are made, and it is now measurable, because one side of it is published every time somebody searches.

You no longer have to guess the language. It is printed at the top of the page. Run it against your catalog in the graph and the intersection comes back named: the answer layer’s words for a need on one side, the products you already stock on the other.

Methodology

Every search result described here was captured from live Google search results on 2026-08-04, query by query. No SERP vendor was used. All captures used one browser profile on a United States connection, signed in to a personal Google account, so results carry whatever personalization that account attracts. A shopping browser extension was active and injected product panels into several pages; those injected modules are not Google results and were excluded from every count here.

The queries described here come from two hand-captured sets, both run on that date: a 20-query pilot covering product-plus-qualifier, situation, and performance queries, and a 30-query extension covering situation queries only.

A named product counts as unsold only if it appeared in no sponsored listing, no shopping grid, and no related-products module on the page. Editorial results, videos, and forum threads are not commercial modules.

The lipstick figures are a separate exercise: a count of product listings in a large corpus, taken independently of the search results, from a static build stamped 2026-07-16. The claim supported by that count is that no SPF segment is present in the attribute layer across those 7,250 lipstick products. It is not a claim that no SPF lipstick exists anywhere.

AI Overview behavior changes quickly. Everything here describes one day of results and should be read as a dated observation rather than a fixed property of search. The placement of products inside AI Overviews in particular should be re-measured rather than assumed.