[Bill Posters]

RewriteEngine on

RewriteCond %{HTTP_HOST} ^example.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.example.com$
RewriteRule ^(.*)$ http://www.example.co.uk [R=301,L]

(via CPanel add-on domain redirect)

Redirect 301 / http://www.example.co.uk

(via manually editing the htaccess file)

…the significant difference being…?

TIA

[Mr Fred]

not sure but some good stuff here

http://www.webmasterworld.com/forum23/1600.htm

webmaster haha - they were the days!

according to that and a few other things one way google likes and the other it doesnt - but i am not sure which.

very helpful i hear you say!

[oli]

not arf
I use one on here, 2nd example i think.

[Bill Posters]

I definately know that the simple Redirect 301 method is the one recommended to keep Google sweet, so I guess I'll steer clear of using CPanel's method.

Cheers Mik.

[oli]

redirect 301 /index.html http://www.designerstalk.com/forums - what dt is using

[Bill Posters]

fwiw™, the index.html part is redundant.
/ is effectively identical to /index.html
Both refer to the default root page.
-

After a little look it appears that the CPanel/longer method works by rewriting the url rather than simply redirecting.
Redirect 301 only works for those users typing in the root/basic domain name with the alternative TLD.


e.g. you want to redirect yourdomain.com (your mop-up TLD) to yourdomain.co.uk (your true site directory)

Those attempting to visit yourdomain.com/page.php will get an error when a Redirect 301 is in use.
The longer method simply surplants the yourdomain.com portion with yourdomain.co.uk which should resolve to an existing page/directory (yourdomain.co.uk/page.php).

So, each has their benefits over the other.
Which one you choose depends on your needs and what urls you expect visitors to arrive on.

[imagn]

Definitely want to submit the changes to Google via sitemap.xml file as well