Skip to content
WooCommerce

The product page, rewritten for a buyer who is asking an assistant

What changes on a WooCommerce product page when the first reader is a retrieval system deciding whether your product answers someone's question.

How should a product page be written so an AI assistant can recommend it?

Mostafa Nouh — portraitMostafa NouhPublished 7 min read

A buyer asking an assistant is not typing keywords. They are describing a situation: a gift for a wedding, a perfume that lasts through a summer day, a kitchen mixer that fits under a cabinet. The page that gets recommended is the one that contains a passage matching that situation — not the one that repeated the product name eleven times.

The shape of a page that gets picked

  1. A full sentence saying what the product is, its category and its defining specification.
  2. Two or three sentences on who it is for and which situations it suits.
  3. The specification as a real table — size, material, weight, contents — not an image.
  4. Price and currency in text, near the top, matching the Product schema exactly.
  5. Availability, shipping destinations and a typical delivery time, in words.
  6. Returns and warranty in one sentence each, on this page, not only in a policy link.
  7. Honest limits: what it is not for. This is the passage that earns a recommendation.

The last item surprises people. A page that says "this is a heavy winter fragrance and it is the wrong choice for daytime in the Gulf summer" is far more useful to a system trying to match a situation than a page claiming the product suits everyone. It also converts better, because the buyer who reads it trusts the rest.

The schema has to agree with the page

Product structured data carrying a price the page does not display, or an availability the stock system contradicts, is worse than no markup: it teaches consumers that your data is unreliable. On WooCommerce the usual culprit is a theme that overrides the default output, or a currency-switcher plugin that changes the visible price and not the markup.

In Arabic, write it in Arabic

A machine-translated product description reads as machine-translated, in both directions. Buyers in this market ask in Arabic, often in dialect, and a description written by someone who knows the product in Arabic will match those questions in a way a translation of English marketing copy never does. Numbers, sizes and Latin product names still need bidirectional handling so they do not scramble.

Before you call a product page done

  • Disable JavaScript and reload: are the price, description and specs still there?
  • Read the page aloud as an answer to a buyer's question. Does any sentence answer it?
  • Does the visible price equal the price in the structured data, in the same currency?
  • Is there one sentence naming a situation this product is wrong for?
  • Does the Arabic read as Arabic, and do the Latin runs and numbers sit correctly?
  • Time to first byte on a cold cache — would a retrieval deadline have waited?

Sources

Contact

Have a site or store that needs to work better?

Tell me what is happening and on which page. A diagnosis is a useful first deliverable on its own.

I read every message myself and reply within one working day — usually with a question or two before anything else, because a scope worth quoting needs them answered.

Available for remote work aligned to EST hours
Mostafa Nouh — portrait

Mostafa Nouh

Full-Stack Developer & Product Builder

Location
Egypt · Remote