![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
This new tool < http://www.tippy.co.uk/google-datacenter-check/ is faster and lighter than MCDar. It achieves the same thing without that cluttered user interface. Worth taking for a spin if you want to check your positions across datacentres. It seems as though more search engines might be added soon... |
#3
| |||
| |||
|
|
Roy Schestowitz wrote: This new tool < http://www.tippy.co.uk/google-datacenter-check/ is faster and lighter than MCDar. It achieves the same thing without that cluttered user interface. Worth taking for a spin if you want to check your positions across datacentres. It seems as though more search engines might be added soon... Does not work, returns PHP error. Would be nice if it did though because I cannot recall when was the last time MCDat tool did not time out on me. |
#4
| |||
| |||
|
|
Borek offered help with the extensive list of datacentres, whereas John takes care of the Perl which handles regular expressions for Yahoo SERP's. From there onwards, I guess it can only be extended further, in line with suggestions. |
#5
| |||
| |||
|
|
OK, not sure what to do here. If I run the scripts locally under Apache, they all work fine. All the backlinks check work ok and get good results. If I run the scripts from the web server, Google gives me a 302 response to the request which works fine locally. Another strange thing, other requests into google, using the same method are not returning the 302. Just the "link:" command. The same server is quite happy to take a request from the browser for this request. Do you guys see this or is all ok from your end? |
#6
| |||
| |||
|
|
Darren Tipton wrote: OK, not sure what to do here. If I run the scripts locally under Apache, they all work fine. All the backlinks check work ok and get good results. If I run the scripts from the web server, Google gives me a 302 response to the request which works fine locally. Another strange thing, other requests into google, using the same method are not returning the 302. Just the "link:" command. The same server is quite happy to take a request from the browser for this request. Do you guys see this or is all ok from your end? It seems to be working fine here. Just did one of my sites, results seem consistent with what I saw manually and with McDar tool. You must have tripped some sort of alarm with Google looking for those Wombats thousand times during the debug. So, they politely wanted to send you some place else ;-) Where was the 302 pointing to? |
![]() |
| Thread Tools | |
| Display Modes | |
| |