Re: [WebDNA] [OT] Google redirect or not

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111037
interpreted = N
texte = This is a multi-part message in MIME format. --------------090203040101020603040003 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dan is correct that Google does try to figure this stuff out because they know that most people don't understand the technical aspects. But if you let them figure it out you are also continuing to dilute your link building efforts, and you are leaving it to Google to identify your primary domain. All of my best results always seem to come from not letting Google do the thinking. It always seemed to me that you'll always rank better when you you just do what they recommend without them spending more CPU cycles to figure out what you should be doing. -Matt On 1/20/2014 1:28 PM, Dan Strong wrote: > Google's latest stance on it = dont sweat it, but let us know which > one is the "authority") > > Don't sweat it: > http://searchengineland.com/googles-matt-cutts-duplicate-content-wont-hurt-you-unless-it-is-spammy-167459 > Dupe content: https://support.google.com/webmasters/answer/66359 > Canonicalization: https://support.google.com/webmasters/answer/139066 > > As for redirects, WebDNA's [redirect] has always been hit and miss > depending on platform, so when SEO matters, I always use Apache > redirect, usually in .htaccess, but if there are a bunch then directly > in httpd.conf > > Redirect301/oldPage.htmlhttp://www.Domain.com/newPage.html > Redirect301http://www.OldDomain.comhttp://www.Domain.com/ > > etc. > > -Dan Strong > http://www.DanStrong.com > On 1/20/2014 10:16 AM, Psi Prime Inc, Matthew A Perosi wrote: >> Yes, you are diluting your domain authority by having multiple >> domains service the same content. There's even a potentially worse >> problem though... Depending on how many domain names you have, more >> than 2 or 3 maybe, Google will view your single website as multiple >> websites. This is known as duplicate content. >> >> Google knows not to penalize someone for the "duplicate" version of >> www.domain.com and simply domain.com, but when it comes to things like: >> >> www.domain1.com >> domain1.com >> www.domain2.com >> domain2.com >> www.domain3.com >> domain3.com >> www.domain4.com >> domain4.com >> www.domain5.com >> domain5.com >> >> then Google starts to get upset because this looks like 10 different >> websites. From their point of view, you've sold or syndicated your >> information, and it will work against you. >> >> Many of the sites I manage have 5 or more domain names we use for >> offline marketing. I use a few different methods to handle this. >> Normally, I would just use the domain forwarding feature with GoDaddy >> to 301 the alternate domain names to the primary domain names. But I >> also add extra Google Analytic UTM tracking codes so I know what >> domain the person used in the first place. >> >> However, for your situation, since you already have pages in the >> Google index, you should change your Apache configuration to test the >> domain name, and rewrite the URL to the primary domain name. That >> way you can still keep the pages and variables. You would want to >> make sure the Apache config uses a 301 to indicate the changed URLs. >> >> You could also build this feature into WebDNA using the [redirect] >> context, but you might run into issues depending on which version of >> WebDNA you are using because the [redirect] is a 302, not a 301. >> Using a 302 will not solve the duplicate content issue. >> >> Hope that helps, >> >> -Matthew Perosi >> >> On 1/20/2014 12:37 PM, Steve Craig wrote: >>> Hi >>> >>> Just looking for a bit of advice - I have a site that is available >>> via many different domains and at the moment there are no redirects >>> so if you arrive via domain1.com then every >>> page thereafter stays on that domain, likewise if you arrive as >>> domain2.com it stays there but all the content >>> is the same from the same CMS. >>> >>> My question is do you think I am wasting Google ranking by >>> effectively sharing out my hits across domains or do you think I >>> should redirect all requests to one of the domains? >>> >>> I read somewhere that I am weakening my position a bit because my >>> "popularity" is being shared out across multiple domains, it seemed >>> logical just wondered what everyones experiences were. >>> >>> If redirecting is the answer, what is the easiest way on an Apache >>> server, using WebDNA or using an Apache redirect? >>> >>> Thanks for any input. >>> >>> Cheers >>> ======================================== >>> Steve Craig - Forest Products (Leisure) Ltd >>> Tel +44 1330 860505 Mob +44 7778 007607 >>> ======================================== >>> http://forestlogcabins.com >>> Email: steve@forestlogcabins.com >>> Skype: s.craig - iChat: steve.craig >>> ======================================== >>> >>> >>> >>> >>> --------------------------------------------------------- This >>> message is sent to you because you are subscribed to the mailing >>> list . To unsubscribe, E-mail to: archives: >>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>> support@webdna.us >> >> >> -- >> Matthew A Perosi >> Corporate Consultant >> Mobile Marketing Expert >> Senior Web Developer >> SEO Analyst & Educator >> matt@psiprime.com >> >> Psi Prime, Inc. >> 323 Union Blvd. >> Totowa, NJ 07512 >> >> Direct: 888.872.0274 >> Fax: 888.488.5924 >> >> http://www.perosi.com >> --------------------------------------------------------- This >> message is sent to you because you are subscribed to the mailing list >> . To unsubscribe, E-mail to: archives: >> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >> support@webdna.us > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------090203040101020603040003 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Dan is correct that Google does try to figure this stuff out because they know that most people don't understand the technical aspects.

But if you let them figure it out you are also continuing to dilute your link building efforts, and you are leaving it to Google to identify your primary domain.

All of my best results always seem to come from not letting Google do the thinking. 

It always seemed to me that you'll always rank better when you you just do what they recommend without them spending more CPU cycles to figure out what you should be doing.

-Matt



On 1/20/2014 1:28 PM, Dan Strong wrote:
Google's latest stance on it = dont sweat it, but let us know which one is the "authority")

Don't sweat it: http://searchengineland.com/googles-matt-cutts-duplicate-content-wont-hurt-you-unless-it-is-spammy-167459
Dupe content: https://support.google.com/webmasters/answer/66359
Canonicalization: https://support.google.com/webmasters/answer/139066

As for redirects, WebDNA's [redirect] has always been hit and miss depending on platform, so when SEO matters, I always use Apache redirect, usually in .htaccess, but if there are a bunch then directly in httpd.conf

Redirect<space>301<space>/oldPage.html<space>http://www.Domain.com/newPage.html
Redirect<space>301<space>http://www.OldDomain.com<space>http://www.Domain.com/

etc.

-Dan Stronghttp://www.DanStrong.com
On 1/20/2014 10:16 AM, Psi Prime Inc, Matthew A Perosi wrote:
Yes, you are diluting your domain authority by having multiple domains service the same content.  There's even a potentially worse problem though... Depending on how many domain names you have, more than 2 or 3 maybe, Google will view your single website as multiple websites.  This is known as duplicate content. 

Google knows not to penalize someone for the "duplicate" version of www.domain.com and simply domain.com, but when it comes to things like:

www.domain1.com
domain1.com
www.domain2.com
domain2.com
www.domain3.com
domain3.com
www.domain4.com
domain4.com
www.domain5.com
domain5.com

then Google starts to get upset because this looks like 10 different websites.  From their point of view, you've sold or syndicated your information, and it will work against you.

Many of the sites I manage have 5 or more domain names we use for offline marketing.  I use a few different methods to handle this.  Normally, I would just use the domain forwarding feature with GoDaddy to 301 the alternate domain names to the primary domain names.  But I also add extra Google Analytic UTM tracking codes so I know what domain the person used in the first place.

However, for your situation, since you already have pages in the Google index, you should change your Apache configuration to test the domain name, and rewrite the URL to the primary domain name.  That way you can still keep the pages and variables.  You would want to make sure the Apache config uses a 301 to indicate the changed URLs.

You could also build this feature into WebDNA using the [redirect] context, but you might run into issues depending on which version of WebDNA you are using because the [redirect] is a 302, not a 301.  Using a 302 will not solve the duplicate content issue.

Hope that helps,

-Matthew Perosi

On 1/20/2014 12:37 PM, Steve Craig wrote:
Hi

Just looking for a bit of advice - I have a site that is available via many different domains and at the moment there are no redirects so if you arrive via domain1.com then every page thereafter stays on that domain, likewise if you arrive as domain2.com it stays there but all the content is the same from the same CMS.

My question is do you think I am wasting Google ranking by effectively sharing out my hits across domains or do you think I should redirect all requests to one of the domains?

I read somewhere that I am weakening my position a bit because my "popularity" is being shared out across multiple domains, it seemed logical just wondered what everyones experiences were.

If redirecting is the answer, what is the easiest way on an Apache server, using WebDNA or using an Apache redirect?

Thanks for any input.

Cheers
========================================
Steve Craig - Forest Products (Leisure) Ltd
Tel +44 1330 860505 Mob +44 7778 007607
========================================
http://forestlogcabins.com
Email: steve@forestlogcabins.com
Skype: s.craig - iChat: steve.craig
========================================




--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 


-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatormatt@psiprime.comPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 

-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatormatt@psiprime.comPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------090203040101020603040003-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [OT] Google redirect or not (Dan Strong 2014)
  2. Re: [WebDNA] [OT] Google redirect or not (Dan Strong 2014)
  3. Re: [WebDNA] [OT] Google redirect or not (Donovan Brooke 2014)
  4. Re: [WebDNA] [OT] Google redirect or not (Steve Craig 2014)
  5. Re: [WebDNA] [OT] Google redirect or not (matt@psiprime.com 2014)
  6. Re: [WebDNA] [OT] Google redirect or not (Steve Craig 2014)
  7. Re: [WebDNA] [OT] Google redirect or not (matt@psiprime.com 2014)
  8. Re: [WebDNA] [OT] Google redirect or not (Dan Strong 2014)
  9. Re: [WebDNA] [OT] Google redirect or not (Steve Craig 2014)
  10. Re: [WebDNA] [OT] Google redirect or not (matt@psiprime.com 2014)
  11. [WebDNA] [OT] Google redirect or not (Steve Craig 2014)
This is a multi-part message in MIME format. --------------090203040101020603040003 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dan is correct that Google does try to figure this stuff out because they know that most people don't understand the technical aspects. But if you let them figure it out you are also continuing to dilute your link building efforts, and you are leaving it to Google to identify your primary domain. All of my best results always seem to come from not letting Google do the thinking. It always seemed to me that you'll always rank better when you you just do what they recommend without them spending more CPU cycles to figure out what you should be doing. -Matt On 1/20/2014 1:28 PM, Dan Strong wrote: > Google's latest stance on it = dont sweat it, but let us know which > one is the "authority") > > Don't sweat it: > http://searchengineland.com/googles-matt-cutts-duplicate-content-wont-hurt-you-unless-it-is-spammy-167459 > Dupe content: https://support.google.com/webmasters/answer/66359 > Canonicalization: https://support.google.com/webmasters/answer/139066 > > As for redirects, WebDNA's [redirect] has always been hit and miss > depending on platform, so when SEO matters, I always use Apache > redirect, usually in .htaccess, but if there are a bunch then directly > in httpd.conf > > Redirect301/oldPage.htmlhttp://www.Domain.com/newPage.html > Redirect301http://www.OldDomain.comhttp://www.Domain.com/ > > etc. > > -Dan Strong > http://www.DanStrong.com > On 1/20/2014 10:16 AM, Psi Prime Inc, Matthew A Perosi wrote: >> Yes, you are diluting your domain authority by having multiple >> domains service the same content. There's even a potentially worse >> problem though... Depending on how many domain names you have, more >> than 2 or 3 maybe, Google will view your single website as multiple >> websites. This is known as duplicate content. >> >> Google knows not to penalize someone for the "duplicate" version of >> www.domain.com and simply domain.com, but when it comes to things like: >> >> www.domain1.com >> domain1.com >> www.domain2.com >> domain2.com >> www.domain3.com >> domain3.com >> www.domain4.com >> domain4.com >> www.domain5.com >> domain5.com >> >> then Google starts to get upset because this looks like 10 different >> websites. From their point of view, you've sold or syndicated your >> information, and it will work against you. >> >> Many of the sites I manage have 5 or more domain names we use for >> offline marketing. I use a few different methods to handle this. >> Normally, I would just use the domain forwarding feature with GoDaddy >> to 301 the alternate domain names to the primary domain names. But I >> also add extra Google Analytic UTM tracking codes so I know what >> domain the person used in the first place. >> >> However, for your situation, since you already have pages in the >> Google index, you should change your Apache configuration to test the >> domain name, and rewrite the URL to the primary domain name. That >> way you can still keep the pages and variables. You would want to >> make sure the Apache config uses a 301 to indicate the changed URLs. >> >> You could also build this feature into WebDNA using the [redirect] >> context, but you might run into issues depending on which version of >> WebDNA you are using because the [redirect] is a 302, not a 301. >> Using a 302 will not solve the duplicate content issue. >> >> Hope that helps, >> >> -Matthew Perosi >> >> On 1/20/2014 12:37 PM, Steve Craig wrote: >>> Hi >>> >>> Just looking for a bit of advice - I have a site that is available >>> via many different domains and at the moment there are no redirects >>> so if you arrive via domain1.com then every >>> page thereafter stays on that domain, likewise if you arrive as >>> domain2.com it stays there but all the content >>> is the same from the same CMS. >>> >>> My question is do you think I am wasting Google ranking by >>> effectively sharing out my hits across domains or do you think I >>> should redirect all requests to one of the domains? >>> >>> I read somewhere that I am weakening my position a bit because my >>> "popularity" is being shared out across multiple domains, it seemed >>> logical just wondered what everyones experiences were. >>> >>> If redirecting is the answer, what is the easiest way on an Apache >>> server, using WebDNA or using an Apache redirect? >>> >>> Thanks for any input. >>> >>> Cheers >>> ======================================== >>> Steve Craig - Forest Products (Leisure) Ltd >>> Tel +44 1330 860505 Mob +44 7778 007607 >>> ======================================== >>> http://forestlogcabins.com >>> Email: steve@forestlogcabins.com >>> Skype: s.craig - iChat: steve.craig >>> ======================================== >>> >>> >>> >>> >>> --------------------------------------------------------- This >>> message is sent to you because you are subscribed to the mailing >>> list . To unsubscribe, E-mail to: archives: >>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>> support@webdna.us >> >> >> -- >> Matthew A Perosi >> Corporate Consultant >> Mobile Marketing Expert >> Senior Web Developer >> SEO Analyst & Educator >> matt@psiprime.com >> >> Psi Prime, Inc. >> 323 Union Blvd. >> Totowa, NJ 07512 >> >> Direct: 888.872.0274 >> Fax: 888.488.5924 >> >> http://www.perosi.com >> --------------------------------------------------------- This >> message is sent to you because you are subscribed to the mailing list >> . To unsubscribe, E-mail to: archives: >> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >> support@webdna.us > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------090203040101020603040003 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Dan is correct that Google does try to figure this stuff out because they know that most people don't understand the technical aspects.

But if you let them figure it out you are also continuing to dilute your link building efforts, and you are leaving it to Google to identify your primary domain.

All of my best results always seem to come from not letting Google do the thinking. 

It always seemed to me that you'll always rank better when you you just do what they recommend without them spending more CPU cycles to figure out what you should be doing.

-Matt



On 1/20/2014 1:28 PM, Dan Strong wrote:
Google's latest stance on it = dont sweat it, but let us know which one is the "authority")

Don't sweat it: http://searchengineland.com/googles-matt-cutts-duplicate-content-wont-hurt-you-unless-it-is-spammy-167459
Dupe content: https://support.google.com/webmasters/answer/66359
Canonicalization: https://support.google.com/webmasters/answer/139066

As for redirects, WebDNA's [redirect] has always been hit and miss depending on platform, so when SEO matters, I always use Apache redirect, usually in .htaccess, but if there are a bunch then directly in httpd.conf

Redirect<space>301<space>/oldPage.html<space>http://www.Domain.com/newPage.html
Redirect<space>301<space>http://www.OldDomain.com<space>http://www.Domain.com/

etc.

-Dan Stronghttp://www.DanStrong.com
On 1/20/2014 10:16 AM, Psi Prime Inc, Matthew A Perosi wrote:
Yes, you are diluting your domain authority by having multiple domains service the same content.  There's even a potentially worse problem though... Depending on how many domain names you have, more than 2 or 3 maybe, Google will view your single website as multiple websites.  This is known as duplicate content. 

Google knows not to penalize someone for the "duplicate" version of www.domain.com and simply domain.com, but when it comes to things like:

www.domain1.com
domain1.com
www.domain2.com
domain2.com
www.domain3.com
domain3.com
www.domain4.com
domain4.com
www.domain5.com
domain5.com

then Google starts to get upset because this looks like 10 different websites.  From their point of view, you've sold or syndicated your information, and it will work against you.

Many of the sites I manage have 5 or more domain names we use for offline marketing.  I use a few different methods to handle this.  Normally, I would just use the domain forwarding feature with GoDaddy to 301 the alternate domain names to the primary domain names.  But I also add extra Google Analytic UTM tracking codes so I know what domain the person used in the first place.

However, for your situation, since you already have pages in the Google index, you should change your Apache configuration to test the domain name, and rewrite the URL to the primary domain name.  That way you can still keep the pages and variables.  You would want to make sure the Apache config uses a 301 to indicate the changed URLs.

You could also build this feature into WebDNA using the [redirect] context, but you might run into issues depending on which version of WebDNA you are using because the [redirect] is a 302, not a 301.  Using a 302 will not solve the duplicate content issue.

Hope that helps,

-Matthew Perosi

On 1/20/2014 12:37 PM, Steve Craig wrote:
Hi

Just looking for a bit of advice - I have a site that is available via many different domains and at the moment there are no redirects so if you arrive via domain1.com then every page thereafter stays on that domain, likewise if you arrive as domain2.com it stays there but all the content is the same from the same CMS.

My question is do you think I am wasting Google ranking by effectively sharing out my hits across domains or do you think I should redirect all requests to one of the domains?

I read somewhere that I am weakening my position a bit because my "popularity" is being shared out across multiple domains, it seemed logical just wondered what everyones experiences were.

If redirecting is the answer, what is the easiest way on an Apache server, using WebDNA or using an Apache redirect?

Thanks for any input.

Cheers
========================================
Steve Craig - Forest Products (Leisure) Ltd
Tel +44 1330 860505 Mob +44 7778 007607
========================================
http://forestlogcabins.com
Email: steve@forestlogcabins.com
Skype: s.craig - iChat: steve.craig
========================================




--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 


-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatormatt@psiprime.comPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 

-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatormatt@psiprime.comPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------090203040101020603040003-- matt@psiprime.com

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

ShowNext Command (1997) value in forms (2000) Shopping cart now bad (1997) 2.0 Info (1997) pacific-coast or starnine? (1998) search criteria (2000) Nesting format tags (1997) Variables for chat (1997) script to autmaticaly update Filemaker DB (2000) webcatalog and webmerchant 2.1 (1998) Linux WebCatalog on Apache w/ Raven SSL (2000) Errata: WCS Newbie question (1997) WebDelivery: One step closer !! (1997) Assign Variable Value (1998) WebCat2 - Getting to the browser's username/password data (1997) RequiredFields template (1997) [OT] Indexing of dynamic web sites (2003) Fun with Dates - revisited (1997) Firewalls - What's Good? (1999) bug in [SendMail] (1997)