eliminating duplicate Perl Dancer site (with and without www )
Hi, I am writing on the list as the subject might be relevant to every web site owner. I've just noticed both http://www.perldancer.org/ and http://perldancer.org/ serve the site. As far as I understand this is a waste of Google Juice. It is better to have only one of them serve the pages and have the other one redirect to the one serving. e.g. http://perldancer.org/ serving the content and http://www.perldancer.org/ redirecting to http://perldancer.org/ regards Gabor
On 2017-10-05 10:06 PM, Gabor Szabo wrote:
I am writing on the list as the subject might be relevant to every web site owner. I've just noticed both http://www.perldancer.org/ and http://perldancer.org/ serve the site.
As far as I understand this is a waste of Google Juice. It is better to have only one of them serve the pages and have the other one redirect to the one serving.
e.g. http://perldancer.org/ serving the content and http://www.perldancer.org/ redirecting to http://perldancer.org/
I completely agree with what Gabor said. And not just a waste of Google Juice, Google will not only hit your site twice as much but it will penalize you in the search rankings due to all the duplicate pages. -- Darren Duncan
Hi, It is usual to use a DNS alias to make both addresses go to the same machine and then use a rewrite and / or a server alias to make the same machine server both sites.
On 6 Oct 2017, at 4:06 pm, Gabor Szabo <szabgab@gmail.com> wrote:
Hi,
I am writing on the list as the subject might be relevant to every web site owner. I've just noticed both http://www.perldancer.org/ and http://perldancer.org/ serve the site.
As far as I understand this is a waste of Google Juice. It is better to have only one of them serve the pages and have the other one redirect to the one serving.
e.g. http://perldancer.org/ serving the content and http://www.perldancer.org/ redirecting to http://perldancer.org/
regards Gabor _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
._--_|\ Peter Yardley | / \ Senior Network Engineer | Peter.Yardley@uts.edu.au \_.--._* Information Technology Division, | Ph: +61 2 9514-2358 . v University of Technology, Sydney.| Fax: +61 2 9514-4327 UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email.
On 2017-10-05 10:16 PM, Peter Yardley wrote:
It is usual to use a DNS alias to make both addresses go to the same machine and then use a rewrite and / or a server alias to make the same machine server both sites.
That may be common, but its a bad practice that needs to go away. Each web page should have exactly 1 url at which it lives (archives and backups notwithstanding); any other urls by which it may be reached should invoke a client-side redirect to that 1 url, not just serve a copy. Doing this correctly is also quite easy. -- Darren Duncan
On 10/06/2017 07:06 AM, Gabor Szabo wrote:
Hi,
I am writing on the list as the subject might be relevant to every web site owner. I've just noticed both http://www.perldancer.org/ and http://perldancer.org/ serve the site.
As far as I understand this is a waste of Google Juice. It is better to have only one of them serve the pages and have the other one redirect to the one serving.
e.g. http://perldancer.org/ serving the content and http://www.perldancer.org/ redirecting to http://perldancer.org/
regards Gabor
Hello Gabor, thanks for spotting this. I agree with you, we should permanently redirect from www.perldancer.org to perldancer.org. Regards Racke -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration.
On Fri, Oct 6, 2017 at 6:06 AM, Gabor Szabo <szabgab@gmail.com> wrote:
Hi,
I am writing on the list as the subject might be relevant to every web site owner. I've just noticed both http://www.perldancer.org/ and http://perldancer.org/ serve the site.
As far as I understand this is a waste of Google Juice. It is better to have only one of them serve the pages and have the other one redirect to the one serving.
e.g. http://perldancer.org/ serving the content and http://www.perldancer.org/ redirecting to http://perldancer.org/
Two suggestions. Pick which URL you want as the definitive version and: 1/ Include a canonical tag pointing to that URL (on both versions of the site) <link rel="canonical" href="http://perldancer.org"> 2/ In Google Webmaster Tools (every site that cares about SEO should be registered with GWT) you can tell Google which domain to use (gear icon -> settings -> preferred domain). You can put redirections in place as well if you want - but these two actions will take care of it. Dave...
participants (5)
-
Darren Duncan -
Dave Cross -
Gabor Szabo -
Peter Yardley -
Stefan Hornburg (Racke)