changer d’URL

Comment changer de nom de domaine sans tout perdre de l’ancien domaine est une question qui revient sporadiquement de webmestre ou de gestionnaires Web allumés. Malheureusement pour eux, d’autres entreprises changent radicalement de plate-forme Web sans se poser de questions cruciales et pleurent par la suite, lorsqu’ils se rendent compte que d’un coup, tout le trafic qu’ils avaient est disparu.

Le porte-parole officieux de Google en ces matières, Matt Cutts, suggère de faire une page de redirection 301.

Now let’s talk for a minute about moving from mattcutts.com to someotherdomain.com. All other things being equal, I would recommend to stay with the original domain if possible. But if you need to move, the recommended way to do it is to put a 301 (permanent) redirect on every page on mattcutts.com to point to the corresponding page on someotherdomain.com. If you can map mattcutts.com/url1.html to someotherdomain.com/url1.html, that’s better than doing a redirect just to the root page (that is, from mattcutts.com/url1.html to someotherdomain.com). In the olden days, Googlebot would immediately follow a 301 redirect as soon as it found it. These days, I believe Googlebot sees the 301 and puts the destination url back in the queue, so it gets crawled a little later. I have heard some reports of people having issues with doing a 301 from olddomain.com to newdomain.com. I’m happy to hear those reports in the comments and I can pass them on to the crawl/indexing team, but we may be due to replace the code that handles that in the next couple months or so. If it’s really easy for you to wait a couple months or so, you may want to do that; it’s always easier to ask crawl/index folks to examine newer code than code that will be turned off in a while.

Mais 123howtoguide suggère plutôt de faire une page de redirection temporaire 302 et d’attendre que le PageRank et que le trafic soit revenu avant de définitivement rediriger avec la page 301.

After migrating the content from old site — with or without modification to the existing pages or content — then consider using 302 “temporarily moved” redirect instead of going directly with the 301 redirect.
A site returning 302 response will maintain its position in the search engines for the old domain. But when the visitor clicks on the page, it will still be redirected to the new domain.
This method solves the age filtering problem for new domains. If you have permanently redirected the old domain to the new domain, even with the same content and everything, chances are the culprit is that the age filter kicks in.
Using 302 lets you migrate the site gradually and gives you time to start a linking campaign for the new site.
After you notice the new domain starting to show up in the rankings — it may take months — then it is time to contact linking sites to let them know of the new site so they update their site accordingly.
Once the domain has been properly aged, the final move is of course to change the 302 temporary redirect to 301 permanent redirect. This will transfer the link popularity from the original site and finalize the move to the new domain.

Il rappelle aussi de créer un contenu original, optimisé avec de bons mots clés et surtout, nouveau afin de ne pas être pénalisé par les engins de recherches qui n’aiment vraiment pas les contenus dupliqués.

Il est aussi primordial de faire une sitemap et une page d’erreur 404 dans laquelle vous pourriez inclure de la pub pour vos produits et services.