Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Port 80 links and duplicate content

         

Hobbs

1:26 pm on Jul 4, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I found in Google WMT that many of the keywords used in linking to one of my sites contains mysitname.com:80 and the links are mysitname.com:80/somepage.. Which naturally opens the same page without the port 80 in the url.

On googling mysitename:80 I found that Google is indexing Alexa serps.

a) Won't that trigger a dupe content penalty?

b) How come Google is indexing another search engine's serps?

Receptional Andy

1:36 pm on Jul 4, 2008 (gmt 0)



Won't that trigger a dupe content penalty?

As far as I'm aware, port 80 will never show in Google serps, since it's the default port for http requests. Port numbers are only visible if they deviate from the norm. Example.com:80 is exactly the same as example.com. In a similar way, your browser simply hides :80 from the address bar as a convenience to you.

How come Google is indexing another search engine's serps?

If it's a valid URL, Google will have no problem indexing it. Most search engines block indexing of search results via robots exclusion, which seems to be widely considered as best practice.

Hobbs

3:05 pm on Jul 4, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



>port 80 will never show in Google serps

Accordingly the port number should not be be in a keywords listed on WMT right? It does.

Googleing "mysitename.com:80" returns Alexa pages with links that contain in both the anchor and the link to my site MySiteName:80 in them, also for every single other link on that Alexa page which lists all the sites linking to some other site.

jdMorgan

3:49 pm on Jul 4, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Redirecting to remove port 80 should be part of your domain canonicalization code on your server. In addition, it is perfectly-legal for an FQDN to have a trailing dot on it.

Assuming that you redirect from non-www to www, your code should redirect all of example.com, example.com:80, example.com., example.com.:80, www.example.com:80, www.example.com., and www.example.com.:80 to www.example.com -- Anything except exactly "www.example.com" should be redirected to "www.example.com".

Sites which use or support https should also take care that each page is available using either http or https, and not both.

Jim