www.www appearing in Google results

[paulbeckett]

Hi

We have a problem with a www.www.kjbeckett [dot] com site appearing, being navigatable and even appearing in Google results! (I have specifically not completed the url so not to encourage Google any further).

If you search for "duchamp accessories" (or click this link to to see the Google page) you can see KJ Beckett has two results appear.

The first, at the top of the page, is fine. It goes to www.kjbeckett.com/acatalog/duchamp.html which is completely fine and correct.

However the second (towards the bottom of the page) goes to the same page but in a www.www.kjb...(and so on) url. When you click on the link, the entire www.kjbeckett.com site is navigatable using the strange www.www url.

Besides not want another site with the www.www url, I'm very concerned that Google will see this as duplicate content and peanilse the real site.

Has anyone had this problem before? I really want to figure out the best way of stoping Google from indexing this rougue www.www site in a way that won't impact the real/main site?

Paul

[paulbeckett]

I've just noted that Google seems to have indexed c. 3000 pages from the www.www [dot] kjbeckett.com site.

Also there are 129 links pointing in when doing a link:www.www [dot] kjbeckett.com

However the links it refers to are definitely not using the rougue www.www. url, they are using the normal, proper url.

It seems like Google is treating the two the same, however in the search results it is treating the two as seperate sites?

Paul

[paulbeckett]

Hi all

I've checked the .htaccess file and an export of the network settings and neither make any reference to www.www

I can't understand how this page could even exist? Could this be a problem on the server?

Paul

[guccij]

In Google webmaster tools you can specify the url settings - might be as well to check all is as it should be there.

[paulbeckett]

In Google webmaster tools you can specify the url settings - might be as well to check all is as it should be there.

Thanks. I have checked the Webmaster settings. Doesn't seem to be anything that refers to www.www

After going over this, my biggest concern is why is the server actually creating pages called www.www. This seems to be a bug on the server. Even if the webmaster tools, htaccess or any site map has a rouge link, it should just be a dead link. The server shouldn't be creating these pages. If the pages weren't being created there wouldn't be any Google indexing issues.

I will contact Pinbrook!

Paul

[Mike Hughes]

Paul,

Is there something wrong with your sitemap page? I've tried several times to view it and the source but it's always locking up my browser. Am I the only one with problems viewing it?

Mike

[Duncan Rounding]

The sitemap page is so large it is difficult to load.

[paulbeckett]

Hi Mike

Is there something wrong with your sitemap page? I've tried several times to view it and the source but it's always locking up my browser. Am I the only one with problems viewing it?

The site map currently shows links for all products. Thats about 19000 links. We are moving to showing section pages only which will significantly reduce the amount of links.

It is IE that can't handle it... the Site Map page works fine on Chrome and FF.

Paul

[animal dreams]

Paul,

Don't want to worry you but it gets worse!

I can also view your pages as www.www.www.www......

Think you need to talk to your host.

[paulbeckett]

Thanks for pointing this out!

I'm certain the core root of the problem is a server issue. I have contacted Pinbrook to resolve.

Paul

[Mike Hughes]

I've checked the .htaccess file and an export of the network settings and neither make any reference to www.www

I wouldn't be surprised if it's the htaccess file. This could well be the htaccess file rewriting urls with an added www. Are you doing any rewrites for non www. urls?

Mike

[paulbeckett]

Hi

This is the contents of the .htaccess file. Could this be causing the server to do this?

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName www.kjbeckett.com
AuthUserFile /data/web/_k/_j/_b/kjbeckett.com/public/www/_vti_pvt/service.pwd
AuthGroupFile /data/web/_k/_j/_b/kjbeckett.com/public/www/_vti_pvt/service.grp
ErrorDocument 404 http://www.kjbeckett.com
Redirect /flatlinks http://www.kjbeckett.com/acatalog/stewartstand.html
Redirect /flatlinks.html http://www.kjbeckett.com/acatalog/stewartstand.html
Redirect /flatlinks.htm http://www.kjbeckett.com/acatalog/stewartstand.html

This .htaccess file has been in place for many years without any changes.

(I presume there is no risk of posting the contents of an .htaccess file???)

Many thanks

Paul

[paulbeckett]

Hi all

I have noticed www.cultpens.com, which is an Actinic site, have the same issue?!?!

e.g. www.www [dot] cultpens.com
e.g. www.www.www [dot] cultpens.com

There must be something relating to us both... not 100% sure about hosting, I would imagine were both on v9?

Paul

[Mike Hughes]

I don't see anything in the htaccess file that could cause this.

There seems to be a few problems here:

1. Google is getting a link to a page with an extra www. from somewhere. Possible a server setting. Possibly just an mis-entered external link. There's no easy fix to this bit if it's an external link.

2. For some reason all the links on this page then have www.www for the urls and google is then indexing these. This shouldn't happen as the basehref doesn't have the extra www. in it. Not sure why this is. Is the basehref broken by the 'Actinic' bit in it?

2. The dns server should not be responding with an IP address to the faulty www.www urls, nor should the server be responding with the page. This is a hosting problem and should be corrected.

Mike

[paulbeckett]

Hi Mike

Interestingly, if you do a link:www.www [dot] kjbeckett.com in Google it displays lots of external links pointing to the rougue site that definately don't feature the www.www. They are valid links though and do exist for the real site. It's almost as if Google is automatically converting them.

However for me, the biggest thing is killing the problem at the server. If the server stops creating the www.www.www.www site there will be nothing for Google to crawl and nothing to index.

The dns server should not be responding with an IP address to the faulty www.www urls, nor should the server be responding with the page. This is a hosting problem and should be corrected.

I'm getting the feeling this is definately a server problem.

Paul