In our error logs we have quite a few (~ 10s / day) internal recursion errors caused by googlebot. Here is a typical example:
[Sun Jul 03 10:58:22 2011] [error] [client goo.gle.ipa.ddr] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
Looking in the access log, the offending GET is always looking for a broken URL with this format:
Undoing the URL encoding to make it more readable:
http://ourdomain.com/wp-content/uploads/2007/11/image-name.jpg" width="39" height="50" alt="image"/></a>< href="/m/imgres?q=some+query+here
This looks like a broken fragment of some HTML that was displaying the image as part of a hyperlink. Looks like it might have been part of some sort of search result.
We don't have any links of this format anywhere in our site, so I can only assume this is a reference from somewhere else that is either misinterpreted by googlebot, or is just broken in the page markup.
There is no entry for the referrer in the Apache access_log. I have tried to find the source in Google webmaster tools, but although the unreachable is noted, there is no mention of the source. I've also tried to use Google to find the reference without success. I do notice that the "imgres" in the href fragment is used in Google image search, but the rest of the fragment isn't consistent with this.
- Should I bother with this or just let these recursion errors happen (10s of them / day)?
- If I need to bother, any suggestions on how to find their source?