Materials for comparing old and replacement images
Materials for comparing old and replacement images
In this guide
  1. Decide whether a new image address is necessary
  2. Find every relevant reference
  3. Verify delivery before switching references
  4. Example: moving a shared article photograph
  5. Distinguish delivery checks from search observations
  6. Use stable naming and a proportionate toolset

Decide whether a new image address is necessary

The deliverable maps old address, new address, referring pages, transition method and checks. If the only objective is smaller files or better quality, first establish whether the existing delivery method can be improved without changing the address. Frequent cosmetic renaming creates extra reference work.

When replacing the actual image, also check the depicted subject and its relationship to the text. If both location and content change, record those as separate decisions. A migration that preserves a photograph is different from replacing it with a different illustration, even when both operations result in a new URL.

Find every relevant reference

Inspect the actual implementation for references in article images, thumbnails, related cards, social previews, structured data, responsive sources, CSS and any image sitemap. You do not need to add systems the site does not use, but changing one visible image tag is not a complete audit.

Record dimensions, format, alternative text and surrounding explanation. When two languages share the same picture, review their alternative text and context separately. Shared image bytes do not establish that both pages explain the image correctly, and an address replacement should not silently remove useful text.

Verify delivery before switching references

Confirm that the new address is publicly retrievable and returns the intended image content and media type. Check for authentication pages, HTML errors and unexpectedly large downloads. Test the responsive variants the site actually serves.

Reserve layout space before the image arrives. Apply lazy loading appropriately to lower-page pictures rather than blindly delaying the main opening image. Keep the picture associated with relevant surrounding text and implemented in a discoverable form. A working URL in a developer’s signed-in browser is not enough to establish public image delivery.

Records to reconcile
Records to reconcile
CheckRecordAcceptance
MappingOld/new URLs and usesReferences traceable
DeliveryType, dimensions and variantsPublicly retrievable
ChecksLanguages, cards and bodyCorrect picture displayed
An index card recording image replacements
An index card recording image replacements

Example: moving a shared article photograph

In a fictional migration, image I-061 moves to a new host and is used by a Japanese article, an English article and a listing card. Add all three uses to the mapping. Test the large article picture and the smaller card version at their new locations.

After switching, open desktop and phone-width pages and inspect crop, aspect ratio and alternative text. Decide how to handle the old address after checking for remaining dependencies; do not automatically delete it as soon as the first visible article appears correct. Keep a rollback reference until acceptance.

Distinguish delivery checks from search observations

Rescan for remaining references to the old address. If redirects are part of the transition, verify that they lead to an appropriate image rather than an unrelated homepage. Keep the intended resource relationship intact.

Observe image-search performance separately from delivery acceptance, noting changes to the landing page and placement as well as the image address. A movement immediately after migration is not necessarily caused by the URL alone. Correct delivery does not guarantee image-search inclusion, and a delayed report is not proof that a technically verified file is unavailable.

Use stable naming and a proportionate toolset

Choose stable descriptive IDs for future assets rather than repeatedly renaming them. Avoid stuffing every filename with keywords; make the article relationship understandable and maintainable. A spreadsheet and current delivery checks may be enough without a new paid audit tool.

For a larger migration, use crawler output to find references and inspect important pages directly. Budget separately for bandwidth, storage, transformations and work time. Acceptance requires correct new delivery and page references, a deliberate policy for old dependencies and a known rollback route if an important placement fails.

Resources for the next step

Publishing and site improvement

Organise article planning, images, launch checks and refresh priorities as your publication grows.

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure