Key takeaways
- Your product title is usually the first and most prominent text an agent reads, so leading it with the category, key attributes, and use-case makes the product legible to a query-matching agent.
- In the ACES study the rewritten field is the product's displayed title/description text (one field in its mock storefront), and the paper describes the winning rewrites as title changes, with query keywords moved to the front of the title the most consistent driver.
- Even so, the effect was concentrated (most product-and-model pairs saw no change while a minority saw large gains), so a title rewrite is a skewed bet, usually neutral and occasionally decisive.
- Write titles in the words a shopper actually types, and keep the brand name after the descriptive words rather than in place of them.
- Because the payoff is uneven, test a rewrite on your own catalog rather than trusting a formula. The protocol for running that test is published; no measured result on this site stands in for it.
How an agent reads your product title
A shopping agent does not skim. It reads structured product data field by field and scores each product against what the shopper asked for. Your title is usually the first and most prominent text field in that record, so it does much of the work of telling the agent what the product actually is. The rest of the record (your feed and your product schema) fills in the price, availability, and attributes around it.
We read the public evidence to mean that an agent weighs how closely your product text answers the shopper's actual query, which puts a title written in the shopper's words at an advantage over one written in a brand's private languageHypothesis (our analysis). Be precise about what that rests on: in the controlled evidence later on this page, the rewritten field is the product's combined title/description text (a single field in the study's storefront), and the paper itself frames the winning rewrites as title changes. What remains unmeasured is a separate title-versus-description comparison, and everything below keeps that line visible.
On ChatGPT, your title is an input, not the label
One major surface does not always show shoppers the title you wrote. OpenAI states that ChatGPT may generate simplified product titles and descriptions from the information it receives from third-party providers, to make results easier to read, because merchants often use varying titles and descriptions for the same product.Spec-factOpenAI, Shopping with ChatGPT Search help article On ChatGPT, then, your title is an input the model rewrites, not the exact string a shopper reads.
That bounds what title work can do here without making it pointless. Because the displayed title is generated from the metadata you supply, the words and attributes you put in your title still feed the rewrite, so a title that clearly states category, attributes, and use-case gives the model better material to simplify; what a merchant cannot do on this surface is control the final wording a shopper sees.Hypothesis (our analysis) OpenAI does not publish how the rewrite weighs its inputs, so treat this as the ceiling on title optimization for ChatGPT, not a formula: supply clean, complete, query-matching text, and accept that the phrasing shown is the model's.
The model also writes the labels shoppers read as signals. Feature labels such as "Budget-friendly" or "Most popular" are generated by the model and are not guarantees or verified statements; a "Budget-friendly" label might mean that reviewers frequently mention good value, not necessarily that the product is the lowest price available.Spec-factOpenAI, Shopping with ChatGPT Search help article You cannot request those labels, and you should not write copy that pretends to have earned one.
None of this undoes the rest of this page. Everywhere else your title text is read more literally, and even on ChatGPT it is the raw material the rewrite starts from, so the same query-aligned wording still helps.
The literal-match problem
Human shoppers forgive a clever product name because they read the photo, the price, and the star rating around it and infer what the thing is. An agent resolving a query has less room for that inference. When a title omits the words a shopper used, it risks being scored as a weaker match to the query (the literal-match problem) because the agent has fewer cues to connect your product to the requestHypothesis (our analysis). This is a claim about mechanism, consistent with the rewrite evidence below, and it is the crux of agent selection at the title level: be the text that most obviously answers the query.
The title formula: category, attributes, use-case
If the goal is to repeat the words a shopper is likely to type, a reliable ordering is to lead with the category, follow with the attributes that distinguish the product, and close with the use-case or fit. This is our recommended structure, not a rule any agent enforces:
- Category first. The plain noun a shopper searches ("weighted sleep mask," "USB-C car charger"), so the product is legible before any modifier.
- Distinguishing attributes. Material, size, colour, capacity, or compatibility: the words that separate your product from the rest of its category ("organic cotton," "65W," "blackout").
- Use-case or fit. Who or what it is for ("for side sleepers," "iPhone 15/16"), which is often exactly how a shopper phrases the underlying need.
- Brand where it helps, not instead. Keep the brand name if it earns trust, but let it follow the descriptive words rather than replace them.
The same title then feeds every engine that reads your catalog, so the fix is write-once. How a given platform surfaces that title differs. The ChatGPT shopping playbook → covers applying this where OpenAI's agent reads your feed.
Before and after: title rewrites
The formula is easier to trust once you see it applied. Each pair below takes a title written in a brand's private language and rewrites it in the words a shopper types, leading with the category and the attributes that set the product apart. We expect the rewritten titles to answer more queries, because every descriptive term you add (material, size, capacity, compatibility, fit) is one more attribute an agent can check against a request, while a bare model name offers almost noneHypothesis (our analysis). The brands, models, and specs below are invented to keep the pattern clear.
The move is the same in every pair: nothing about the product changed, only how legibly the title states what it is and how many of its attributes an agent can pair with a query.
The evidence: text rewrites shifted selection
The reason to take title wording seriously is that changing product text measurably moved which product an agent picked in the strongest public study we have. One structural fact matters throughout: in the ACES storefront, a product's displayed title and description are a single text field, so the paper uses "title" and "description" for the same rewritten text.
In the ACES simulation, rewriting a product's description to better fit the shopper's query raised its market share in the agents' picks by an average of +3.66 percentage points for Claude Sonnet 4, +8.37 pp for GPT-4.1, and +14.79 pp for Gemini 2.5 Flash, all statistically significantReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). ACES is a controlled simulation (vision-language-model agents choosing from a mock storefront in randomized trials, not a record of real purchases on live stores), so read these as evidence that text can move selection, not as guaranteed conversion math for your catalog.
From there, the step to titles is shorter than we once framed it, because the paper itself makes it. In ACES the rewritten field is the product's displayed title/description text, a single field; the paper's current revision instructs its seller agent to change the product title without inventing features or adding spurious keywords, describes the winning rewrites as title edits that can materially shift selection shares, and identifies relocating the query's own terms to the beginning of the title (keyword front-loading) as the most consistent driver of the gainsReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). One caveat stays ours: ACES never ran a title and a long-form description as two separate fields, so a field-versus-field comparison remains unmeasured. What the evidence shows is that rewriting the product's title text moved selection.
Why the effect is concentrated, not uniform
A rewrite is not a lever that pays out every time. The description-rewrite effect was concentrated rather than uniform: in 67% of the category-model pairs a one-shot rewrite produced no significant change, while 33% produced large gainsReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). Where it did land, the upside was real: the biggest outliers reached +52.0 pp for an office lamp on Gemini 2.5 Flash and +30.3 pp for an office lamp on GPT-4.1ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17).
For a title that means the expected value is skewed: most rewrites will do little, a minority will do a lot, and you cannot tell in advance which product falls where. Treat a query-aligned title as a low-cost bet with an occasional large payoff, not a reliable percentage lift you can bank across a catalog.
From a title to a test
Because the payoff is uneven (mostly neutral, sometimes large), a title rewrite is a hypothesis about your specific catalog, not a guarantee, and the only honest way to know is to measure it. The protocol for measuring it on your own catalog is in how to test agent selection →. Run it before you rename a catalog on faith, and read how AI shopping agents choose products → for the full set of signals a title sits inside.