Générez du code de redirection 301 pour les fichiers .htaccess. Redirigez de www vers non-www ou de non-www vers www de votre domaine instantanément.
Créez du code de redirection 301 de www vers non-www ou non-www vers www pour Htaccess avec Indexpro. Suivez les 3 étapes et cliquez sur le bouton « Obtenir le Code .htaccess ».
N'incluez pas www. Nom de domaine uniquement - ex. votredomaine.com
Une redirection .htaccess est une directive de configuration serveur qui envoie automatiquement les visiteurs d'une URL à une autre. Le fichier .htaccess est un puissant fichier de configuration utilisé sur les serveurs web Apache.
Une redirection 301 est une redirection permanente qui indique aux moteurs de recherche que la page a définitivement déménagé. C'est le type de redirection le plus favorable au SEO car il transmet environ 90-99% de l'équité des liens.
La redirection de www vers non-www (ou vice-versa) est particulièrement importante pour le SEO car les moteurs de recherche traitent www.example.com et example.com comme deux sites différents.
La mise en place de redirections .htaccess appropriées offre de nombreux avantages :
Four rules cover the great majority of real redirect work. Each goes in the .htaccess file at your document root, inside an IfModule mod_rewrite.c block with RewriteEngine On above it.
Sends every http request to the https version of the same URL, preserving the path.
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]Picks one canonical host so the same page is not reachable at two addresses.
RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]For a page that moved. Point it at the closest equivalent, not the homepage.
Redirect 301 /old-page https://www.example.com/new-pageMoves a folder and everything under it, keeping the rest of the path intact.
RewriteRule ^old-folder/(.*)$ /new-folder/$1 [L,R=301]A 301 is permanent and tells Google to move the ranking signals to the new URL. A 302 is temporary and tells Google to keep the old one. Use 301 for anything that has genuinely moved. Using 302 by mistake is one of the most common ways sites lose rankings during a migration.
A 301 passes the great majority of it. What costs you is chaining: every extra hop adds latency and risk, and long chains can be abandoned by crawlers. Point the old URL at the final destination directly.
In the document root of your site, usually alongside the homepage file. Rules in a subdirectory's .htaccess apply only to that directory and below.
No. It is an Apache feature. Nginx uses its own configuration syntax and ignores .htaccess entirely, so rules pasted there will silently do nothing.
Almost always a rule that matches its own destination, so the redirect fires again on arrival. Adding a condition that excludes the target URL, such as a RewriteCond checking the host or path, breaks the cycle.
Only if there is genuinely no closer match. Google treats mass redirects to the homepage as soft 404s, which means the old URL gets dropped anyway. A relevant page or a clean 410 is usually better.