Before changing a product page, preserve evidence of what shoppers, search engines, feeds, analytics, and fulfillment systems currently receive. A screenshot is useful visual evidence, but it cannot prove price logic, variant identifiers, inventory, structured data, checkout behavior, or integrations. Keep a dated technical and commercial baseline plus a recoverable prior version.
Capture the public experience
Save the canonical URL, HTTP status, response headers, source HTML, rendered HTML, desktop and mobile screenshots, title, meta description, canonical tag, robots directives, headings, product copy, disclosures, return and shipping information, images, alt text, video, reviews, calls to action, and accessibility state. Record viewport, browser, location or market, currency, login state, and capture time.
Exercise variant selection, quantity, price, sale price, stock status, subscription or bundle options, personalization, shipping estimate, add to cart, error state, and a test checkout path with noncustomer data. Stop before a real charge unless separately authorized. Record expected and observed behavior rather than simply marking the page good.
Preserve catalog and feed fields
Export the product's stable ID, SKU, global trade identifier where used, title, description, brand, category, variant IDs, option values, price, compare-at price, currency, availability, condition, inventory policy, image URLs, media filenames, weight, dimensions, tax class, shipping class, tags, collections, metadata, and update timestamp.
Google's Merchant Center product data specification requires accurate identifiers, titles, links, images, price, availability, and variant relationships. Preserve the feed row and diagnostics alongside the page because an apparently minor page edit can create a disagreement between visible content and submitted product data.
WooCommerce's CSV importer and exporter documentation describes core product export, import, column mapping, bulk updates, and optional custom metadata. If the page relies on an extension, record its fields separately; a core CSV is not proof that subscriptions, bundles, bookings, reviews, or custom options are recoverable.
Save structured data and search evidence
Google's product structured-data documentation covers product and offer fields such as price, availability, shipping, returns, identifiers, variants, and reviews. Save the exact JSON-LD or other markup, validation output, warnings, and the visible values it represents. Eligibility does not guarantee an enhanced search display.
Export a dated search baseline when available: indexed URL, impressions, clicks, queries, countries, devices, product-result appearance, and structured-data issues. Keep the filters and date range. Do not claim that a later ranking or traffic change was caused by the product-page edit without analysis.
Map ownership and integrations
Inventory the commerce account, catalog owner, domain, content system, repository, deployment service, image library, feed generator, Merchant Center, analytics, reviews, inventory, fulfillment, tax, shipping, consent, email, and payment links. Record accountable roles and recovery paths without copying credentials or tokens.
Map events and webhooks such as view item, select item, add to cart, remove, begin checkout, purchase, inventory update, and feed refresh. Preserve event names, required parameters, destinations, and test evidence. Use a staging or test mode; never create a false real order to prove tracking.
Keep deployment and rollback proof
Store the prior content export, template or code revision, asset list, configuration version, database backup where appropriate, redirect map if the URL changes, and restoration steps. Define rollback triggers for wrong price, unavailable purchase, broken variant, inaccessible control, lost disclosure, missing analytics, feed rejection, or security failure.
After deployment, read the live page and compare the acceptance matrix. Verify canonical, robots, structured data, feed alignment, variants, price, availability, media, keyboard use, cart, test checkout, analytics, and error monitoring. The evidence set is complete when another authorized person can reconstruct the old state, explain every intended change, verify the live result, and restore the prior version without guessing.
Sources
- Product data specification — Google Merchant Center Help
- Product CSV Importer and Exporter — WooCommerce Documentation
- Introduction to Product structured data — Google Search Central, Dec. 10, 2025