HTTP to HTTPS redirect
Checks if HTTP requests redirect properly to HTTPS.
Why does this matter?
Without a redirect, visitors and search engines can access your site via HTTP, leading to duplicate content and split link value. Google counts both versions as separate URLs.
How to fix it?
Add a server-side 301 redirect from http:// to https://. In Apache do this in .htaccess; in Nginx in the server block. Also make sure www and non-www are consistent.
This check scores from 0 to 100. Below 50 is a fail, 50 to 89 is a warning, 90 or above is good. After each crawl you see the score per page in your report, with a short note on what we found.
Frequently asked questions
Checks if HTTP requests redirect properly to HTTPS.
Without a redirect, visitors and search engines can access your site via HTTP, leading to duplicate content and split link value. Google counts both versions as separate URLs.
Add a server-side 301 redirect from http:// to https://. In Apache do this in .htaccess; in Nginx in the server block. Also make sure www and non-www are consistent.
Example
Copy the code below and adapt the domain name, brand name and content to your situation.
# Nginx: HTTP → HTTPS redirect (301 permanent)
server {
listen 80;
server_name yourdomain.com www.yourdomain.com;
return 301 https://www.yourdomain.com$request_uri;
}
# Apache .htaccess
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]