Forum Moderators: martinibuster
My greatest fear is that this person is stupid enough to probably click their own ads and crap like that.
I have already contacted his free web host (fugures) about the abuse and reported it to adsense abuse. Any other suggestions to help protect my good standing account with google?
This is very irritating
In my experience, webmasters who hotlink to your images will already have looked at the image once themselves. When they hotlink to it, they will continue to see their hotlinked image because they are seeing it from their browser cache. However, all visitors to their site will see the broken image (or the replacement image notifying viewers of the bandwidth theft) and this moron's website looks stupid pretty-much in perpetuity, and serves him right, because the images always look like they're working OK to him, as long as the image remains in his browser cache.
I have some sites that continue to hotlink the same images on my site, some now for more than a year. They still don't recognize their visitors aren't seeing the images! :-)
Some Korean blog hotlinked 2 or 3 images over a year ago.
Rather than .htaccess redirects, I played musical filenames for certain .gif images.
I rename the real image, and point my pages to it.
Then I substitute something fun under the original hotlinked .gif filename.
Like I say, its been over a year and they never noticed apparently.
If they would just clean their cache it should be obvious. -Larry
wizarddave: What and basically how would I modify the htaccess file: This sounds like it may be a more viable fix for the problem.
Now I'm just waiting for a Google response. Maybe early this week. I hope.
------------------------
RewriteEngine On
Options +FollowSymlinks
RewriteCond %{HTTP_REFERER}!^$
RewriteCond %{HTTP_REFERER}!^http://([a-z0-9-]+\.)*mydomain.com/? [NC]
RewriteCond %{HTTP_REFERER}!^http://([a-z0-9-]+\.)*another-domain-you-want-to-allow.com/? [NC]
RewriteCond %{HTTP_REFERER}!^http://([a-z0-9-]+\.)*babelfish.altavista.com/? [NC]
RewriteCond %{HTTP_REFERER}!toolbar.googl [NC]
RewriteCond %{HTTP_REFERER}!/search\?q=cache: [NC]
RewriteCond %{HTTP_REFERER}!/search\?sourceid=navclient [NC]
RewriteCond %{HTTP_REFERER}!/translate_c\?hl= [NC]
RewriteRule .*\.(gif¦GIF¦jpg¦JPG)$ - [F]
ErrorDocument 403 /blank.html
Options -Indexes
---------------------------------------
The lines under the lines with your domain(s) allow your images to work in google image search and other services that scrape your page in an allowable way.
blank.html is a zero-byte file.
The only downside would be if they engaged in abuse and got your account suspended for it. If that were to happen, it would seem to be fairly simple to present your evidence, including your earlier notification to the AdSense team, and get the matter resolved.
You walk away with the earnings generated by the rogue, and, in the end, they get banned or whatever.
The only downside would be if they engaged in abuse
It has been suggested before and needs to be repeated.
AS should have each account register the sites that are using their AdSense code. It just seems logical. They ask us to do this when we sign up.
From some posts lately in this forum it's obvious that a new group of scam artists are getting involved. These people who have been involved in Ponzi schemes and other Internet scams are becoming more active. I have personally followed the trails of some of the posters and found them involved in things that don't bode well for AdSense.
If ASA is monitoring this thread then maybe you could pass on the word that now is the time to become more proactive with both this type of thing and the regular abuse.
If this is not in your job description maybe you could drop a note to GoogleGuy or some other person who may have more clout to set a fire under someone.
This person will simply get another host and I will have to find him and potentialy deal with this issue again in the future, so it really needs to be addressed. I do find it hard to believe that I am the first one that this has happened to. So I am hopefull that it can be resolved (without any AS downtime)
Tropical Island is right, there are some new approaches being taken to scam people and companies. CHECK YOUR LOGS.........
I would have thought, that they would want to check every site that carried adsense. At least they could cross reference a site to an adsense account and avoid this problem.
It would surely improve the quality of the sites carrying adsense as well.