Broken Images and SEO: Why They Matter and How to Fix Them
Broken images are image elements on your pages that return a 404 or other error response — displaying as empty boxes or broken icon placeholders to visitors. They hurt user experience, signal poor site maintenance to Google's quality evaluators, waste crawl budget on non-existent resources, and eliminate any SEO value the image could have contributed. Regular audits for broken images are an essential part of site hygiene for any SEO programme.
How Broken Images Affect SEO
Google's quality raters assess page quality in part by examining whether a page appears well-maintained and professional. Pages full of broken image placeholders signal the opposite. While Google does not assign a direct ranking penalty for a single broken image, a pattern of broken resources across many pages contributes to a lower overall quality assessment. Additionally, each broken image request wastes a small portion of your crawl budget on a dead end, which adds up significantly on image-heavy sites.
Common Causes of Broken Images
Broken images occur for predictable reasons: files deleted from the server without updating pages that reference them, images moved to a different folder path during a site migration, CDN configuration changes that alter image URLs, case-sensitivity differences between local development (case-insensitive) and production servers (case-sensitive Linux), images uploaded to an old domain that no longer resolves, and third-party hosted images removed or blocked by the source domain.
Broken Images and Google Image Search
When Google attempts to crawl an image URL and receives a 404 response, the image is removed from Google Images. If those images were driving referral traffic — particularly relevant for e-commerce product images, recipes, infographics, and editorial photography — fixing broken images or redirecting old URLs to new ones can recover lost image search traffic. Images that have existing backlinks pointing to the old URL are especially important to redirect rather than simply delete.
How to Find Broken Images
A site crawler like SitemapFixer checks every <img src> URL across all your pages and reports which return non-200 HTTP status codes. This is more reliable than manual checking, which is impractical for sites with more than a few dozen pages. Google Search Console's Coverage report may also surface image crawl errors under "Not found (404)." Browser developer tools can confirm broken images on individual pages: open the Network tab, filter by "Img," and look for red (error) rows.
Fixing Broken Images: The Right Approach
The fix depends on the cause. If the image was moved, update the src URL on every page referencing it, or set up a server-side 301 redirect from the old URL to the new one. If the image was deleted intentionally, remove the <img> tag from the page or replace it with an appropriate substitute. If the image still exists but the path is wrong due to a migration, a bulk find-and-replace on the URL pattern in your CMS database is the most efficient resolution method.
Broken Images After Site Migrations
Site migrations are the most common cause of large-scale broken image problems. Moving from HTTP to HTTPS, changing domains, restructuring folder paths, or switching CDN providers can invalidate thousands of image URLs simultaneously. Before any migration, crawl all image URLs and document them. After migration, run a full crawl again and compare. Use a server-level redirect map for image paths that changed, and update hardcoded URLs in your CMS database using search-and-replace tools like WP-CLI for WordPress.
Preventing Broken Images Going Forward
Prevention is more cost-effective than fixing after the fact. Implement monitoring: schedule weekly crawls to check for newly broken images before they accumulate. Set up server-side 404 alerting for image requests. When deleting images from your media library, run a check for pages that reference the file before deletion. Use relative paths for internal images rather than absolute URLs where possible, so domain changes do not break image references. A CDN with a fallback source can also prevent broken images when origin files are temporarily unavailable.
Broken Images vs. Slow-Loading Images
Broken images (404 errors) and slow-loading images (performance issues) are distinct problems with different fixes. Broken images need URL corrections or redirects; slow images need compression, format optimisation (WebP, AVIF), lazy loading, and proper sizing. Both hurt user experience and both are detected in site audits, but they require different remediation workflows. Address broken images first — they are categorically more damaging than slow ones — then prioritise performance optimisation for the images that remain.