Googlebot is annoying the hell out of me
Note: This question may not technically belong under HTML & CSS, but I wasn't sure where else to stick it, because it's kind of a general -- yet complicated --question. Here goes...
We have a website that is made up of automotive listings. Feel free to check it out if you'd like. It's called theusedcarplace.com. The site was constructed based upon a script created by a company called Flynax. Aside from some bugs and broken links that needed to be fixed during the first month or two, the script has basically done what we need it to do. Specifically, a number of those broken links were caused by the script trying to load URLs beginning with www.www. (instead of just one www.). I managed to track down the majority of these after I set up a little PHP script to email me an error report each time a user attempted to load a non-existent file or page.
In a possibly unrelated sidebar, I finally got the Apache rewrite mod to work on our site last week. The script developers had said all along that all I had to do was click one little button in the Admin section, but I could never get it to work -- it would just result in every link breaking -- until I went in and cleaned up the htaccess file, putting everything on individual lines. That fixed the problem, and the Apache rewrite is now functional.
Since (but possibly unrelated to) that change, I've been getting thousands upon thousands of 404 Error Report emails each day. All of them look something like this...
On Tue Nov 13 2012 11:02:54 am CST, 18.104.22.168 tried to load :
User Agent = Googlebot-Image/1.0
I don't see anything on the site or in the sitemap that has the www.www. prefix and as near as I can determine, these specific files that Googlebot is looking for have never existed.
Can anyone give me an idea -- short of telling Googlebot to not index our site -- of how to get these emails to stop? Will Googlebot eventually realize that these files don't exist, or is there something broken in the structure of our site? Did my htaccess tinkering cause this, or is it just a coincidence?
Any information at all is greatly appreciated.