What belongs on a product page

First, define the job of each field

The product name helps readers identify an item among other offers. Specifications provide comparable values. The description connects the product's design with its use. Instructions explain actions and restrictions. A store may give these parts different names, but distinguishing their jobs remains useful.

If capacity appears only in a paragraph, a reader may still find it. A catalogue filter will not automatically obtain the value from that paragraph unless the system supports that processing. Conversely, a completed filter field does not explain why the nominal 500 ml differ from the 450 ml used in the test report.

Before writing, inspect the place where the content will appear: what is visible on a phone, where variants are selected, which fields drive filtering, where text is truncated and whether an explanation can be opened. A single document labelled “product description” does not show these conditions. The content hierarchy needs to support the actual points at which people make choices.

A product name also has technical counterparts. The page's H1 heading, the HTML title element, the meta description, the name in a product feed and a title field in an internal program response are different entities. An identical field name does not establish identical rules. For each export, record where a value comes from, where it goes and which transformations are allowed.

Distributing one dossier across the page

For T500, we know the nominal capacity of 500 ml, the empty mug's mass of 280 g, that the lid is removable and that hand-washing the lid is permitted. In the fictional test, 450 ml of a drink initially at 95 °C were kept in the closed mug for six hours at an ambient temperature of +20 °C. At the end, the drink's temperature was at least 60 °C.

This is enough to support the following distribution. It preserves the distinction between specification values, the test result and care instructions.

Product name

“T500 insulated mug, 500 ml.” Product type, model and nominal capacity identify the offer. No colour has been added: the dossier does not specify one.

Specifications

“Nominal capacity — 500 ml”, “Empty mug mass — 280 g”, “Lid — removable”. The qualifier “empty” remains in the parameter label.

Description

“The lid can be removed and hand-washed separately from the body.” This is followed by a separate paragraph presenting the test result with all material conditions.

Care

The permitted method for washing the lid. Dishwasher suitability remains a question for the data owner; permission cannot be inferred from the fact that the part is removable.

The result can be presented in the description as follows (a separate analysis shows it as part of the complete T500 product page): “In the test, 450 ml of a drink initially at 95 °C remained in the closed mug for six hours at an ambient temperature of +20 °C. At the end, the drink's temperature was at least 60 °C.” This is longer than a promotional label, but the reader can see which situation the number describes.

Price, availability and delivery time require up-to-date offer data and their own update process.

Limited space requires choices

Suppose the top of the product page has room for one short line about a feature. All the conditions of the six-hour test will not fit. The editor has several options: show another verified parameter; mention that a test took place and provide a clear link to the result; or change the layout so that the conditional statement fits in full.

“Temperature-retention test result” can work as a link label. It does not itself promise a particular duration. A “Warm for 6 hours” label with a qualification far below already communicates a result without its necessary boundaries. A link to details does not always undo the meaning created by the main statement.

Start the selection with questions that affect suitability. For a replacement cartridge, that is the compatible device model; for a set, its contents; for a suitcase, its external dimensions and how they were measured. A blanket instruction to put everything important into the first three hundred characters cannot determine priorities.

How common a question is helps determine the order, but the consequences of a wrong answer may outweigh frequency. If a known restriction rules out use with a particular device, it cannot be removed in favour of a more popular topic. An unanswered question, meanwhile, remains a research task even if no place has yet been assigned to it.

A practical selection record contains the question, the supported answer, material conditions, the publication location and the reason for its priority. It can form the basis of a verifiable coverage plan. The decision can then be challenged on specific grounds: for example, by showing that the chosen location is not visible before purchase or that one variant needs a different answer.

Repetition can make an answer easier to find

The 500 ml capacity belongs both in T500's name and in its specifications. In the first location it helps identify the offer; in the second it supports comparison. This is justified repetition at different access points. Four adjacent phrases — “spacious mug”, “high-capacity model”, “large capacity” and “500 ml” — do not serve the same purpose.

Removing every repetition can make a page awkward to use. A reader who opens the instructions separately must be able to tell which model they concern. A dimension diagram needs labels even when the measurements also appear in a table. These representations need to agree, and it must be possible to update them when the source value changes.

Duplication also has a limit. If every section reproduces the entire test report, the conditions start to obstruct comparisons of simple parameters. A clearly named “Temperature-retention test” section is preferable, with short links to it wherever that result is discussed. The shortest wording must still avoid making a stronger promise.

Repeating the search query is a separate matter. The question “can the lid be washed?” is already addressed by the permitted care method. Mechanically adding the phrase five times provides no new information. Detail is determined by the answer to the need, not by the number of formulations of the same query.

A shared description must not assign a property to every variant

Suppose a second model, T350, appears on the same page. This is another fictional variant; its specifications have not been defined. If the T500 test paragraph moves into a shared section without naming the model, readers may take the result to apply to every variant.

Define the scope of each fragment: product family, model, variant or specific seller offer. Then check what happens when a variant is switched: do the name, numbers, images and explanations change consistently? A shared description is appropriate for genuinely shared properties, but that commonality also needs evidence.

Even an identical body shape does not justify transferring a thermal-insulation result. The same photograph does not prove identical contents. The rules of product identification still apply when text is placed on a page, even if the error looks like an interface problem.

A useful check is to open each variant and ask the same question across every visible part of the page. If the section labelled as the selected model's description still reports T500's result after T350 is selected, the page is inconsistent regardless of the quality of its individual sentences.

Check platform rules separately

For a specific channel, its rules become part of the brief. For example, Google Merchant Center requires an accurate product title and distinctions between variants; the title limit is 150 characters. The description has a limit of 5000 characters and must be consistent with other data and the landing page. These limits concern that particular data-submission system, not every title and description on the internet.

For titles and descriptions created with generative AI, current Merchant Center rules require structured_title and structured_description. Digital provenance is indicated by the nested digital_source_type attribute with the value trained_algorithmic_media. Natural-sounding editing does not override this requirement. The rules were checked on 6 November 2026; they should be checked again when a real export is configured.

The product page's internal structure may be richer than the export format. Several website sections may have to be combined into one field, while some information is passed as separate attributes. An explicit transformation process is needed. If conditions are lost during concatenation or truncation, the error occurs after the original text has been written.

Permitted formatting also needs a separate check: does the field support markup, line breaks and lists? A paragraph that reads clearly on a website can become an unbroken line in another channel. Acceptance needs to examine the delivered representation, not only the source file.

Check how readers find answers on the finished page

An image of the removable lid helps explain the design. It does not establish the permitted washing method. A bare “280 g” label does not say whether the empty mug was weighed. Visuals and text should explain the same parameters and complement one another.

Material conditions should remain available as accessible text. If they appear only as small lettering in an image, they are difficult to read on a phone; the image itself may also be unavailable. A measurement diagram benefits from labels within the diagram and a text explanation beside it.

To check the layout, use tasks with verifiable outcomes: find the empty mug's mass, identify the conditions of the six-hour test and determine the permitted lid-washing method. Show participants the page without telling them which section to use. Record the answer they found, how they understood its scope and where they had difficulty. Search time is meaningful only alongside answer accuracy.

If someone confidently repeats “500 ml, six hours in freezing weather”, a note saying “found in ten seconds” is insufficient. Find out which page elements the person relied on and what connections they made between them. A hypothesis about the cause of the error can then be tested by changing the wording or layout. This analysis examines content placement; the effect on purchases requires a different study.

T500 now has clearly distinguishable parameters, a test result and care information. The next decision concerns presentation itself: which properties to explain through action and benefit, which tone to choose and where an appealing phrase begins to promise too much.