Choosing which product attributes belong in visible copy
The supplier sent forty-one specifications, so the product page shows forty-one specifications. The buyer still can’t tell if it’s the right one. Sound familiar?
It’s rarely a shortage of information. The useful details are just buried among attributes that don’t help anyone choose.
I don’t treat a product page as a storage shelf for every catalogue field. Some information belongs in the feed, some helps staff manage stock, and some helps a person decide if the item is right for them. Your job is to make that last group easy to find, without hiding facts that matter for compliance or safe use.
Start with the decision the buyer is making
Before deciding whether an attribute should appear in the visible copy, write down the choice a person is trying to make. A buyer comparing two lamps may care about dimensions, light source, colour temperature and whether a bulb is included. A buyer choosing a notebook may care about paper size, ruling and whether the pages lie flat. The important attributes depend on the question, not on how many columns exist in an export.
This sounds obvious until you have a large catalogue. Then the same fields get copied into every description because they’re available. The reader ends up with a long block of data and the job of finding the one difference that matters.
For each product family, ask what could make a customer pick the wrong item, abandon the page or contact support before buying. Those are strong candidates for visible information. The answer may come from customer questions, returns notes, product experts or how people use the item. Don’t present a guess as a known pattern. No evidence? Flag it and ask someone close to the product.
Separate decision facts from catalogue operations
A catalogue contains fields that serve different jobs. A SKU, supplier reference or warehouse location can be essential to operations while being unhelpful to a shopper. That does not make the data useless; it means the product page is not necessarily the right place for it.
Some operational attributes help buyers indirectly. A model identifier stops someone ordering a replacement part for the wrong device. A material code may matter to a trade customer. Stock status changes whether an item is worth considering today. Decide who needs each field and where they’d look for it.
I like to sort candidate attributes into three groups:
- Choose: details that help compare options or confirm fit.
- Use safely: instructions, limits or compatibility facts someone needs after choosing.
- Run the catalogue: information mainly used by the business, supplier or fulfilment process.
The groups are a prompt for discussion, not a universal template. An attribute can belong in more than one group. If a trade buyer needs a manufacturer reference to place an accurate order, that code may deserve a visible place even if a retail buyer rarely uses it.
Put the important differences where people can scan them
A product description should explain what the item is and why the relevant details matter. A structured specifications section can carry precise values. Comparison tables can help when products differ along a small number of meaningful dimensions. Use labels that people understand, not internal field names that happen to fit the content-management system.
Avoid making every attribute a paragraph. If the value is easy to scan, a labelled value may work better than prose. If context is required, explain it. “Fits 12-inch frames” is more useful than a bare internal size code, but only if the measurement and fit claim are accurate.
It’s tempting to hide long lists behind tabs or accordions to keep the page tidy. That’s fine when the information stays accessible and the page still shows the facts for a quick decision. It’s a poor trade if someone has to open six panels to compare basic differences. Test the actual task: can a person tell which option fits without memorising values from another tab?
Do not turn missing data into confident copy
A blank field isn’t permission to guess. If the page doesn’t say whether an accessory is included, don’t imply it is. If a material description is vague, ask the product owner or supplier for a reliable definition. “Premium” is not a specification.
This matters for search too. Search engines can only reflect what a page says; they cannot settle an ambiguous product detail on your behalf. Adding more attributes may make a page look complete, but unsupported information can create customer confusion and reputational risk.
Keep a simple source note for attributes that carry a meaningful claim: who confirmed it, when it was checked and where the source lives. This need not become a bureaucratic system. A link to an approved product document or a named owner is often enough to make the next edit safer.
Design the field once, then check the output
When one product family has hundreds of pages, decide how its key attributes will be shown before any bulk edit. Give fields clear names, agreed formats and validation rules. Measurements need units. Colour names may need a controlled list. Compatibility fields should name the models, not rely on vague shorthand.
Then check the published template, not only the spreadsheet or admin screen. A field may be present in the catalogue but missing from the page. It may be shown twice, truncated on mobile or labelled differently across product types. Review a representative set of pages and include awkward cases: the product with a long value, a missing value and several options.
A sensible rollout is small. Pick a product family, update the field mapping and inspect the live output. Ask someone who understands the products to confirm the facts and someone who understands the customer task to confirm the presentation. Once the pattern works, document what should happen when an attribute is unknown or not relevant.
Keep the page useful as the range changes
Products change. Suppliers revise specifications, models get replaced and a once-important difference may disappear. Visible attributes need an owner and a review path, especially when the page is generated from structured data. Otherwise an old field can keep publishing long after its source has become unreliable.
A product-content review should therefore include the data source and the page template. Check a sample after supplier updates, theme changes or bulk imports. If a field becomes unused, decide whether to retire it rather than leaving an empty label in the interface. If a new customer question appears, add the answer where it belongs instead of creating another disconnected block.
Related reading
- Choosing a useful baseline before a storefront redesign
- How to explain product differences without repeating specifications
- A review workflow for supplier-provided product copy
Start with one product family and list the five or six attributes that really help someone choose, use or verify the item. Which are visible today, and who can confirm the ones that are missing?