| 8:45 pm on Jul 23, 2005 (gmt 0)|
One way to check is to use WW server headers tool:
Just plug in their link to you, and see what the header response it.
| 2:25 am on Jul 24, 2005 (gmt 0)|
So what should I see here? Also I e-mailed the webmaster and he said "that is just the way I do things". He said he was doing nothing wrong. He told me the click counter was called "ccount". I looked up it up but I didn't know what to look for to see if it was malacious.
| 3:44 am on Jul 24, 2005 (gmt 0)|
That is bad right? lol. I guess I can try to contact his host. Worth a shot.
| 3:51 am on Jul 24, 2005 (gmt 0)|
Hi Alphacooler, actually the main problem with a 302 redirect is that search engines don't recommend it. Rather they prefer 301 redirect. That's a pretty gud tool sugested above. If U havin probs understandin, sticky me the redirected link of ur site. I'll help u sort it.
| 4:29 am on Jul 24, 2005 (gmt 0)|
I used the tool and at the top it reported:
HTTP/1.1 302. Therefore I am assuming he is using a 302 to my site.
| 9:56 pm on Jul 24, 2005 (gmt 0)|
Hopefully all search engines will do what Yahoo have done, and treat any 302 Redirects that point to a different domain as 301 Redirects, and then the problem will go away.
| 10:50 pm on Jul 24, 2005 (gmt 0)|
Yeah but what about when the redirects are to your site. That causes just as much of a problem in the SERP's.
| 1:47 am on Jul 25, 2005 (gmt 0)|
That is the exact scenario that Yahoo is fixing.
Someone does a 302 redirect from their site to your site, if the domain of the redirecting page does not match the domain of that it is redirecting too, treat it as a 301 Redirect i.e. index the page under the new URL which is your ULR.