Forum Moderators: open
Laurenz
I have a www, and www-less domain and a .ca and .com
domains all pointing to the very same IP address. In
the past Google choose one to index and ignored the rest.
A few weeks ago, Google changed their duplicate content algorhim and I was dropped from Google (site:www.widget.com or .ca with or without www turns up nothing). However I still have pagerank.
So I don't know if google messed something in the new Dup Content Algorthim or if it was intentional.
If it was intentional is was stupid. Its perfectly valid to have a .ca and .com domain with duplicate content, as I advetise one for canadians who prefer to shop on .ca (canadian sites) and Americans who prefer to shop on .com site.
RewriteEngine on
RewriteCond %{HTTP_HOST}!^mysite\.com
RewriteRule ^(.*)$ [mysite.com...] [R=301]
and it redirected www to non www fine (90% of links are to non www)
However when I checked my subdomains they were as follows:
[maindomain.com...]
instead of
How can I redirect www to non www and preserve the subdomain stuctures?
Thanks.
[edited by: No5needinput at 1:35 pm (utc) on Oct. 13, 2004]
Having several aliases for a domain name on the same IP is not duplicate content. Their is only one content. Just several alias URL's that point to the same content.
I could see if somebody had hundreds of keyword specific URL's and was spamming the engines, Google would be upset, but my understanding is that Googleguy once said they concatonized www and non-www and .country and .com down to the simplest form of the .com domain. Correct me Googleguy if i am wrong.
site:www.domain.com
site:domain.com
this site redirects to domain.com
0 pages listed for site:www.domain.com
all pages listed for site:domain.com
Ideally search engines would treat this the same, if there were no spammers/cloakers in the world, but the unfortunate fact is that www.domain.com and domain.com can be separate websites if you use mod_rewrite
It doesn't matter I think which you pick, the user will never see it with the correct mod_rewrite
=================
re the subdomains, you need to add exclusions for the subdomains, I'm not very good at mod_rewrite, but the basic idea is this, pseudocode
if
rewritecondition subdomain1 ¦ subdomain2 ¦ subdomain3 do nothing
else
rewrite condition ^domain.com rewrite to www.subdomain.com
That is link only to: www.domain.com/ and to www.domain.com/folder/.
Don't link to: www.domain.com/index.html or to www.domain.com/folder/index.html and so on.
Open IIS in MMC -- expand all sites.
Right click on site you wish to redirect and go to "Properties."
Click on "Home Directory" tab.
In the "Redirect to:" field, fill in the complete URL of the site/page you want to redirect to. Include "http://"
Check "The exact URL entered above."
Check "A permanent redirection for this resource."
Click "Apply" and close.
I agree with you. It seems pointless to degrade your site if you are using www or not. Back in the good 'ol days, www was for a companies' web site and the domain name without www was usually the email server. But back in the good 'ol days, webservers and software were not as smart as they are now. Today it is possible to just add a pointer record in your DNS so both types can go to the website. If you need an email server, just add another pointer to mail.widget.com. Need a different ftp server? Just add ftp.widget.com and so on... Most sites today utilize both www and no www, so what is the real point in making this a problem? It seems that the G would have fixed this.
But then we get into whether or not the WWW thing is really occurring. I know it seems to affect the little green bar that everyone is hung up on but my question would be if anybody has seen or experimented with this to see if the problem actually exists in the SERPs. PR is one thing, but the returns are a whole different matter.
The problem you're having with subdomains is due to the construct you used in the RewriteCond. As posted it says, "IF the requested domain is NOT "mysite.com", then redirect." Therefore, all domains and subdomains NOT equal to "mysite.com" will be redirected. By changing that to a positive match, you can avoid the problem:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.com
RewriteRule ^(.*)$ http://mysite.com/$1 [R=301,L]
Also, add the [L] flag as shown unless the output of this rule needs to be further rewritten during the current HTTP request.
Some server configurations will require the addition of
Options +FollowSymLinks Jim
Before our site was redesigned early this year the old site used frames (the new site does not)
The old site home page was named www.mysite.com/home2.html and the frame was mysite.com/navigation2.html.
When the new site launched the homepage was named mysite.com/index.php.
Here's the question. I saw today the the old page names (home2.html and navigation2.html) have some sort of a redirect that reads in part:
<FRAMESET ROWS="100%,*" cols="100%,*" border="0" frameborder="0" framespacing="0">
<FRAME SRC="http://www.mysite.com" scrolling="auto" noresize>
</FRAMESET>
Is this a problem for google?
Thanks
It's my guess that that's possibly the reason we're seeing a domain.com URL only version of the homepage of sites in the index a lot of times when there aren't any links done that way. Of course I could be wrong, but I believe it's quite possibly one of their measures to combat spam issues.
Thanks!
Laurenz