HTTPS is a ranking signal
Google confirmed HTTPS as a lightweight ranking signal. More importantly, browsers warn visitors on unencrypted pages, which damages trust before a visitor even reads the content.
Paste a URL and check whether it loads over HTTPS, whether the http:// version redirects correctly, and whether any mixed content resources are slipping through on an insecure connection.
Run a check to see the HTTPS and mixed content signals for this page.
This tool fetches the URL you submit and checks the HTML it receives. It can detect whether the final response is served over HTTPS, whether the http:// version redirects, whether HSTS is present, and whether image, script, iframe, or form URLs in the HTML source are insecure. It cannot detect mixed content that JavaScript adds after the page loads, resources referenced only in CSS files, or issues on pages it does not visit.
Google confirmed HTTPS as a lightweight ranking signal. More importantly, browsers warn visitors on unencrypted pages, which damages trust before a visitor even reads the content.
Scripts, stylesheets, iframes, and form actions loaded over http:// on an https:// page are blocked by modern browsers. This can silently break features visitors depend on.
Images and media loaded over http:// may still load in some browsers, but the padlock icon disappears and some browsers display a security warning to the visitor.
Mixed content is when an https:// page loads resources like images, scripts, or stylesheets over http://. Browsers block or warn on mixed content, which can break pages and reduce visitor trust. Google uses HTTPS as a ranking signal, so insecure resources on an otherwise secure page can still create issues.
Active mixed content includes scripts, stylesheets, iframes, and form actions. Modern browsers block these automatically because they can alter the page. Passive mixed content includes images, video, and audio. Browsers may load these but display a warning or change the security indicator.
No. The tool checks one URL at a time. It scans the HTML of the page you submit, but it does not crawl subpages, check CSS files for background image URLs, or detect mixed content loaded dynamically by JavaScript after the page renders.