Redirect chains
Detects redirect chains longer than 2 hops.
Pourquoi est-ce important ?
Redirect chains slow down load time (each hop adds 100-300ms) and dilute the passed link value. Google recommends limiting redirect chains to a maximum of 1 hop.
Comment le corriger ?
Analyze your redirects and combine multiple steps into one direct 301 redirect. Update internal links to the final destination. Avoid temporary 302 redirects for permanent moves.
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
Detects redirect chains longer than 2 hops.
Redirect chains slow down load time (each hop adds 100-300ms) and dilute the passed link value. Google recommends limiting redirect chains to a maximum of 1 hop.
Analyze your redirects and combine multiple steps into one direct 301 redirect. Update internal links to the final destination. Avoid temporary 302 redirects for permanent moves.
Exemple
Copiez le code ci-dessous et adaptez le nom de domaine, la marque et le contenu à votre situation.
# Direct 301 redirect (no chain) - 1 hop
# Nginx
location = /old-page/ {
return 301 https://www.yourdomain.com/new-page/;
}
# Apache .htaccess
Redirect 301 /old-page/ https://www.yourdomain.com/new-page/
# Also update internal links to point directly to the final URL
# Avoid: /a/ → /b/ → /c/ (chain of 3 = slow + PageRank loss)