Write product pages that support a decision

Describe the observable product

Name the item using words customers use and specify material, dimensions, variants, contents and use. Separate checked measurements from illustrative examples. A supplier description may miss questions specific to your audience.

Add short answers to repeated uncertainties: care, compatibility, timing or availability. The catalogue guide helps define common fields before publishing dozens of pages.

Distinguish identifiers before enriching the product page. A SKU is merchant-specific; a GTIN identifies a trade item under the relevant rules. Fictional example: DEMO-LOT12 may be an internal SKU, but renaming its field does not make it a GTIN. Google Merchant Center recommends a stable id, possibly the SKU, and says not to recycle it for another product. Preserve original values, including leading zeros, rather than converting them into quantities; then check the format required by each destination.

For a pack, record who assembled it and what the supplied reference identifies. In Merchant Center, manufacturer-created multipacks use the multipack’s identifiers; seller-created groupings follow guidance for individual-product identifiers and the applicable multipack setting. Do not mix item, variant and packaging level in an ambiguous column. Some products have no assigned GTIN: the documentation says never to guess one. Confirm the reference and package contents with the product source before publication.

• Characteristics actually measured.
• Variants distinct and clear.
• Frequent questions answered on the page.

Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

Show several useful views

Prepare a main view and details that support the decision: scale, material, assembly and delivered contents. Fictional example: a lamp is photographed with a decorative bulb that is not included; state that exclusion near the image and in the package contents. When a color is selected, show the matching variant or explicitly explain the photograph’s illustrative scope.

Give each image suitable alt text and a lightweight file. Test phone crops and zoom where useful. A beautiful photo cannot replace written dimensions.

• Product-specific main photo.
• Details and scale visible.
• Lightweight accessible images.

Make terms visible

Present price and inclusions, availability, relevant fees or arrangements, and the next action near the decision point. Conditions that can change need editorial ownership and coordinated updates.

Google product data guidance distinguishes informative product pages from directly purchasable products. Put only accurate, visible information in structured data.

• Price and availability consistent.
• Terms accessible before action.
• Markup matches visible content.

Check the complete journey

Test the product page from a category, search and a direct variant link. Fictional example: a selected size becomes unavailable after the page opens; status, price and action should remain consistent through to the basket. Also check returning to the list and retired products. A visible image must not imply that the item can still be ordered.

Review pages after pricing or catalogue changes. The checkout guide continues the test after product selection.

Fictional exercise: two lamps in one family have references LAMP-BL and LAMP-RD. They may share a manufacturing description, but colour, image, price and availability must match the selected variant. A demonstration internal reference is not a GTIN; do not invent a standard trade identifier.

For Google variant eligibility, each variant needs a distinct identifier in its markup and a distinct URL that preselects it. The documentation distinguishes single-page product groups and variants across multiple pages; one canonical rule cannot be applied to both indiscriminately. Test the direct link and basket: changing the image alone does not validate the journey.

• Entry paths and direct links tested.
• Variants and stock states handled.
• Review after product changes planned.

Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

• Google Search Central · Product variants

  Google Search Central documents variant identification and access; Schema.org defines grouping. Sources consulted on 22 October 2026. LAMP references and products in this exercise are fictional.

• Schema.org · ProductGroup

  ProductGroup groups variants with shared characteristics; the group itself is not the product directly offered for sale.