HTTP to HTTPS redirect
Checks if HTTP requests redirect properly to HTTPS.
Pourquoi est-ce important ?
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.
Comment le corriger ?
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.
Ce check note de 0 à 100. Sous 50 c’est un échec, 50 à 89 un avertissement, 90 ou plus c’est bon. Après chaque crawl vous voyez la note par page dans le rapport, avec une courte explication.
Questions fréquentes
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.
Exemple
Copiez le code ci-dessous et adaptez le nom de domaine, la marque et le contenu à votre 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]