What Does "Broken images" Mean?
Images of your site have an HTTP status code that is over 400, which means these images are likely not showing up on the page.
Why It's Important
Broken images will not be displayed on web pages, so the intended content will be missing which creates a poor user experience and confusion for site visitors. If there are a large number of broken images, it could signal to search engines that the site is not well-maintained and lead to worse rankings.
How To Fix
The method to fix each issue will depend on the HTTP status code for each broken image. Here are some of the most common ones:
404 (Not found): Take a look at the src attribute in the <img> tag in all places you're linking to this image. It's possible there was a typo or misspelling. If there's no mistake here, then check to make sure the image was not deleted, moved, or was never uploaded to the server to begin with. You'll want to move or upload the image to the exact location in the src attribute of all linking <img> tag, or change the src to the correct URL.
503 (Service unavailable): Check to see whether you can see the image. If it loads okay, it's possible the error was a temporary server issue and has been resolved. If you see many of these errors, the server could be limiting or blocking Dragon Metrics' crawler, Dragonbot. If so, you may want to consider adjusting your crawl speed in Dragon Metrics or talking to your server administrator.
401 (Unauthorized): Ensure this image should be available to all users without logging in. If it should be available, you'll have to modify your web server's settings or application code to allow unauthenticated users to access this image. If this is an image only available to logged-in users, consider excluding these pages using the robots.txt file.
403 (Forbidden): Ensure that the URL is referring to is an actual image file and not a directory listing. This is the most common cause of 403 errors. If the URL is a directory listing, you'll want to change any links pointing to this URL or create a 301 permanent redirect to a new URL. In some cases, your web server might be blocking or not accepting requests from Dragonbot, and the server could return a 403. If this is the case, you will have to modify your server settings to allow requests from Dragonbot.
500 (Internal server error): Since this is a general error code there could be many causes, such as errors in server configuration, file permissions, server timeouts, or others. Consider talking to your server administrator to resolve this issue.