Security: HTTP URLs

HTTP URLs that are encountered in the crawl.

All websites should be secure over HTTPS today on the web. Not only is it important for security, but it’s now expected by users.

Chrome and other browsers display a ‘Not Secure’ message against any URLs that are HTTP, or have mixed content issues (where they load insecure resources on them).

How to Analyse in the SEO Spider

Use the ‘Security’ tab and ‘HTTP URLs’ filter to view these URLs.

To view how these URLs were discovered, view their ‘Inlinks’ in the lower window tab.

Export pages that link to HTTP URLs via ‘Bulk Export > Security > HTTP URLs Inlinks’.

What Triggers This Issue

This issue is triggered for any internal URL found in a crawl that is linked to using HTTP instead of HTTPS. This includes URLs discovered by any link types, such as hyperlinks, canonicals, hreflang and more.

For example, if the following URL:

https://www.screamingfrog.co.uk/

Linked to the following URL:

http://www.screamingfrog.co.uk/froggy/

It would be flagged for this issue.

How To Fix

All URLs should be secure HTTPS pages. Pages should be served over HTTPS, any internal links should be updated to HTTPS versions and HTTP URLs should 301 redirect to HTTPS versions.

HTTP URLs identified in this filter that are redirecting to HTTPS versions already should be updated to link to the correct HTTPS versions directly.