Reading the Wrong page

[Andy]

Have recently done onpage optimisation and run a links campaign for a client. Trouble is, the site is all in ASP which usually shouldnt be a problem (index.asp is the default home page) Yet still google gives index.html all the Page Rank and link popularity even though the file doesnt exist on the server.

As far as I can see this should not happen, anyone else seen this before?

What I thought might resolve the issue was to 301 index.html to index.asp but the client tells me this is not possible as the webspace serves several domains. My knowlege of IIS is limited as more used to working with Apache. If the above is true can anyone else see any kind of solution to the problem?

Thanks for your help

Andy

[compar]

Anybody who hosts on IIS deserves what they get

Was there ever a index.html file?

I don't see why a 301 redirect won't work. You don't have to use an IP address to do a redirect I don't believe. So a redirect to www.hisdomain.com/index.asp should work.

[Andy]

Thanks for the reply Compar. Sorry, I should have said. The sites originally had an index.html page with absolutly no content, only an onpage javascript redirection. Simply removing the didnt seem to make any difference.

I didnt think a redirection would be IP dependant yet the client insists that under their current configuration if they were to set up a server redirection then it would be common to all the domains. Their next best offer was to set up a custom 404 error page with a script redirecting to index.asp. Oddly enough this seems to return a 302 status code.

Does anyone know if between this will be enough to force google into correcting the mistake?