A media migration can change more than page weight. Image URLs may be referenced by search results, external sites, product feeds, saved links, or older articles. Replacing the visible image in a new design does not establish that those relationships have been preserved.
When image-search discovery matters, the migration plan should inventory the images and their landing-page context separately from the HTML pages. This guide describes the checks without promising that visibility will remain constant after a change.
Identify which assets matter
Collect image URLs used in published pages, important direct references, and available search-performance evidence. Separate original assets, generated sizes, decorative images, product images, and downloadable media. Their roles differ.
A large count of files is not a useful migration plan by itself. Record where each important image appears, what it depicts, and which page should provide the surrounding explanation. Keep rights and usage permissions attached to the asset where relevant.
Do not assume that every old size can be deleted because the new layout uses fewer variants. Some addresses may still be referenced outside the current template. Review the evidence before removing them.
Preserve identity where practical
If an image’s role and content remain the same, unnecessary URL changes add migration work. When addresses must change, map important old resources to suitable replacements and verify the result directly.
A replacement should be genuinely related to the old asset. Redirecting every image to one generic portrait or logo does not preserve the user’s expected content. If an asset has no replacement, handle its removal honestly rather than pretending equivalence.
Check the final content type and image response, not only the status code. A successful response containing an HTML error page is not a working image.
Keep discovery and context intact
Google’s image guidance explains that standard HTML image elements support discovery, while CSS background images are not indexed in the same way. Moving an informative image into a purely decorative background can therefore change more than its visual placement.
Review the image’s surrounding text, useful alternative text, and landing-page relevance. Describe what the image contributes rather than filling alternative text with unrelated keywords. Decorative images and informative images have different accessibility roles.
Ensure responsive implementations retain a usable image source and appropriate sizing. A desktop screenshot is insufficient if the mobile variant is broken or crops away the information the image is meant to communicate.
Treat optimization as a controlled change
Compression, format conversion, resizing, and cropping can improve delivery but may remove essential detail. Product dimensions, texture, labels, or comparison information should remain legible where they matter to the buying decision.
Use representative assets for visual review: photographs, text-heavy graphics, diagrams, and transparent images. One compression setting may not suit all of them. Check the rendered result at actual display sizes rather than only comparing file sizes.
Retain a suitable original source for future generation without exposing private working files in the public site. The public build should contain intended assets, not every draft in the production folder.
Validate the media and page together
For each important image, confirm the final URL, successful image response, rendered placement, and relevant landing page. Check direct old-image requests where preservation or redirection was intended.
An image sitemap can be useful for discovery in appropriate cases; Google’s image-sitemap documentation describes the supported structure. A sitemap does not compensate for a broken asset or guarantee indexing.
Also inspect product feeds and structured data if they reference the changed image addresses. The website can look correct while another channel continues using an obsolete URL.
Monitor the right scope after launch
Separate image-search observations from ordinary web-search traffic where the reporting allows it. Review important landing pages and asset groups, accounting for reporting delays and other concurrent changes.
If a decline appears, investigate accessibility of the image, the URL mapping, page context, and indexing signals before replacing the entire media strategy. Search visibility can fluctuate for reasons beyond the migration, so preserve evidence and avoid attributing every movement to one change.
For the broader URL plan, read commerce-blog migration. For finding missing page relationships after a rebuild, see internal-link gaps in a growing catalog.