Document a product page by connecting every customer-facing fact to an owner and source of truth. The record should cover product identity, approved claims, price and availability feeds, reviews and disclosures, structured data, publishing authority, and live verification.
Establish the product source of truth
Record the product identifier, name, variants, manufacturer or supplier record, approved description, image rights, specifications, price source, inventory source, shipping policy, return policy, and status. Name the owner of each field and the system that controls it.
Separate durable product facts from changing operational data. Materials or dimensions may come from an approved specification, while price and availability may come from commerce software. Document which system wins when the page, feed, and internal record disagree. Never repair a mismatch by copying whichever value happens to be visible.
Keep claims and reviews accountable
For each performance, comparison, environmental, health, warranty, or savings claim, link the approved wording to its evidence and reviewer. Record expiration or review triggers where evidence may change. If the evidence does not support the displayed claim, remove or narrow the claim before release.
The Federal Trade Commission's endorsement guidance says endorsements should be truthful and not misleading, material connections should be disclosed, and endorsers should not describe product experience they do not have or make claims requiring proof they lack. Document who verifies review provenance, incentives, permissions, editing rules, and disclosures. Do not mix owner-written promotion with customer reviews.
Record structured data and feed settings
Google's Product structured data guide explains that product pages can provide details such as price, availability, ratings, shipping, and returns for eligible search experiences. It distinguishes product snippets from merchant listings and notes that combining on-page structured data with a Merchant Center feed can help Google understand and verify product data.
Document which markup type is used, where its values originate, who maintains the feed, and how discrepancies are detected. Include the canonical URL, variant URL rules, currency, identifiers, availability mapping, shipping and return sources, sitemap, and last test result. Search enhancements are not guaranteed, so record eligibility tests rather than promising a particular appearance.
Assign approval and publishing roles
Name the product-data owner, merchandising approver, legal or compliance reviewer when applicable, commerce administrator, feed owner, developer, and release approver. One person may hold several roles, but each responsibility must be explicit. Store credentials in the approved manager, not in the page record.
Define which changes may publish automatically and which need approval. A stock update may follow a trusted inventory feed; a new product claim, testimonial, or return condition should follow the business's review rule. Record emergency contacts for incorrect price, unsafe content, or broken checkout behavior.
Verify the live page
Before release, compare the rendered page with the approved record. Test the selected variant, price, availability, image, accessible name, add-to-cart path, shipping and return links, disclosures, canonical URL, and structured data. After deployment, retrieve the public URL and confirm the same fields. Preserve the release identifier and result.
Keep the previous working version and document rollback. A useful handoff test asks a new owner to trace one claim to evidence, one price to its source, one review to its disclosure record, and one markup value to the live page. If any step depends on memory, the documentation is incomplete.
Sources
- Introduction to Product structured data — Google Search Central, Dec. 10, 2025
- Advertisement Endorsements — Federal Trade Commission