| 1:53 am on Feb 17, 2006 (gmt 0)|
Hmm, that would be pretty bad if they didn't filter it on the domain side and considered any host name to be different.
I have been curious about this myself.
| 3:08 am on Feb 17, 2006 (gmt 0)|
|Does Google considers www.example.com and example.com as different domains? |
Oh! //www.yoursite is actually a sub-domain of //yoursite
Need I say more?
Yes, I need to! Loads of screwed-up domains for SEO purposes all over the Net!
| 5:12 am on Feb 17, 2006 (gmt 0)|
I have just check them with wget.
www.examle.com and example.com seems resolve to the same domain and the same page for the both cases. So I still cannot understand whyh Google does not filter www.example.com with the filter set to example.com.
| 6:15 am on Feb 17, 2006 (gmt 0)|
Optirex, are you saying that filtering http://example.com resolves this issue?
Got a few http://www.example.com's in my own filter...
| 6:27 am on Feb 17, 2006 (gmt 0)|
If you block example.com, ads will also be blocked on www.example.com.
However, if you block www.example.com, ads will not be blocked on example.com.
So, there is no need to filter both, but make sure to remove the 'www' if you want to block ads across the entire domain.
Hope that clarifies!
| 10:06 pm on Feb 17, 2006 (gmt 0)|
Thanks ASA! Got some work to do with my filter!
It appears I have been doing this wrong all the time!
| 4:29 am on Feb 18, 2006 (gmt 0)|
|If you block example.com, ads will also be blocked on www.example.com. |
Unfortunately, AdSenseAdvisor, I have two specific examples when it is not so.
Example.com does *not* block www.example.com
Could it be the spammers' tricks, Google bug or what is it?