A missing image can make a polished page feel abandoned. It may also remove useful context, create empty layout space, and send crawlers toward repeated errors. A WordPress broken image audit finds those failures systematically and fixes their cause instead of replacing only the most visible example.
Understand where image failures begin
Broken images can come from deleted media files, incorrect migrations, changed domains, mixed HTTP and HTTPS URLs, expired external sources, case-sensitive filenames, or generated sizes that no longer exist. Page-builder templates and custom fields can hold references that do not appear in the main editor.
Record the error pattern before changing content. A group of failures under one old domain suggests a different fix from a single file deleted by mistake.
Crawl public pages and image resources
Use a crawler that reports image URLs, source pages, response codes, and redirect chains. Cover posts, pages, category archives, templates, and important landing pages. Include lazy-loaded image attributes and CSS background images where the tool supports them.
Export the findings so each repair can be tracked. Sort by source-page traffic or business importance to handle the most visible problems first.
Check the Media Library and storage
For local URLs, confirm that the attachment exists in WordPress and that the physical file is present in the uploads directory or object storage. Verify the original file and the generated size requested by the page. A valid attachment record does not guarantee that every derivative image exists.
Do not delete unattached media during the audit. A file can be used by theme settings, reusable blocks, custom fields, or external campaigns without appearing as attached to a post.
Repair migrations and domain changes carefully
When failures share an old hostname or directory, use a structured search-and-replace process that understands serialized WordPress data. Test on staging, back up the database, and limit the replacement to the exact value that changed.
Avoid global text replacement in raw database exports. It can damage serialized settings and alter unrelated content that happens to contain the same text.
Choose restore, replace, or remove
Restore the original file when ownership, licensing, and quality are known. Replace it when the visual is outdated or unavailable, then update alt text and credit information. Remove the image and its empty container when it no longer supports the page.
Do not substitute an unrelated stock image merely to remove an error. The replacement should preserve the meaning and context of the surrounding content.
Review alt text and captions
A repair is a useful moment to check accessibility. Alt text should communicate the image’s purpose in the page context, while decorative images can use empty alt text. Captions and credits should remain accurate when the source changes.
Avoid stuffing target keywords into every alt attribute. Describe useful content naturally and do not repeat nearby text unnecessarily.
Clear caches and verify rendered pages
After repairs, regenerate image sizes when needed and clear page, hosting, and CDN caches. Test the final public URL in a logged-out browser. Check desktop and mobile because responsive markup may request different files at each width.
Inspect the browser network panel for remaining 404 responses and confirm that images do not create unexpected layout shifts.
Final WordPress broken image audit review
- Public pages and templates were crawled.
- Error patterns and source pages were documented.
- Local files and generated sizes were verified.
- Database replacements were tested on staging.
- Alt text, captions, and credits remain accurate.
- Caches were cleared and responsive pages were retested.
A thorough WordPress broken image audit protects credibility, accessibility, and page stability. Fix common causes in a controlled way, keep proof of media rights, and schedule a smaller recurring crawl so new failures are caught before visitors report them.