Insecure content on HTTPS pages

This report lists pages that are transferred via HTTPS but contain insecure files (i.e. non-HTTPS content).

Why you should avoid non-HTTPS files:

If you do not use HTTPS for embedded files, visitors to your site will see a warning in their browser, even if the page itself uses HTTPS. Users will be confused and may be less likely to trust your site. In addition, the use of HTTPS is a ranking signal, so you should definitely fix these problems.

What the information in the list means:

In the "URL" column, you'll find a list of affected pages containing insecure files. You can also see which type of file is specifically affected (e.g. images, CSS or JavaScript) in the "Problems" column.

How to fix these problems:

Click on the 'Details' link to get an overview of all the media and files used on the page. Any files that are not transferred using HTTPS will have a "No HTTPS" label. Make sure that these files are transferred via HTTPS.

You can find instructions for migrating your site to HTTPS on our blog and on Google Search Central.