HTTP to HTTPS redirect
Checks if HTTP requests redirect properly to HTTPS.
¿Por qué importa esto?
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.
¿Cómo se soluciona?
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.
Este check puntúa de 0 a 100. Bajo 50 es un fallo, 50 a 89 un aviso, 90 o más es bueno. Tras cada crawl ve la nota por página en el informe, con una breve explicación.
Preguntas frecuentes
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.
Ejemplo
Copie el código de abajo y adapte el dominio, la marca y el contenido a su situación.
# 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]