Re: Cost of redirect and site domain switch? Good Practice / Bad Practice / Terrible Practice
| From: | Tristan | Date: | Fri, 17 Aug 2012 20:01:32 +0000 |
| Subject: | Re: Cost of redirect and site domain switch? Good Practice / Bad Practice / Terrible Practice | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-318742@lists.php.net to get a copy of this message | ||
Jonathan,
Yeah that was my intention but, I think search engines will hit you for
duped content if you're running two domains same content. So, the idea was
to redirect 301 style and have an alias.
-T
On Fri, Aug 17, 2012 at 1:36 PM, Jonathan Sundquist <jsundquist@gmail.com>wrote:
> Depending on how long you have why not just do an alias? No redirect
> required.
>
>
> On Fri, Aug 17, 2012 at 2:35 PM, Tristan <sunnrunner@gmail.com> wrote:
>
>> So, I need to change from somedomain.com to somenewdomain.com
>>
>> I was thinking of doing this
>>
>> 1) create an alias to the site somenewdomain.com to point to current
>> server
>> 2) run permanent 301 redirect from somedomain.com to somenewdomain.com
>>
>>
>> I was thinking this was a clean safe way to do it so we dont have to run a
>> global find replace.
>>
>> Concerns might be but, I don't know for sure?
>>
>> 1) SEO
>> 2) processing / time / cost for the 301 redirect on any old
>> somedomain.comrequests
>>
>>
>> What do you guys think?
>>
>> Thanks, T
>>
>
>