Does client-side JavaScript act like a 301?

Reading Time: < 1 minute

Before you shoot me for saying that, take a look at the following SERPs for apcug.org (I am on its board but not involved with the decision that moved it to apcug.net two years ago) and check the total page count in the index:

Compare with the results for apcug.net

The Google and Live results show the same count for .net and .org, which is unlikely. Yahoo’s results are quite different and more likely to be accurate.

The webmaster of the day had placed a client-side JS “location.replace” statement in index.htm of the .org, but that should be invisible to the spiders, right? There is no meta refresh in the page or a 301 via other means. The .org page returns a 200 header response, as it should.

Why are G and L showing the same indexed page counts for .org and .net?
Please comment.

Mastodon