The product_detail attribute in Google Shopping (and product_highlight)
How the product_detail attribute and product_highlight work in Google Shopping, structured specs, benefit bullets, where each surfaces, and how to write them well.
These two attributes carry the product information that doesn't fit anywhere else. product_detail is structured specification data, section, attribute name, value, like a spec table in feed form. product_highlight is up to 100 short benefit bullets, though the best listings use 4 to 6. Both surface in the expanded product views shoppers see on the Shopping tab, and both are free reach most feeds leave empty.
Two attributes for the long tail of product information
| Attribute | Structure | What it carries | Rough limit |
|---|---|---|---|
product_detail |
section: attribute_name: value (three sub-fields) |
Technical specs | Repeat as needed |
product_highlight |
Plain short text, repeatable | Benefit bullets | Up to 100; aim for 4-6 |
Titles carry ~150 characters and descriptions are prose. Everything a shopper would find in your spec table or bullet list (wattage, material, capacity, compatibility, what's in the box) has nowhere structured to live in a basic feed. These two attributes are that home, and because most merchants never populate them, they're an easy differentiation in the expanded views where buying decisions actually happen.
product_detail: the spec table in feed form
Each product_detail entry has three parts:
section_name(optional): the grouping header, e.g.General,Dimensions,Battery.attribute_name(required): the spec's name, e.g.Material,Capacity,Screen size.attribute_value(required): the value, e.g.Stainless steel,1.7 l,6.1 in.
In a text feed the sub-fields are colon-separated within one column, and the attribute repeats for each spec:
product_detail: General:Material:Stainless steel
product_detail: General:Capacity:1.7 l
product_detail: Power:Wattage:3000 W
Guidelines that keep entries useful:
- One fact per entry: don't cram "1.7l, 3000W, cordless" into a single value.
- Use the attribute names shoppers and manufacturers use (
Wattage, notpwr_spec_1). - Don't duplicate attributes that have their own field: colour, size, gender and material belong in their dedicated attributes, not in product_detail.
- No promotional text, prices or shipping claims: specs only.
product_highlight: the benefit bullets
product_highlight is repeatable short text: the "why you'd want this" list:
product_highlight: Boils a full 1.7l in under 3 minutes
product_highlight: Quiet-boil design at under 60dB
product_highlight: Removable limescale filter, dishwasher safe
product_highlight: Auto shut-off and boil-dry protection
What separates good highlights from filler:
- Standalone sentences a shopper can absorb in a glance: under ~150 characters.
- Concrete and specific: "boils 1.7l in under 3 minutes" beats "fast boiling".
- Benefits and differentiators, not spec repeats: the wattage is already in product_detail; the highlight is what the wattage does for the shopper.
- 4-6 of them. The ceiling is 100, but nobody reads 100 bullets; a tight six is the format working as intended.
Where these actually surface
Both attributes feed the expanded product view: what a shopper sees after tapping a result on the Shopping tab or a product panel in Search: highlights render as a bullet list, product_detail entries as a spec table alongside data from Google's own catalogue. They can also inform which filtered and spec-driven queries your product matches, which is where the reach comes from: approved products don't compete for queries their data doesn't answer (see how listings work).
Deep dive Why structured beats prose for the same information
Most merchants already have this information: it's in the description, the spec tab, the bullet list on the product page. The instinct is that Google "reads the page anyway", so restating it in the feed feels redundant. It isn't, for three reasons:
- Named fields are unambiguous. A description saying "powerful 3000W element with 1.7L capacity" requires Google to infer which number is which spec. A
product_detailentry sayingWattage: 3000 Wdoesn't. For query matching (someone filtering to kettles over 2500W) the structured version is the one that reliably qualifies you. - The feed is the contract; the page is a hint. Google composes listings from your submitted attributes first. Data that only exists as landing-page prose may or may not be extracted, and you have no visibility into whether it was. Data in the feed is deterministically yours.
- Structure survives translation and comparison. In multi-country feeds and comparison surfaces, a named attribute-value pair maps cleanly across languages and across competing offers of the same catalogue product. Prose doesn't.
The economics follow from that: writing 4-6 highlights and a dozen spec rows per product is trivial for ten products and impossible by hand for ten thousand: which is why coverage of these attributes is near zero across typical feeds, and why populating them at catalogue scale is disproportionately valuable. This is exactly the kind of field a feed enrichment layer generates from the product data you already have (page copy, spec tabs, option values) written to a supplemental layer without touching your store. Both attributes are among the 20 enriched fields /tools can populate.
How this works in /tools
Enrichment builds product_detail entries and product_highlight bullets from your existing product content, normalised into Google's expected structure, and serves them through your enriched feed: the supplemental layer means nothing is written back to your platform. Coverage of optional-but-valuable attributes like these is tracked in your Feed Health Score, and the full field list is in the 20 enriched fields. For the attributes that are required, start from the product data spec overview.
Frequently asked questions
What is the product_detail attribute used for?
It submits structured technical specifications, each entry is a section name, an attribute name and a value, like General / Material / Stainless steel. Google shows these in the product's expanded detail view and can use them to match filtered and spec-driven searches that titles alone can't cover.
How many product highlights should I add?
Google accepts up to 100 but recommends 4 to 6. Each is a short standalone bullet, best kept under about 150 characters, focused on what a shopper gains, not a keyword list and not a rehash of the title.
Is product_detail the same as the description?
No. The description is prose; product_detail is structured data with named fields Google can read individually. A spec buried in a paragraph is visible to shoppers who read; a spec in product_detail is usable by Google for matching and display. Submit both.
Do these attributes affect ranking?
They're optional, so nothing is disapproved without them. But they give Google more structured data to match queries against, a search for "1000W blender" can be answered by a product_detail entry even if the title omits the wattage, which widens the queries you're eligible for.