Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

Migrating Product Images Without Breaking Search and Feeds

Originals, thumbnails, file names, alt text and the three systems that consume images invisibly: social previews, product feeds and marketplace connectors.

Product images are the most underestimated part of a store migration. They are easy to export, slow to move, and create problems that surface months later — thumbnails that never regenerate, pages that load the original 4000-pixel upload, WhatsApp previews that show a broken square.

Here is what actually matters, in the order it needs attention.

Bring the originals, but serve the right size

Export the highest-resolution version you have. You cannot regenerate a large image from a small one, and you will want the originals for marketplaces, catalogues and future formats.

Then let WooCommerce generate the sizes it needs. Two failures are common:

  • Only thumbnails exported. The store looks fine at grid size and falls apart on the product page, on retina screens, and anywhere a marketplace needs 1000px
  • Regeneration never triggered. Images import, but the intermediate sizes are missing, so WordPress serves the full-size file at 300px with width and height attributes that lie

After import, run a thumbnail regeneration and confirm one product page serves a sized image, not the original.

File names matter more than you think

Migrated files often arrive with names like DSC_04821.jpg or a hashed string from the CDN. That is a wasted signal, and it makes the media library unusable for humans.

Renaming 3000 files after import is painful but not impossible. Renaming 3000 files before import is a script. A practical rule: product-slug-01.jpg, product-slug-02.jpg. Sequential, predictable, and readable in the media library.

If you cannot rename everything, rename the top 100 products by revenue. That is where the gain is.

Alt text is not decoration

Image alt text serves two audiences: screen readers and image search. In a migration it is usually either empty or copied from the product title on every image.

Rules that hold up:

  • Describe the image, not the product title: “Navy cotton apron folded on a wooden surface”
  • Do not repeat the product name in all five gallery images
  • Do not stuff keywords — an alt attribute longer than about 120 characters is almost always written for a crawler, not a person
  • Decorative images should have an empty alt, not a description

If the old store had alt text, migrate it rather than regenerating from titles. If it had none, write it for the top products and leave the long tail empty — empty is honest, keyword-stuffed is a liability.

Format and compression

WebP is worth doing, but not during the migration. Convert after launch, once the catalogue is stable, using a plugin or at the CDN layer. Doing it during migration means debugging two problems at once.

What to do during migration: confirm nothing is uncompressed. A 2MB JPEG served at 600px is the single most common cause of “the new site is slower than the old one”.

CDN and hotlink protection

If the old store used a CDN, image URLs in the database may point at the CDN hostname. After migration those URLs either keep pointing at the old CDN — which you will eventually cancel — or break.

Two-step fix: rewrite stored image URLs to local paths during import, then put the new site behind a CDN with its own pull configuration. Do not leave a hard dependency on a CDN you are migrating away from.

The other trap is bot protection. Image CDNs and security layers sometimes block requests that do not look like browsers, which breaks feed generation and social previews. Test that an image URL loads with a plain request, not just in your browser.

Gallery structure

OpenCart and WooCommerce both support multiple images per product, but the semantics differ. In WooCommerce, one image is the featured image and the rest are gallery; in OpenCart the ordering is often arbitrary.

After import, check a sample: is the first image the one a customer should see? Is there only one featured image per product? Duplicated featured-plus-gallery entries produce a product page with the same image twice.

The invisible work: previews and feeds

Three systems consume product images outside the product page, and migrations break all three:

System What breaks
Open Graph / social previews No featured image set, so shares show a blank card
Merchant Center feeds Images under 500×500, or URLs that redirect
Marketplace connectors Missing high-resolution originals

Each of these has a distinct requirement, and none of them is visible on the storefront. Check them explicitly after import — the Merchant Center guide covers the feed side in detail.

A workable sequence

  1. Export originals; keep the orphan cleanup from the catalogue cleanup pass so you are not moving dead files
  2. Rename files by product slug where feasible
  3. Carry existing alt text; write new alt text only for top products
  4. Import, then regenerate thumbnails
  5. Set featured images — confirm one per product
  6. Rewrite any CDN-hosted URLs to local paths
  7. Verify a product page serves sized images, and that an image URL loads without a browser session
  8. Check social preview and feed requirements separately
  9. Convert to WebP after launch, not during

Most image migrations are judged by whether the product page looks right. That is the lowest bar. The failures that cost money are in search, feeds and social — and they are invisible unless you look for them.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote