twimco.Let’s talk ↗︎
Menu
Field notes / Commerce

Google is showing shoppers how to ask Gemini about your product page. Answer its three questions on the page itself

Picture a shopper on your product page with Gemini open beside it, asking what the thing weighs. Google's own how-to shows exactly that scene, two weeks before Black Friday. You won't see the question in your analytics, so the answer had better be on the page.

Editorial engraving of a sunlit outdoor-gear studio where a merchandiser weighs a sleeping bag and reads its tag while a colleague types up the product details on a laptop.

Gemini in Chrome can read the product page a shopper has open and answer questions about it in a side panel, and Google's November 12, 2026 guide illustrates exactly that on a retailer's page. You can't see those questions or answers in your analytics. The practical response is to put the facts shoppers ask about, like weight, materials, sizing and what reviews say, in plain visible text on the page, and to check that it reads correctly.

The picture in Google's how-to

On November 12, Google posted a short guide called "Get quick answers from Gemini on any website." It has two steps. Click the Gemini icon in Chrome's toolbar to open the side panel. Then ask Gemini to "summarize a dense report, compare product details, or explain complicated topics in plain language," all while keeping your spot on the page.

The words are general. The illustration isn't. According to PPC Land's write-up the same day, the only image shows a shop's product page for a down sleeping bag, with an add-to-cart button on the left and the Gemini panel on the right. The panel suggests three questions: list the key features of this bag, the sleeping bag's weight details, and what the fill material is. The request typed in the box asks Gemini to summarize the reviews.

None of this is a new feature. Gemini arrived in Chrome for U.S. desktop users in September 2025 and has spread to more countries since. What's new is Google showing shoppers how to use it on a product page, fifteen days before Black Friday on November 27.

So picture the moment. A shopper is on your page, ready to buy or nearly. Instead of scrolling, they ask the panel what it weighs, what it's made of, and what other buyers complained about. You never see the question. You only find out how it went from whether they bought.

Decision guide

What you can see, and what you can't

ConsiderationVisible to youNot visible to you
The visitA session on the product page, as usualThat the shopper opened Gemini beside it
The questionNothing, unless they also use your site search"What's the fill material?"
The answerNothingGemini's summary in its own words
Your pageEvery word and image you publishedWhich parts the panel relied on
Decision framework based on Google's November 12, 2026 guide and PPC Land's report; illustrative, not measured.

What the panel reads, and what you'll never see

By default, Gemini in Chrome uses the current tab to answer, and on a computer a shopper can share up to ten open tabs, so "compare product details" can mean your page against two competitors' pages at once. That's from Google's help pages as summarized by PPC Land.

Your analytics will record a session on the product page, as usual. They won't record that the shopper asked the panel anything, or what it said back. Some of the attention you designed the page for goes to a panel you don't control and can't measure.

There are limits on who sees it. Per Google's help page, users must be 13 or older and in a supported region, signed in to Chrome, on a Mac, Windows computer or Chromebook Plus, and not in Incognito. The rollout is gradual, work and school accounts need an administrator to switch it on, and PPC Land found no EU country on Google's list of supported locales. So it isn't every shopper. In the U.S., UK and Canada, it can be some of yours.

If the answer isn't on your page in plain words, the panel will build one from whatever is there.

Answer the three questions on the page

We don't know exactly how Gemini chooses what to say from a page, and Google hasn't published it. What we do know is simpler: it works from what's on the page. If the answer isn't on your page in plain words, the panel will build one from whatever is there.

Take Google's three suggested questions as a template for your own best sellers.

Key features. Is there a short, plain list of what the product is and does, near the top, in text? Many product pages put the real facts inside images, banners or a spec graphic. A person can read those. Don't assume anything else can.

Weight and size. These are the questions that cause returns. Give the numbers in plain units, with the packed size where it matters, and make sure they match the box and the listing on any marketplace you sell through. If three of your own pages disagree, a summary may pick any of them.

Materials. The fill, the fabric, the finish, what it's coated with. Say it once, clearly, in the description. "Premium materials" doesn't answer the question; a summary of it won't either.

Then the fourth question in Google's picture: the reviews. You can't and shouldn't edit what customers wrote. You can make sure the reviews that load on the page are a fair set, not just the newest three, and that your replies to the complaints that matter are visible next to them. If the common complaint is "runs small," your sizing note should say so before a summary does.

What we'd skip

Don't rewrite pages for a machine. The fixes above help the shopper who scrolls just as much as the one who asks the panel, which is the point.

Don't hide facts behind tabs and accordions you'd never open yourself. Collapsed sections are fine for long care instructions. They're a bad home for the weight.

Don't start stuffing questions and answers into the page in a voice nobody talks in. A short FAQ that reflects real support emails is good. Forty invented ones are clutter.

And don't panic about traffic. The visit still happens; it's the conversation you can't see. Our note on Reddit writing a review page for your product covers the related problem of AI summaries of your reviews that live elsewhere, and blocking AI crawlers explains why opting out tends to hand the answer to someone else.

How the work moves

One afternoon per best seller

  1. Write down the three questions

    From support emails, returns notes and your own site search.

  2. Find each answer on the page

    In visible text, not only in an image or a closed tab.

  3. Fix what's missing or wrong

    Specs that match the box, sizing in plain units, care instructions.

  4. Read the reviews section cold

    Would a fair summary of what's showing match what you'd say?

  5. Ask the question yourself

    Where you have access, open the panel on your own page and compare.

Illustrative routine for a small catalog; not Google guidance.

Before the holiday traffic

Pick your ten best sellers. For each one, write down the three questions customers actually ask, from support emails, returns notes and your own site search. Find each answer on the page, in visible text. Fix what's missing or wrong. Read the reviews section as a stranger would. If you have access to Gemini in Chrome, open it on your own page and ask the same questions, and compare its answers to what you'd say at the counter.

Then give the job an owner. Product copy tends to be written once, at launch, by whoever was available, and then nobody touches it while the product changes underneath: a new supplier, a revised fill, a different box. If the weight on the page is from the first batch, every summary built from it is wrong too. Someone should check the facts on your best sellers whenever the product changes, not only before the holidays.

That's an afternoon per product at most, and most of the work is copy, not code. Where it turns into code, because specs live in three systems or the page template buries them, that's our web application development work: making the page and the systems behind it tell one story. Talk to us.

Related work: Paddle8

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎