Non-retrievable file sources

Learn what is checked in this report and how to fix any issues found

This report gives you an overview of embedded files on your website (e.g. images, CSS, and JavaScript files) that could not be retrieved from the server.

Why you should avoid unretrievable file sources:

If files can not be retrieved, this can have a serious impact on the user experience of your website. Nobody likes to browse a site where images won't load or the layout doesn't display correctly due to missing CSS files.

It is also important for Google to be able to access all of the relevant files so that the content of your pages can be fully and correctly indexed.

What the messages in the "Problem" column mean:

  • Request failed: When requesting this file, the Seobility crawler was unable to reach the server. You can get more information about the cause from the HTTP status code next to it (if available). You can find an overview of the meaning of different HTTP status codes here.
  • Timeout: The server was reached when the file was requested. However, it did not send a response within 10 seconds. Common cause: server performance issues.
  • SSL/TLS error: A problem has occurred during the SSL/TLS handshake.
  • Invalid URL scheme: The URL of the embedded file is incorrect.
  • Bot error (unknown): An unknown problem occurred while retrieving the file.

How to fix the most common problems:

A common cause of unretrievable files is poor server performance. This can lead to error messages such as "Request failed" or "Timeout". These errors often occur in combination with long page response times (see the "Slow response times" report). You can find tips for improving your server response times here.

Another common cause is that the Seobility Bot is blocked from accessing the files. This can lead to error messages such as "Request failed" or an HTTP status 403. In these cases, you need to make sure that the Seobility Bot is allowed to access your website. You can find an overview of Seobility's user agent and IP addresses here.

In the case of 404 errors and invalid URLs: correct or remove internal links that point to the wrong file URL (which cannot be retrieved). You can find these links by clicking on the URL in the list. This will allow you to see all the pages that contain the file in question.