Start with the decision, not a content quota
A shopper may need to check size, compatibility, materials, contents, availability, delivery or a return condition before choosing. Which details matter depends on the product and the buyer's task. Begin by listing the questions that could change the choice; do not add a field merely because another product page has one.
One self-reported Poshmark discussion gives a narrow example: a poster says they passed on bags without measurements because photos made the size hard to judge. This is one resale-platform post, not detail of prevalence or a general buying rule, but it shows why dimensions and images can answer different questions.
When using support questions as drafting prompts, summarise the question in general terms and keep account-specific details in the support conversation.
Separate a verified product fact from a benefit claim. Ask the product owner to confirm dimensions, materials, compatibility, included parts, care instructions and any safety information. If a detail is unknown, leave it out or record it for follow-up rather than turning an assumption into a confident claim.
Map each question to a verified answer
Use a small content map to decide what belongs on the page and where. The fields below are prompts to check against the product, not a universal specification. Keep the answer close to the selection or action it affects, with a plain link to fuller policies where needed.
| Shopper question | Information to verify | Useful placement |
|---|---|---|
| Will it suit my use or fit my space? | Dimensions, materials, compatibility, intended use and relevant limits. | Beside the option or specification the buyer is comparing; explain technical terms. |
| Which version should I choose? | Variant names, option values, price, image and stock state for each choice. | Within the selector, with the selected option reflected in the page. |
| What arrives in the package? | Included components, accessories, quantities and items sold separately. | Near the product description and purchase action. |
| When can I receive it, and what if it is unsuitable? | Dispatch or delivery information, applicable conditions and the current returns route. | A concise summary near the decision, linked to the full policy. |
| What detail can I inspect visually? | A useful view of scale, finish, contents or a feature that text alone cannot show. | In a consistently ordered image gallery with an appropriate text alternative. |
Keep product facts separate from promotional wording
Create a source record for decision-critical fields: the value shown, the source of truth, the person or system responsible for checking it, and when it was last confirmed. Product data can come from a supplier, product owner, inventory system or confirmed policy; name the source rather than merging conflicting values.
Shopify's documentation, for example, lists descriptions, media, inventory and variants among the details its product tools can manage. That describes Shopify's platform; other systems and product types may use different fields. A feature claim should still be supported by product detail. If compatibility, material, care or an included component is not confirmed, ask the owner or omit the claim rather than filling the gap with inference.
Use images to answer a specific question
Plan the gallery around what the buyer needs to inspect: shape, scale, finish, controls, contents, packaging or the product in use. Use a close view when a small feature affects the choice, and do not make a lifestyle photograph the only view of a physical detail. Keep the sequence predictable across similar products when that helps comparison.
Write alternative text for the image's purpose in context. W3C's decision tree distinguishes informative images that need a brief description from decorative images that use an empty alternative. Avoid repeating the same product title in every image description; describe the information that view adds.
Check variants and fulfilment as one journey
A page can contain accurate facts and still confuse a buyer if selecting an option does not update the image, price or availability that belongs to it. Test each meaningful variant, including the state when an option is unavailable. Check that delivery and returns summaries point to the current policy and do not promise a service level the fulfilment team cannot meet.
Google's ecommerce guidance says sharing ecommerce data and site structure can help it find and parse product information. If you use product structured data, represent the information visible on the page. Google notes that, on a single-page variant design, the image, price and availability may change as shoppers select options while the markup does not change dynamically; the suitable structure depends on the page and URL design. Structured data does not guarantee a search result.
Test the page with a concrete shopper task
Ask someone unfamiliar with the item to complete a realistic task without coaching: choose the version that fits a stated constraint, identify what is included, or find the relevant delivery condition. Record the answer they were looking for and where they expected to find it. Repeat on a narrow screen and with the actual option controls, not just a static design.
For a hypothetical desk lamp, a task might be to confirm its height, whether the bulb is included, which plug is supplied and what the chosen finish looks like. Each answer should trace to an confirmed specification or operational source. If the tester cannot find it, move or clarify the information; do not assume a longer description will solve a placement problem.
A usability check tells you whether an answer is findable; it does not prove that a change increases sales.
A final product-page content check
Before publishing, have the product owner check the source facts, confirm that the chosen options match their images and availability, and review the delivery and returns links. Ask a shopper to find one decision-critical answer on mobile. Remove unsupported claims and mark unresolved fields for follow-up rather than implying certainty.
The useful page is the one that answers the questions relevant to that product with information the business can stand behind. A template can keep the work consistent, but it should leave room for meaningful differences between products.
- The product and intended use are plain.
- Decision-critical facts have a named source and owner.
- Options, price, imagery and availability agree.
- Images add useful inspection detail and have suitable text alternatives.
- Delivery, returns and support information is current and linked.
- A shopper can complete a specific product-selection task without guessing.