Audit stale product images

Before you start

The one tip: align every image signal

1. Record what Google is showing now. Search Google for the product name plus your domain, then check Google Images with site:yourdomain.com product name. Save the visible thumbnail URL or a screenshot. The point is to document the mismatch before you touch metadata.
2. Make Product schema point to the current image. On product pages, the image field in Product structured data should contain the current product photo URL. Google says Product structured data can make product information eligible for Google Search results, Google Images, Google Lens, Shopping, and related merchant experiences. 4 Use one clean, crawlable image first; add alternates only after the primary photo is correct.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Widget",
  "image": [
    "https://example.com/images/example-widget-current-front.webp"
  ]
}
</script>

3. Set og:image to the same preferred image. Google lists og:image as one of the metadata sources that can influence preview selection, and the Open Graph Protocol defines og:image as the image URL that should represent the object on the page. 35 If your CMS has a social image field, check that it did not keep an old launch screenshot after the product UI changed.

<meta property="og:image" content="https://example.com/images/example-widget-current-front.webp">
<meta property="og:image:alt" content="Example Widget current dashboard screen">

4. Use primaryImageOfPage when the page is not a pure product page. For a homepage, category page, template gallery, or blog post that keeps showing the wrong thumbnail, add primaryImageOfPage to the WebPage schema and point it at the one image you actually want Google to consider primary. Google names primaryImageOfPage as a supported way to provide a preferred image for a page. 3

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "url": "https://example.com/templates/invoice-generator",
  "primaryImageOfPage": "https://example.com/images/invoice-generator-current.webp"
}
</script>

5. Use an image sitemap only when discovery is the problem. Google says image sitemaps help it find images it might not otherwise discover, including images reached through JavaScript, and image sitemaps can include images hosted on another domain such as a CDN. 6 If your image already appears in Search but Google chooses the wrong one, a sitemap alone is unlikely to solve the selection problem. Fix the page-level signals first.
6. Do not use robots directives as a thumbnail picker. max-image-preview controls the maximum preview size Google may show, and noimageindex can prevent images on a page from being indexed. 7 Those directives are useful for display control or blocking, but they do not tell Google which product image to choose.
7. Publish the change and request a fresh crawl. After the metadata is live, inspect the changed URL in Search Console and request indexing. Keep the old screenshot in your sheet so you can compare the visible thumbnail after Google revisits the page.

What to do if the image still stays wrong

• The preferred image URL returns a normal successful response in the browser.
• The same preferred image URL appears in Product schema, og:image, and primaryImageOfPage where those fields apply.
• The old image URL is not still present in page templates, CMS social fields, product feed fields, or archived variant data.

How to verify the audit

• The current product image URL.
• The image URL in Product structured data.
• The image URL in og:image.
• The primaryImageOfPage value, if the page uses WebPage schema.
• Whether the image is discoverable through the page HTML or image sitemap.
• The screenshot or note showing what Google displayed before the change.