A product page combines customer-facing content with operational data. The visible title and description are only part of the handoff; variants, SKUs, prices, inventory rules, images, accessibility text, shipping facts, return information, structured data, reviews, redirects, analytics, and ownership controls may live in different systems. Transfer the page as a tested data package, not a copy-and-paste exercise.
Inventory the product record
List the product title, handle or slug, description, vendor or brand, category, tags, SKU and barcode identifiers, options, variants, prices, compare-at prices, tax status, weights and units, inventory locations, shipping attributes, media, alt text, SEO fields, structured data, policy references, and page-specific scripts. Mark each field's system of record so the new tool does not overwrite authoritative inventory or pricing.
Export data and dependencies
Use the platform's supported export, retain an untouched original, and work on a copy. Shopify's product CSV documentation shows why field relationships matter: variant-related columns can depend on option names and values, images may span multiple rows, metafields can be included, and multi-location inventory may require a separate inventory CSV. Even when using another platform, ask which dependencies are excluded from the main product export.
Preserve media and rights
Download original product images and videos only when the business has the right to reuse them. Preserve filenames, alt text, captions, crop instructions, and links between media and variants. Record photographer, supplier, model-release, trademark, or license restrictions. Test that the new host serves crawlable HTTPS image URLs and does not depend on a temporary URL from the old platform.
Rebuild the machine-readable product
Google's merchant-listing documentation says eligible product pages need Product information including a name, image, and an Offer, and it recommends initial-HTML structured data for merchants seeking shopping experiences. Recreate the markup from the new page's live values instead of copying stale JSON-LD. Validate price, currency, availability, URL, image, shipping, and return-policy references against what a customer actually sees and can buy.
Map URLs and redirects
If the product URL changes, map the old page to the corresponding new product, not to the store homepage. Google recommends server-side permanent redirects where possible, testing them, updating canonicals and internal links, and keeping redirects for at least a year. Preserve campaign and profile links where practical. If variants have distinct URLs, test each one and decide whether it remains distinct or consolidates to a supported canonical page.
Transfer operational ownership
Add the new owner through the platform's account controls and verify permissions for editing, inventory, discounts, analytics, and publishing. Do not share a personal password. Move API keys and webhooks through a controlled secret-rotation process, and confirm that integrations point to the new product identifiers. Payment, tax, banking, and identity fields should be entered by the authorized owner through the provider's official interface.
Run an acceptance order
In a preview or test environment, import the product, inspect every variant, and compare prices, inventory behavior, media, structured data, and policies. Place a non-charge test order only where the platform provides an approved test mode; otherwise stop before payment. After cutover, check the public URL logged out, follow the product through cart and checkout without submitting a charge, verify analytics, and monitor 404s, inventory mismatches, and feed errors. Keep the rollback copy until the owner accepts the transferred page.
Sources
- Using CSV files to import and export products — Shopify
- Merchant Listing Product Structured Data — Google Search Central
- Site Moves and Migrations — Google Search Central