What does it mean if you internally rewrite a URL and put [R=301] at the end of it? Does it make any sense since you are not forcing an external 'http://' call so what is the meaning of a redirection in that case?
I have an old site domain that has to be redirected to a new domain name on a NEW server, but I also have the option to move the old domain to the new server and do an internal redirect.
scorpion Hopefully I'm not to far off base here? I'm assuming the comparison you present between internal (server side-htaccess) and external (html page based) is what your looking for.
The SE's will automatically pick up on the internal/server side redirects.
Html redirects are not a good idea. Especially to SE's. There use to be a rule of thumb acceptable to SE's of 10 second dealys before the redirect. Although I tried this initally before beginning with htaccess, I don't reall the SE impact.
Case 1 is not "correct usage according to the book." If I get some time, I'll test it using the Server Headers checker [webmasterworld.com] and post.
Case 2 is an external rewrite, visible to search engines.
Case 3 is an external rewrite as above, but using mod_alias.
Either way you go with your two domains, it's a good idea to use a 301. Otherwise, you run the risk of problems due to duplicate content on multiple domains, and search engines getting confused as to which of the two domains gets listed or which pages get the PR.
i'm having all sorts of problems with google indexing both www.mysite.com and mysite.com. i recently converted my site from static to dynamic and have used mod rewrite, i suspect that maybe i have brought this problem on myself.
is there a way of forcong a rewrite from mysite.com to www.mysite.com?