📝 WordPress: Fix Featured Images Vanishing After a CDN Migration
WordPress stores an attachment’s URL in post content and in its standard attachment metadata at upload time, pointing at whatever domain was configured then. Migrating media to a CDN by running a URL search-and-replace across the database typically covers wp_posts content and the normal attachment sizes array – but a featured image’s URL is often cached separately inside a theme or page builder’s own meta key, calculated once and stored rather than looked up fresh each time. A generic search-and-replace that never touches that field leaves featured images resolving to the old origin domain, which the CDN config has since stopped proxying, while every image inside normal post content updates fine.
🔎 The Problem
wp_posts.post_content -> updated by the search-replace (CDN domain)
_wp_attachment_metadata (sizes) -> updated by the search-replace
Theme's own cached featured-image URL meta key (e.g. a builder-specific
cache field) -> NOT touched by a generic search-replace
-> featured image keeps resolving to old-origin-domain.com/wp-content/...
which the CDN no longer proxies -> broken thumbnail, content images fine
✅ Fix: Find Every Place That Cached the Old URL, Not Just the Content
- Search the database specifically for the theme or plugin’s own cached featured-image URL meta key, not just
wp_postsand the standard attachment metadata, when running a search-and-replace after a CDN migration. - Regenerate thumbnails after the migration (via a plugin or the WP-CLI media regenerate command) so any size-specific cached URLs rebuild against the new CDN domain instead of carrying the old one forward.
- Purge both the CDN’s edge cache and any WordPress page cache for templates that render the featured image, since a stale cached HTML page can keep embedding the broken URL even after the database itself is fixed.
🚨 Why This Is Dangerous
- A search-and-replace that only touches
wp_postsand leaves a theme’s separately cached featured-image field untouched can look fully successful in testing while every post’s thumbnail silently 404s on the front end.
A URL migration is only finished once you’ve found every place that cached the old one, not just where the content itself lives.
