# Product pages for shoppers who ask an assistant

> Shoppers ask assistants about products in their own language. What a product page needs to be found and used in another language, and what to review first.

Source: https://www.fluentc.io/articles/product-pages-and-shopping-assistants/
Published: 2026-10-20

A shopper asks an assistant, in Portuguese, whether a jacket like yours comes in a long size and ships to Portugal. The assistant answers in Portuguese. When it needs facts it doesn't have, it searches the web and reads product pages the way a search engine does: it fetches a page at an address, in a language, and works with what's there.

So the question for a store is the one search has always asked, with a shopper's phrasing on top. Is there a page, in Portuguese, at an address, that says what this product is, what it costs, whether it comes in that size and whether it ships there? If the only page is in English, the assistant can read it and answer. But the link it gives is to the English page, and the Portuguese searches it ran to get there turn up, as a rule, pages in Portuguese. Your English page was at a disadvantage before anyone read a word of it.

## What a product page needs in another language

Most of this list is familiar from [multilingual SEO for a store](https://www.fluentc.io/articles/ecommerce-multilingual-seo/). The assistant doesn't change the list. It raises the cost of leaving things off it.

- **Its own address per language.** `pt.yourstore.com/jackets/field-jacket/` or `yourstore.pt/...`. One address, one language, so it can be fetched, linked and cited.
- **hreflang on every product page**, so the Portuguese page and the English page are understood as the same product in two languages.
- **A translated title and description.** The product's name and what it is, in a Portuguese shopper's words, on the page and in its meta title and description.
- **Variants and sizes.** A product in three colours and five sizes has those words on the page. If they're still in English, "does it come in long?" has nothing to match.
- **Shipping and returns, in the language.** Whether it ships there, how long it takes and how returns work.
- **Checkout in the language.** A shopper who got this far in Portuguese shouldn't meet an English checkout.
- **Order emails in the language.** The confirmation is the last thing they read from you.
- **The same page every time.** A page that changes language with the visitor's settings can only be indexed in one of them.

## What FluentC does

On WooCommerce, the [WordPress plugin](https://www.fluentc.io/wordpress/) translates product titles, descriptions, variants and metadata, supports variable products and their variations, and translates cart and checkout fields, so the buying steps stay in the shopper's language. Edit a product in English and the translated versions stay in sync. Each language gets its own indexable URLs and `hreflang` is added for you. See [translating WooCommerce product pages](https://www.fluentc.io/articles/woocommerce-translation/).

On any other store, [FluentC Domains](https://www.fluentc.io/domains/) reads your pages, translates them, saves the translation and serves each language from its own subdomain or country domain, with `hreflang` set. Because they're saved, every shopper, crawler and assistant gets the same words, and you can edit any of them in the dashboard.

Order emails aren't on either list. Read yours in each language you sell in before launch.

## What to review first on a store

Machine translation gives you the first version of every product page. You won't read them all. Read these:

1. **Product names.** Decide which are translated and which stay as they are, then make it so.
2. **Size and variant labels.** "Long", "Regular", "Set of four". Short, repeated, easy to get wrong.
3. **Shipping and returns pages.** Every "only", "not" and "within" in them.
4. **The cart and checkout.** Field labels, error messages and the confirmation.
5. **Your best-selling products.** The first screen of each, in each language you sell in.

Change a line in the dashboard and that's what's served from then on. On WordPress, you edit without leaving it.

## What this doesn't promise

Nobody can promise which product an assistant will suggest, any more than a search ranking. What you control is whether there's a product page in the shopper's language to find, with the size, the shipping and the price on it. [How assistants find your site in other languages](https://www.fluentc.io/articles/found-by-ai-assistants-in-every-language/) has the general list, and [the e-commerce page](https://www.fluentc.io/ecommerce/) has the store overview.