Path Redirect is definitely the way to go, and more maintainable in the long run. Google's index is sensitive to redirects so it should try to retain rankings for 301 redirects, which Path Redirect provides.
On Tue, Jan 11, 2011 at 4:36 PM, Steve Kessler skessler@denverdataman.comwrote:
That fact that the paths have .shtml does not impact anything. We have done this before with .html paths without a problem. You can do this very well with path_redirect.
Another way to solve this without grunt work is to import the path into a CCK field and then use pathauto to build the path on import. You can then, after the import, change the path back and use Views Bulk Operations to make the paths the way you want them on Drupal.
Make sure that you have path redirect perserve paths when you update.
-Steve
On Tue, Jan 11, 2011 at 3:11 PM, Shai Gluskin shai@content2zero.comwrote:
Hi Folks,
A site I'm taking over has had content migrated from another CMS. The old URLs are important and need to be preserved. There is an admin assistant available to do the grunt work.
My question: Which method is better from an SEO perspective (is there an another perspective???, if so do share):
- Drupal core's path module; paste in the old urls as the path alias
- use http://drupal.org/project/path_redirect to redirect the old
paths to new ones created with the pathauto module.
I don't know if it makes a difference or not... but all the old paths end in "shtml".
Other suggestions?
The site is running 6.20 and clean URLs.
Thanks in advance,
Shai
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Steve Kessler Owner and Lead Consultant Denver DataMan, LLC 303-587-4428
-- [ Drupal support list | http://lists.drupal.org/ ]