Image SEO After a Site Migration: What to Check

Why image assets fail during site migrations

A comprehensive site migration—such as moving from WordPress to Next.js, switching from an on-premise media server to an Amazon S3/Cloudfront CDN, or restructuring subdomains—fundamentally alters how and where media files are stored.

When HTML pages migrate, developers map `/about-us` to `/about`. But what happens to `/wp-content/uploads/2024/05/enterprise-architecture-diagram.png`?

In many migrations, the new CMS uses a completely different file hashing system, storing the same asset at `https://cdn.yoursite.com/media/assets/hash_928174a.webp`. If the legacy URL is simply abandoned without a permanent 301 redirect:

1. Google Images traffic crashes: Search engines index specific image URLs. When those URLs return 404 Not Found, Google purges them from the visual search index.
2. Third-party backlinks break: Industry publications, partner blogs, and educational resources that hotlinked your original infographics now display broken image icons, severing referral traffic.
3. Internal rendering failures: If database content references older relative paths (e.g., ``), newly deployed pages render with broken image placeholders across your entire blog archive.

Executing an image SEO migration audit protects both user-facing visual integrity and valuable organic search visibility.

The Image Migration Architecture: Preserving asset equity

To safeguard your media library during and after a platform transition, establish an explicit mapping architecture between legacy image endpoints and modern CDN destinations.

A resilient image migration follows a three-stage preservation pipeline:

1. Legacy Media Mapping: Document all legacy paths (such as `/wp-content/uploads/`) and historical URLs generating search impressions.
2. Permanent Edge 301 Redirects: Configure server-level 301 redirects routing each legacy image path directly to its new CDN endpoint in a single hop.
3. XML Image Sitemap Ingestion: Submit updated image sitemaps containing modern canonical URLs to expedite search engine re-crawling and re-indexing.

Seven-step post-migration image SEO audit workflow

Step 1: Audit HTTP status codes of legacy image URLs

Before migration, extract the top 100 most-trafficked image URLs from your historical Google Search Console performance data (filtered by Search Type: Image) and server access logs.

Immediately following DNS cutover, test these legacy URLs:

• Do they return an exact `301 Moved Permanently` status code?
• Do they resolve directly to the new media asset without passing through multiple redirect chains?
• Do any legacy URLs return `404 Not Found`, `403 Forbidden`, or `500 Server Error`?

Use the Redirect Chain Checker to verify that image redirects resolve in a single hop.

Step 2: Scan for mixed content and SSL protocol mismatches

If your migration involved transitioning an older HTTP website to full HTTPS, or moving images to an external cloud storage bucket, mixed content errors frequently occur.

If your secure page (`https://yourdomain.com/product`) loads an image asset over unencrypted HTTP (`http://legacy.yourdomain.com/image.png`), modern browsers will block the image completely or display security warnings in the address bar.

Inspect your migrated pages using the Image SEO Audit Tool to verify that 100% of embedded image URLs utilize secure HTTPS protocols.

Step 3: Verify Cross-Origin Resource Sharing (CORS) headers

When moving images to a separate subdomain (e.g., `images.yourdomain.com`) or an external CDN (e.g., `assets-cdn.com`), browsers enforce strict Cross-Origin Resource Sharing (CORS) rules.

If your new image server lacks proper CORS headers:

• SVG icons and vector illustrations will fail to render inside modern browsers.
• HTML5 `` elements and WebGL product demos will throw security exceptions.
• Web fonts embedded within SVG diagrams will be blocked.

Verify that your CDN responds with:

http
Access-Control-Allow-Origin: https://yourdomain.com
Access-Control-Allow-Methods: GET, HEAD

Step 4: Audit responsive image markup and template rendering

A new CMS theme often introduces new image rendering components. Verify that the new templates do not introduce regressions:

• Confirm that `srcset` attributes point to active, reachable image resolutions rather than non-existent thumbnails.
• Check that explicit `width` and `height` dimensions are present on all image wrappers to prevent Cumulative Layout Shift (CLS).
• Verify that `alt` attributes were successfully migrated from the legacy database. In many CMS migrations, image alt text stored in separate metadata tables fails to export, leaving thousands of migrated images with blank alt attributes.

Step 5: Update and submit XML image sitemaps

Search engines do not actively re-crawl millions of historical image files daily without a prompt. To alert Googlebot to your new media architecture, compile and submit a dedicated XML image sitemap.

Your image sitemap should specify the canonical page URL alongside its primary visual assets:

xml


  
    https://yourdomain.com/features/analytics
    
      https://cdn.yourdomain.com/images/features/analytics-dashboard.webp
      Real-time analytics dashboard interface
      Interactive user cohort retention analysis screen
    
  

Step 6: Verify Open Graph and social preview persistence

When pages migrate, social sharing cards frequently break if the CMS fails to populate `og:image` tags with absolute URLs.

Inspect migrated URLs:

• Does `og:image` contain an absolute HTTPS URL (e.g., `https://cdn.yourdomain.com/...`) rather than a relative path (e.g., `/images/og.png`)?
• Does the social image asset return an HTTP 200 status code to external bot crawlers like Twitterbot and LinkedInBot?
• Is the image at least 1200x630 pixels to guarantee high-resolution card rendering on social feeds?

Step 7: Monitor Google Search Console Image Search performance

Following migration, filter your Google Search Console performance report by Search Type: Image:

• Expected trend: A brief 10% to 15% dip during the first two weeks as Google processes 301 redirects, followed by stabilization at pre-migration levels.
• Crisis trend: A 50%+ collapse in image impressions sustained over 30 days indicates broken redirect mappings, widespread 404s, or robots.txt blocks on your new image CDN.

Post-migration image decision framework

Case study: diagnosing an 80% Google Images traffic collapse

A high-growth B2B fintech company completed a complete website migration, moving from an older self-hosted CMS to a modern serverless deployment. Within 6 weeks of launch, visual organic traffic from Google Images dropped by 82%.

The Diagnostic Audit: The team deployed the Image SEO Audit Tool and audited legacy server logs, discovering three critical failures:

1. Broken image paths: The previous platform stored images at `/uploads/year/month/file.png`. The new platform uploaded images to an AWS S3 bucket using unique hash filenames (`/s3/bucket/9f8a7c2b.png`) without configuring redirects for legacy URLs. Over 1,400 indexed images returned 404 errors to Googlebot.
2. CDN Robots Block: The AWS S3 bucket included a default `robots.txt` file configured with `User-agent: * Disallow: /`, preventing Google from crawling any asset hosted on the cloud domain.
3. Missing sitemaps: No XML image sitemap had been generated for the new deployment.

The Solution:

• The engineering team built a script mapping all 1,400 legacy image paths to their corresponding S3 bucket URLs and deployed permanent 301 redirects at the server edge.
• They updated the S3 CDN configuration to allow search crawler access.
• They generated and submitted a clean XML image sitemap containing all new asset URLs.

The Outcome: Within four weeks of Googlebot re-crawling the 301 redirect paths, Google Images impressions rebounded to 95% of pre-migration levels and reached all-time highs within three months due to faster WebP delivery.

Migration image SEO checklist

• [ ] Complete inventory of top-trafficked legacy image URLs compiled before migration.
• [ ] 1-to-1 or pattern-based permanent 301 redirects configured for all legacy media paths.
• [ ] 100% of image URLs resolve over secure HTTPS without mixed-content warnings.
• [ ] Image CDN and cloud storage buckets return valid CORS access headers.
• [ ] New CMS templates declare explicit aspect ratio `width` and `height` dimensions.
• [ ] Alt text attributes successfully migrated from legacy database records.
• [ ] Image CDN `robots.txt` verified to ensure search engine crawlers are not blocked.
• [ ] XML image sitemap compiled, validated, and submitted to Google Search Console.
• [ ] Open Graph social preview images return HTTP 200 with absolute CDN paths.
• [ ] Google Search Console Image Search impressions tracked weekly post-migration.

Frequently asked questions

How long does it take Google to process 301 redirects on image files?

Can we use a single wildcard redirect for all legacy images to our home page?

Do we need a separate XML sitemap just for images?

Next steps

Verifying your image assets after a site migration protects hard-won organic rankings and visual search traffic. Use AltHunt's Image SEO Audit Tool to audit your migrated pages for broken media links and missing attributes.

To ensure your broader migration avoids technical traps, explore our guide to on-page SEO audits after redesign, check your server headers with the Redirect Chain Checker, or publish your alternative page for free on Alt Hunt.