HTTPS, certificates, mixed content and security headers. Browsers warn visitors about insecure pages, and search engines prefer secure sites.
SmooxSEO runs 18 security checks on every page of your site:
The site, or its key pages, can drop out of Google or can't be reached. Fix it first.
Browsers show a full-page warning instead of your site, and Google can't crawl it securely.
A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.
The certificate expires in under 14 days. When it does, browsers will block the site.
The form's action is an http:// address, so data leaves unencrypted even from an HTTPS page.
The http:// address still loads the site instead of sending visitors to https://, so two copies of the site exist and some visitors browse unencrypted.
These pages load without encryption. Browsers mark them "Not secure" and Google prefers HTTPS.
The page still ranks, but less well, or a real opportunity is lost. Fix it when you can.
The certificate is valid, but the server doesn't send the intermediate certificate with it. Most browsers fetch it themselves, but other software (apps, scripts, some phones, tools that read your site) refuses the connection.
Anything visitors type into this form (names, emails, passwords) travels unencrypted.
This HTTPS page loads images, scripts, styles or frames over http://. Browsers block some of them and show a warning.
Good practice with a small effect, or something that is often intentional. Nice to have.
Without Strict-Transport-Security, browsers may still try http:// first, which an attacker on the network can intercept.
Links to the http:// version of your own pages cost a redirect and can send visitors to the insecure version.
No list of allowed script and style sources, so injected scripts run freely.
Full page addresses, including any private details in them, can leak to the sites you link to.
Browsers may guess file types, which attackers can abuse.
Other sites can show your pages inside a frame to trick visitors into clicking (clickjacking).
The server still accepts TLS 1.0 or 1.1, outdated encryption that browsers no longer trust.
Addresses starting with // load over HTTP when the page is HTTP, and are a known source of mixed content.
Links that open another site in a new tab (target="_blank") without rel="noopener". Old browsers let that site control your tab.
The server labels a file as the wrong type (or not at all), so browsers and Google may handle it wrongly.